Too many links errno 31 openvpn как исправить

Сообщения: 7
Благодарности: 0

Доброго времени суток уважаемые коллеги. Прошу подсказать как исправить ошибку при развертывания openVPN.
Имеется сервер Windows 2012 на котором есть адаптер, смотрящий наружу (в Интернет) и имеющий адрес 213.xxx.xxx., есть адаптер для внутренней сети с адресами 192.xxx.xxx.xxx.
На этом же сервере установлено приложение OpenVPN, которое развернуто с помощью версии openvpn-install-2.4.6-I602. Служба VPN создала виртуальный адаптер с адресацией 172.xxx.xxx.xxx. За безопасность отвечает Kerio, в правилах трафика разрешено подключение по 443 порту на MAP 172.xxx.xxx.xxx (то есть на виртуальный адаптер)
Цель в том, чтобы компьютер, находящийся в другом городе мог по интернету доходить до внешнего адреса 213.xxx.xxx.xxx, далее он бы перенаправлялся на виртуальный адаптер 172.xxx.xxx.xxx, который бы проверял сертификаты и разрешал бы компьютеру пользоваться ресурсами сети 192.xxx.xxx.xxx.
Следуя вот этой инструкции http://lumpics.ru/configuring-openvp. er-on-windows/ я настроил OpenVPN сервер в локальной сети. То есть на одном ПК с внутренним адресом создавался виртуальный адаптер и компьютер клиент создавал защищённый канал.
На тестовом компьютере установлена такая же версия OpenVPN. При попытке подключения выскакивает следующая ошибка:
Не могу понять это ошибка происходит из-за того что клиент не может даже достучаться до сервера и ему мешает сетевой экран или он доходит до виртуального адаптера, но проблема в openVPN? И нужно ли дополнительно что-то указывать в настройках внешнего адаптера и виртуального?

Настройки сервера

port 443
proto udp
dev tun
dev-node «VPN Lumpics»
dh C:\\OpenVPN\\ssl\\dh2048.pem
ca C:\\OpenVPN\\ssl\\ca.crt
cert C:\\OpenVPN\\ssl\\Lumpics.crt
key C:\\OpenVPN\\ssl\\Lumpics.key
server 172.xxx.xxx.xxx 255.255.255.0
max-clients 32
keepalive 10 120
client-to-client
comp-lzo
persist-key
persist-tun
cipher DES-CBC
status C:\\OpenVPN\\log\\status.log
log C:\\OpenVPN\\log\\openvpn.log
verb 4
mute 20

Настройки клиента

client
resolv-retry infinite
nobind
remote 213.xxx.xxx.xxx 443
proto udp
dev tun
comp-lzo
ca ca.crt
cert vpn-client.crt
key vpn-client.key
dh dh2048.pem
float
cipher DES-CBC
keepalive 10 120
persist-key
persist-tun
verb 0

Текст ошибки

Ignoring option ‘dh’ in tls-client mode, please only include this in your server configuration
Enter Management Password:
Wed Dec 12 16:23:15 2018 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.

Сообщения: 6431
Благодарности: 1444

Конфигурация компьютера
Процессор: Intel Core i5-8259U @ 2.30GHz
Материнская плата: Intel NUC8BEB
Память: Patriot 2400 C15 Series DDR4-2400, 32 GB
HDD: Samsung SSD 970 EVO Plus 500 GB, M.2
Видеокарта: Intel Iris Plus Graphics 655
Звук: Behringer UCA222 + M-Audio Studiophile AV 40
Монитор: BenQ G900 (19″ LCD, 5:4)
ОС: Windows 11 Pro x64

Собственно, надо просто перевести то, что пишут.

Цитата Nagumo:

Ignoring option ‘dh’ in tls-client mode, please only include this in your server configuration »

В клиенте опцию dh не надо указывать, это для сервера.

Цитата Nagumo:

No server certificate verification method has been enabled. »

Не активирован режим проверки сертификата на сервере, см. ссылку.

А зачем вам ОпенВПН, если у вас Керио есть, который сам прекрасно умеет VPN?

Для отключения данного рекламного блока вам необходимо зарегистрироваться или войти с учетной записью социальной сети.

Сообщения: 7
Благодарности: 0

Спасибо! Сейчас буду искать почему режим проверки сертификатов в данном случае не активирован. VPN с помощью Kerio не устраивает руководство по требованиям безопасности. Есть контакты в других странах и требуется шифрование.

Прошу прощения что не написал все в одном сообщении. А вы не подскажете почему в случае развертывания внутри сети он проверял сертификаты, а теперь нет. Ведь в конфигурации не одной строчки не поменялось?

Вот лог Open VPN при запуске сервера:

Лог запуска

Wed Dec 12 15:44:47 2018 us=235792 Current Parameter Settings:
Wed Dec 12 15:44:47 2018 us=235792 config = ‘server.ovpn’
Wed Dec 12 15:44:47 2018 us=235792 mode = 1
Wed Dec 12 15:44:47 2018 us=235792 show_ciphers = DISABLED
Wed Dec 12 15:44:47 2018 us=235792 show_digests = DISABLED
Wed Dec 12 15:44:47 2018 us=235792 show_engines = DISABLED
Wed Dec 12 15:44:47 2018 us=235792 genkey = DISABLED
Wed Dec 12 15:44:47 2018 us=235792 key_pass_file = ‘[UNDEF]’
Wed Dec 12 15:44:47 2018 us=235792 show_tls_ciphers = DISABLED
Wed Dec 12 15:44:47 2018 us=235792 connect_retry_max = 0
Wed Dec 12 15:44:47 2018 us=235792 Connection profiles [0]:
Wed Dec 12 15:44:47 2018 us=235792 proto = udp
Wed Dec 12 15:44:47 2018 us=236791 local = ‘[UNDEF]’
Wed Dec 12 15:44:47 2018 us=236791 local_port = ‘443’
Wed Dec 12 15:44:47 2018 us=236791 remote = ‘[UNDEF]’
Wed Dec 12 15:44:47 2018 us=236791 remote_port = ‘443’
Wed Dec 12 15:44:47 2018 us=236791 remote_float = DISABLED
Wed Dec 12 15:44:47 2018 us=236791 bind_defined = DISABLED
Wed Dec 12 15:44:47 2018 us=236791 bind_local = ENABLED
Wed Dec 12 15:44:47 2018 us=236791 bind_ipv6_only = DISABLED
Wed Dec 12 15:44:47 2018 us=236791 NOTE: —mute triggered.
Wed Dec 12 15:44:47 2018 us=236791 277 variation(s) on previous 20 message(s) suppressed by —mute
Wed Dec 12 15:44:47 2018 us=236791 OpenVPN 2.4.6 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 26 2018
Wed Dec 12 15:44:47 2018 us=236791 Windows version 6.2 (Windows 8 or greater) 64bit
Wed Dec 12 15:44:47 2018 us=236791 library versions: OpenSSL 1.1.0h 27 Mar 2018, LZO 2.10
Enter Management Password:
Wed Dec 12 15:44:47 2018 us=237792 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Wed Dec 12 15:44:47 2018 us=237792 Need hold release from management interface, waiting.
Wed Dec 12 15:44:47 2018 us=714305 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Wed Dec 12 15:44:47 2018 us=816224 MANAGEMENT: CMD ‘state on’
Wed Dec 12 15:44:47 2018 us=816224 MANAGEMENT: CMD ‘log all on’
Wed Dec 12 15:44:47 2018 us=897850 MANAGEMENT: CMD ‘echo all on’
Wed Dec 12 15:44:47 2018 us=900858 MANAGEMENT: CMD ‘bytecount 5’
Wed Dec 12 15:44:47 2018 us=903866 MANAGEMENT: CMD ‘hold off’
Wed Dec 12 15:44:47 2018 us=906874 MANAGEMENT: CMD ‘hold release’
Wed Dec 12 15:44:47 2018 us=943972 Diffie-Hellman initialized with 2048 bit key
Wed Dec 12 15:44:47 2018 us=945978 TLS-Auth MTU parms [ L:1622 D:1212 EF:38 EB:0 ET:0 EL:3 ]
Wed Dec 12 15:44:47 2018 us=946983 interactive service msg_channel=0
Wed Dec 12 15:44:47 2018 us=970044 ROUTE_GATEWAY 213.xxx.xxx.xxx/255.255.255.252 I=25 HWADDR=98:de:d0:01:f3:cc
Wed Dec 12 15:44:47 2018 us=972046 open_tun
Wed Dec 12 15:44:47 2018 us=976057 MANAGEMENT: Client disconnected
Wed Dec 12 15:44:47 2018 us=977060 CreateFile failed on TAP device: \\.\Global\.tap: Too many links (errno=31)
Wed Dec 12 15:44:47 2018 us=977060 Exiting due to fatal error

Последний раз редактировалось Nagumo, 13-12-2018 в 11:39 .

OpenVPN Support Forum

Forum rules
Please use the [oconf] BB tag for openvpn Configurations. See viewtopic.php?f=30&t=21589 for an example.

4 posts • Page 1 of 1
sat99 OpenVpn Newbie Posts: 2 Joined: Mon Sep 19, 2022 4:37 pm

Error openvpn in server

Post by sat99 » Mon Sep 19, 2022 4:40 pm

Hello community!! , suddenly I have stopped being able to connect through openvpn, on the server I get this in the log, does anyone have an idea what it could be, nothing had changed before.

Mon Sep 19 18:27:11 2022 OpenVPN 2.4.6 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 26 2018
Mon Sep 19 18:27:11 2022 Windows version 6.2 (Windows 8 or greater) 64bit
Mon Sep 19 18:27:11 2022 library versions: OpenSSL 1.1.0h 27 Mar 2018, LZO 2.10
Enter Management Password:
Mon Sep 19 18:27:11 2022 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Mon Sep 19 18:27:11 2022 Need hold release from management interface, waiting.
Mon Sep 19 18:27:12 2022 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Mon Sep 19 18:27:12 2022 MANAGEMENT: CMD ‘state on’
Mon Sep 19 18:27:12 2022 MANAGEMENT: CMD ‘log all on’
Mon Sep 19 18:27:12 2022 MANAGEMENT: CMD ‘echo all on’
Mon Sep 19 18:27:12 2022 MANAGEMENT: CMD ‘bytecount 5’
Mon Sep 19 18:27:12 2022 MANAGEMENT: CMD ‘hold off’
Mon Sep 19 18:27:12 2022 MANAGEMENT: CMD ‘hold release’
Mon Sep 19 18:27:12 2022 WARNING: —ifconfig-pool-persist will not work with —duplicate-cn
Mon Sep 19 18:27:12 2022 NOTE: your local LAN uses the extremely common subnet address 192.168.0.x or 192.168.1.x. Be aware that this might create routing conflicts if you connect to the VPN server from public locations such as internet cafes that use the same subnet.
Mon Sep 19 18:27:12 2022 Note: cannot open openvpn-status.log for WRITE
Mon Sep 19 18:27:12 2022 Note: cannot open ipp.txt for READ/WRITE
Mon Sep 19 18:27:12 2022 Diffie-Hellman initialized with 2048 bit key
Mon Sep 19 18:27:12 2022 Outgoing Control Channel Authentication: Using 160 bit message hash ‘SHA1’ for HMAC authentication
Mon Sep 19 18:27:12 2022 Incoming Control Channel Authentication: Using 160 bit message hash ‘SHA1’ for HMAC authentication
Mon Sep 19 18:27:12 2022 interactive service msg_channel=324
Mon Sep 19 18:27:12 2022 ROUTE_GATEWAY 192.168.1.1/255.255.255.0 I=13 HWADDR=00:fd:45:fd:36:c0
Mon Sep 19 18:27:12 2022 open_tun
Mon Sep 19 18:27:12 2022 MANAGEMENT: Client disconnected
Mon Sep 19 18:27:12 2022 CreateFile failed on TAP device: \\.\Global\.tap: Too many links (errno=31)
Mon Sep 19 18:27:12 2022 Exiting due to fatal error

TinCanTech OpenVPN Protagonist Posts: 11128 Joined: Fri Jun 03, 2016 1:17 pm

Re: Error openvpn in server

Post by TinCanTech » Mon Sep 19, 2022 8:17 pm

Mon Sep 19, 2022 4:40 pm
on the server I get this in the log
Mon Sep 19, 2022 4:40 pm

Mon Sep 19 18:27:12 2022 Note: cannot open openvpn-status.log for WRITE
Mon Sep 19 18:27:12 2022 Note: cannot open ipp.txt for READ/WRITE

Mon Sep 19 18:27:12 2022 interactive service msg_channel=324
Mon Sep 19 18:27:12 2022 ROUTE_GATEWAY 192.168.1.1/255.255.255.0 I=13 HWADDR=00:fd:45:fd:36:c0
Mon Sep 19 18:27:12 2022 open_tun
Mon Sep 19 18:27:12 2022 MANAGEMENT: Client disconnected
Mon Sep 19 18:27:12 2022 CreateFile failed on TAP device: \\.\Global\.tap: Too many links (errno=31)
Mon Sep 19 18:27:12 2022 Exiting due to fatal error

Can you post your sanitized server config, please.
sat99 OpenVpn Newbie Posts: 2 Joined: Mon Sep 19, 2022 4:37 pm

Re: Error openvpn in server

Post by sat99 » Tue Sep 20, 2022 2:43 pm

Mon Sep 19, 2022 8:17 pm
Mon Sep 19, 2022 4:40 pm
on the server I get this in the log
Mon Sep 19, 2022 4:40 pm

Mon Sep 19 18:27:12 2022 Note: cannot open openvpn-status.log for WRITE
Mon Sep 19 18:27:12 2022 Note: cannot open ipp.txt for READ/WRITE

Can you post your sanitized server config, please.

#################################################
# Sample OpenVPN 2.0 config file for #
# multi-client server. #
# #
# This file is for the server side #
# of a many-clients one-server #
# OpenVPN configuration. #
# #
# OpenVPN also supports #
# single-machine single-machine #
# configurations (See the Examples page #
# on the web site for more info). #
# #
# This config should work on Windows #
# or Linux/BSD systems. Remember on #
# Windows to quote pathnames and use #
# double backslashes, e.g.: #
# «C:\\Program Files\\OpenVPN\\config\\foo.key» #
# #
# Comments are preceded with ‘#’ or ‘;’ #
#################################################

# Which local IP address should OpenVPN
# listen on? (optional)
;local a.b.c.d

# Which TCP/UDP port should OpenVPN listen on?
# If you want to run multiple OpenVPN instances
# on the same machine, use a different port
# number for each one. You will need to
# open up this port on your firewall.
port 55433

# TCP or UDP server?
;proto tcp
proto udp

# «dev tun» will create a routed IP tunnel,
# «dev tap» will create an ethernet tunnel.
# Use «dev tap0» if you are ethernet bridging
# and have precreated a tap0 virtual interface
# and bridged it with your ethernet interface.
# If you want to control access policies
# over the VPN, you must create firewall
# rules for the the TUN/TAP interface.
# On non-Windows systems, you can give
# an explicit unit number, such as tun0.
# On Windows, use «dev-node» for this.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
dev tun

# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel if you
# have more than one. On XP SP2 or higher,
# you may need to selectively disable the
# Windows firewall for the TAP adapter.
# Non-Windows systems usually don’t need this.
dev-node VPN

# SSL/TLS root certificate (ca), certificate
# (cert), and private key (key). Each client
# and the server must have their own cert and
# key file. The server and all clients will
# use the same ca file.
#
# See the «easy-rsa» directory for a series
# of scripts for generating RSA certificates
# and private keys. Remember to use
# a unique Common Name for the server
# and each of the client certificates.
#
# Any X509 key management system can be used.
# OpenVPN can also use a PKCS #12 formatted key file
# (see «pkcs12» directive in man page).
ca ca.crt
cert decorterra-server.crt
key decorterra-server.key # This file should be kept secret

# Diffie hellman parameters.
# Generate your own with:
# openssl dhparam -out dh2048.pem 2048
dh dh2048.pem

# Network topology
# Should be subnet (addressing via IP)
# unless Windows clients v2.0.9 and lower have to
# be supported (then net30, i.e. a /30 per client)
# Defaults to net30 (not recommended)
;topology subnet

# Configure server mode and supply a VPN subnet
# for OpenVPN to draw client addresses from.
# The server will take 10.8.0.1 for itself,
# the rest will be made available to clients.
# Each client will be able to reach the server
# on 10.8.0.1. Comment this line out if you are
# ethernet bridging. See the man page for more info.
server 10.8.100.0 255.255.255.0

# Maintain a record of client virtual IP address
# associations in this file. If OpenVPN goes down or
# is restarted, reconnecting clients can be assigned
# the same virtual IP address from the pool that was
# previously assigned.
ifconfig-pool-persist ipp.txt

# Configure server mode for ethernet bridging.
# You must first use your OS’s bridging capability
# to bridge the TAP interface with the ethernet
# NIC interface. Then you must manually set the
# IP/netmask on the bridge interface, here we
# assume 10.8.0.4/255.255.255.0. Finally we
# must set aside an IP range in this subnet
# (start=10.8.0.50 end=10.8.0.100) to allocate
# to connecting clients. Leave this line commented
# out unless you are ethernet bridging.
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100

# Configure server mode for ethernet bridging
# using a DHCP-proxy, where clients talk
# to the OpenVPN server-side DHCP server
# to receive their IP address allocation
# and DNS server addresses. You must first use
# your OS’s bridging capability to bridge the TAP
# interface with the ethernet NIC interface.
# Note: this mode only works on clients (such as
# Windows), where the client-side TAP adapter is
# bound to a DHCP client.
;server-bridge

# Push routes to the client to allow it
# to reach other private subnets behind
# the server. Remember that these
# private subnets will also need
# to know to route the OpenVPN client
# address pool (10.8.0.0/255.255.255.0)
# back to the OpenVPN server.
;push «route 192.168.10.0 255.255.255.0»
;push «route 192.168.20.0 255.255.255.0»

# To assign specific IP addresses to specific
# clients or if a connecting client has a private
# subnet behind it that should also have VPN access,
# use the subdirectory «ccd» for client-specific
# configuration files (see man page for more info).

# EXAMPLE: Suppose the client
# having the certificate common name «Thelonious»
# also has a small subnet behind his connecting
# machine, such as 192.168.40.128/255.255.255.248.
# First, uncomment out these lines:
;client-config-dir ccd
;route 192.168.40.128 255.255.255.248
# Then create a file ccd/Thelonious with this line:
# iroute 192.168.40.128 255.255.255.248
# This will allow Thelonious’ private subnet to
# access the VPN. This example will only work
# if you are routing, not bridging, i.e. you are
# using «dev tun» and «server» directives.

# EXAMPLE: Suppose you want to give
# Thelonious a fixed VPN IP address of 10.9.0.1.
# First uncomment out these lines:
;client-config-dir ccd
;route 10.9.0.0 255.255.255.252
# Then add this line to ccd/Thelonious:
# ifconfig-push 10.9.0.1 10.9.0.2

# Suppose that you want to enable different
# firewall access policies for different groups
# of clients. There are two methods:
# (1) Run multiple OpenVPN daemons, one for each
# group, and firewall the TUN/TAP interface
# for each group/daemon appropriately.
# (2) (Advanced) Create a script to dynamically
# modify the firewall in response to access
# from different clients. See man
# page for more info on learn-address script.
;learn-address ./script

# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN, causing
# all IP traffic such as web browsing and
# and DNS lookups to go through the VPN
# (The OpenVPN server machine may need to NAT
# or bridge the TUN/TAP interface to the internet
# in order for this to work properly).
;push «redirect-gateway def1 bypass-dhcp»

# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses. CAVEAT:
# http://openvpn.net/faq.html#dhcpcaveats
# The addresses below refer to the public
# DNS servers provided by opendns.com.
;push «dhcp-option DNS 208.67.222.222»
;push «dhcp-option DNS 208.67.220.220»

# Uncomment this directive to allow different
# clients to be able to «see» each other.
# By default, clients will only see the server.
# To force clients to only see the server, you
# will also need to appropriately firewall the
# server’s TUN/TAP interface.
;client-to-client

# Uncomment this directive if multiple clients
# might connect with the same certificate/key
# files or common names. This is recommended
# only for testing purposes. For production use,
# each client should have its own certificate/key
# pair.
#
# IF YOU HAVE NOT GENERATED INDIVIDUAL
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
# EACH HAVING ITS OWN UNIQUE «COMMON NAME»,
# UNCOMMENT THIS LINE OUT.
duplicate-cn

# The keepalive directive causes ping-like
# messages to be sent back and forth over
# the link so that each side knows when
# the other side has gone down.
# Ping every 10 seconds, assume that remote
# peer is down if no ping received during
# a 120 second time period.
keepalive 10 120

# For extra security beyond that provided
# by SSL/TLS, create an «HMAC firewall»
# to help block DoS attacks and UDP port flooding.
#
# Generate with:
# openvpn —genkey —secret ta.key
#
# The server and each client must have
# a copy of this key.
# The second parameter should be ‘0’
# on the server and ‘1’ on the clients.
tls-auth ta.key 0 # This file is secret

# Select a cryptographic cipher.
# This config item must be copied to
# the client config file as well.
# Note that v2.4 client/server will automatically
# negotiate AES-256-GCM in TLS mode.
# See also the ncp-cipher option in the manpage
cipher AES-256-CBC

# Enable compression on the VPN link and push the
# option to the client (v2.4+ only, for earlier
# versions see below)
;compress lz4-v2
;push «compress lz4-v2»

# For compression compatible with older clients use comp-lzo
# If you enable it here, you must also
# enable it in the client config file.
;comp-lzo

# The maximum number of concurrently connected
# clients we want to allow.
;max-clients 100

# It’s a good idea to reduce the OpenVPN
# daemon’s privileges after initialization.
#
# You can uncomment this out on
# non-Windows systems.
;user nobody
;group nobody

# The persist options will try to avoid
# accessing certain resources on restart
# that may no longer be accessible because
# of the privilege downgrade.
persist-key
persist-tun

# Output a short status file showing
# current connections, truncated
# and rewritten every minute.
status openvpn-status.log

# By default, log messages will go to the syslog (or
# on Windows, if running as a service, they will go to
# the «\Program Files\OpenVPN\log» directory).
# Use log or log-append to override this default.
# «log» will truncate the log file on OpenVPN startup,
# while «log-append» will append to it. Use one
# or the other (but not both).
;log openvpn.log
;log-append openvpn.log

# Set the appropriate level of log
# file verbosity.
#
# 0 is silent, except for fatal errors
# 4 is reasonable for general usage
# 5 and 6 can help to debug connection problems
# 9 is extremely verbose
verb 3

# Silence repeating messages. At most 20
# sequential messages of the same message
# category will be output to the log.
;mute 20

# Notify the client that when the server restarts so it
# can automatically reconnect.
explicit-exit-notify 1

We’re here to help.

OpenVPN will display the error message «AUTH: Received control message: AUTH_FAILED» in the connection log if the OpenVPN server rejects a connection during the authentication stage. While this is typically the result of an incorrect username and/or password, an OpenVPN server may also reject a VPN connection during the authentication stage for other reasons as well.

It should be noted that in some instances seeing an «AUTH_FAILED» message in the log is normal and does not indicate a problem. For example, if using dynamic two-factor authentication (where the OpenVPN server prompts you for additional credentials, such as a one-time password) an AUTH_FAILED message in the log is normal and part of the process. It should only be considered a problem if the VPN connection is unable to connect.

If you are unable to connect your VPN Connection, and you’re seeing an «AUTH: Received control message: AUTH_FAILED» message in the connection log, then in the first instance you should contact your VPN Provider. An AUTH_FAILED message comes from the OpenVPN server and indicates it is rejecting your authentication attempt. Only your VPN Provider can tell you exactly why this is occurring (they should be able to check their server logs). If you are unsure of who your VPN Provider is please see How Do I Find Out Who My VPN Provider Is?

Common causes of an AUTH_FAILED message include:

The OpenVPN server is rejecting the username and/or password you’re using. Make sure that the details you’re entering are correct, and that your account with your VPN Provider is active and allowed to authenticate. It is recommended you get in contact with your VPN Provider in this instance to check your account is still valid and the username and password being used are correct.

The OpenVPN server is rejecting your connection attempt as the two-factor credentials being used are invalid or missing. If your VPN connection requires that you authenticate using two-factor authentication (such as a one-time password, authenticator code, etc.) make sure it is being entered, it is correct, and it’s not expired. If you’re unsure whether you need to enter two-factor credentials, please get in contact with your VPN Provider.

The OpenVPN is rejecting your connection attempt as it limits the number of active connections. Some OpenVPN servers may be configured to enforce a limit on number of connections that can be active at the same time. If this enforcement is done in an authentication script or plugin on the server, then you will receive an AUTH_FAILED message if the server believes there are too many active connections. This could be enforced on a per-user basis (for example only a single connection is allowed per user) or server wide (for example the server may only allow a total of 10 connections at a time among all users). In some cases an OpenVPN server may not immediately notice a VPN connection has been disconnected, and so you may need to wait several minutes before attempting to connect. Please get in contact with your VPN Provider to check whether any connection limits are being reached.

The OpenVPN server is rejecting your connection’s certificate. This can be the case if the OpenVPN server accepts the certificate for the initial connection, but then rejects it in an authentication script or plugin. You should contact your VPN Provider to see whether you need to update your VPN connection configuration.

Your connection’s configuration details may be incorrect or out of date. VPN Providers may periodically update their VPN servers, so you may need to download updated connections to import. You will need to get in contact with your VPN Provider to ensure your configuration details are correct and up to date.

There is a problem with the OpenVPN server. In some cases there may be a problem with the OpenVPN server that is causing authentication attempts to fail. For example, back-end authentication systems might be down or unavailable. Please get in contact with your VPN Provider to ensure that the OpenVPN server is available and not experiencing any problems.

Как запустить сервер OpenVPN на Windows?

Wed Jul 10 12:49:40 2019 OpenVPN 2.4.7 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 25 2019
Wed Jul 10 12:49:40 2019 Windows version 6.2 (Windows 8 or greater) 64bit
Wed Jul 10 12:49:40 2019 library versions: OpenSSL 1.1.0j 20 Nov 2018, LZO 2.10
Enter Management Password:
Wed Jul 10 12:49:40 2019 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Wed Jul 10 12:49:40 2019 Need hold release from management interface, waiting.
Wed Jul 10 12:49:41 2019 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Wed Jul 10 12:49:41 2019 MANAGEMENT: CMD ‘state on’
Wed Jul 10 12:49:41 2019 MANAGEMENT: CMD ‘log all on’
Wed Jul 10 12:49:41 2019 MANAGEMENT: CMD ‘echo all on’
Wed Jul 10 12:49:41 2019 MANAGEMENT: CMD ‘bytecount 5’
Wed Jul 10 12:49:41 2019 MANAGEMENT: CMD ‘hold off’
Wed Jul 10 12:49:41 2019 MANAGEMENT: CMD ‘hold release’
Wed Jul 10 12:49:41 2019 NOTE: when bridging your LAN adapter with the TAP adapter, note that the new bridge adapter will often take on its own IP address that is different from what the LAN adapter was previously set to
Wed Jul 10 12:49:41 2019 Diffie-Hellman initialized with 2048 bit key
Wed Jul 10 12:49:41 2019 interactive service msg_channel=0
Wed Jul 10 12:49:41 2019 open_tun
Wed Jul 10 12:49:41 2019 MANAGEMENT: Client disconnected
Wed Jul 10 12:49:41 2019 CreateFile failed on TAP device: \\.\Global\.tap: Too many links (errno=31)
Wed Jul 10 12:49:41 2019 Exiting due to fatal error

Как исправить ошибку и запустить сервер OpenVPN. Заранее спасибо за полный ответ!

Ps: В интернете на форумах задают такой вопрос но ответа на него нету

Вопрос задан более трёх лет назад
2916 просмотров

2 комментария

Простой 2 комментария

Too many links errno 31 openvpn как исправить