Ошибка connecting to management interface failed openvpn - Ремонт и установка крупной бытовой техники

honor_the_vpn: OpenVpn Newbie; Posts: 7; Joined: Wed May 19, 2021 9:07 pm

Connecting to management Interface failed error on Windows 10

Hello everyone,

In March In iused the OpenVPN 2.5.1-l601 amd64 installer to install the OpenVPN client and had been connecting to VPN successfully for the next two months. On May 13 I ran Windows updates and installed the kb5003173 update (https://support.microsoft.com/en-us/top … e249f52527). After rebooting I was no longer able to connect to VPN.

I continually got the following error: Connecting to management Interface failed. (the following screenshot shows a different version of the client because i found that screenshot online)

When I look at the verb 3 logs I see the following:

Code: Select all

2021-05-13 14:32:20 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.
2021-05-13 14:32:20 OpenVPN 2.5.1 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Feb 24 2021
2021-05-13 14:32:20 Windows version 10.0 (Windows 10 or greater) 64bit
2021-05-13 14:32:20 library versions: OpenSSL 1.1.1j  16 Feb 2021, LZO 2.10
Enter Management Password:
2021-05-13 14:32:20 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
2021-05-13 14:32:20 Need hold release from management interface, waiting...
2021-05-13 14:32:21 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
2021-05-13 14:32:21 MANAGEMENT: CMD 'state on'
2021-05-13 14:32:21 MANAGEMENT: CMD 'log all on'
2021-05-13 14:32:21 MANAGEMENT: CMD 'echo all on'
2021-05-13 14:32:21 MANAGEMENT: CMD 'bytecount 5'
2021-05-13 14:32:21 MANAGEMENT: CMD 'hold off'
2021-05-13 14:32:21 MANAGEMENT: CMD 'hold release'
2021-05-13 14:32:23 MANAGEMENT: CMD 'username "Auth" "*****"'
2021-05-13 14:32:23 MANAGEMENT: Client disconnected
2021-05-13 14:32:43 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
2021-05-13 14:32:46 MANAGEMENT: Client disconnected

I found this on the forums but its several years old and using an earlier version of the client- https://community.openvpn.net/openvpn/ticket/1051

Has anyone seen the «Connecting to management Interface failed» on a modern version of Windows 10?

Last edited by honor_the_vpn on Thu May 20, 2021 1:18 am, edited 2 times in total.

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

Re: Connecting to management Interface failed error on Windows 10

Post

by TinCanTech » Thu May 20, 2021 1:01 am

honor_the_vpn wrote: ↑

Thu May 20, 2021 12:04 am

I continually got the following error: Connecting to management Interface failed.

Actually, your log shows that you were disconnected not a failure to connect.

honor_the_vpn: OpenVpn Newbie; Posts: 7; Joined: Wed May 19, 2021 9:07 pm

Re: Connecting to management Interface failed error on Windows 10

Post

by honor_the_vpn » Thu May 20, 2021 1:20 am

TinCanTech wrote: ↑

Thu May 20, 2021 1:01 am

honor_the_vpn wrote: ↑

Thu May 20, 2021 12:04 am

I continually got the following error: Connecting to management Interface failed.

Actually, your log shows that you were disconnected not a failure to connect.

Thanks TinCanTech.

I found a screenshot online to show the error I was referring to:

That screenshot was not from my machine but my machine is saying the same thing. The error is saying that connecting to the management interface failed.

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

Re: Connecting to management Interface failed error on Windows 10

Post

by TinCanTech » Thu May 20, 2021 11:18 am

Your log file is more important than a random screen shot you found online …

Try again or re-install or something.

honor_the_vpn: OpenVpn Newbie; Posts: 7; Joined: Wed May 19, 2021 9:07 pm

Re: Connecting to management Interface failed error on Windows 10

Post

by honor_the_vpn » Fri May 21, 2021 4:46 pm

The screenshot was not random. I included it because that is the same exact response I get with my client.

Before submitting my original post I already tried uninstalling and reinstalling. I also tried uninstalling an earlier version, 2.4.9. In both cases my vpn connection attempting is erroring/disconnecting with exit code 1 without event prompting me for credentials.

Has anyone seen anything like this?

honor_the_vpn: OpenVpn Newbie; Posts: 7; Joined: Wed May 19, 2021 9:07 pm

Re: Connecting to management Interface failed error on Windows 10

Post

by honor_the_vpn » Fri May 21, 2021 5:18 pm

I uninstalled 2.4.9, rebooted, and reinstalled 2.5.1. When I tried to launch the connection it did not prompt me for credentials and I got the following logs which repeared infinitely until I finally hit the disconnect button:

Code: Select all

2021-05-21 13:09:16 us=526384 OpenVPN 2.5.1 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Feb 24 2021
2021-05-21 13:09:16 us=526384 Windows version 10.0 (Windows 10 or greater) 64bit
2021-05-21 13:09:16 us=526384 library versions: OpenSSL 1.1.1j  16 Feb 2021, LZO 2.10
Enter Management Password:
2021-05-21 13:09:16 us=526384 WE_INIT maxevents=1 flags=0x00000002
2021-05-21 13:09:16 us=526384 WE_INIT maxevents=1 capacity=2
2021-05-21 13:09:16 us=526384 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
2021-05-21 13:09:16 us=526384 Need hold release from management interface, waiting...
2021-05-21 13:09:16 us=526384 WE_CTL n=0 ev=0000000000F28280 rwflags=0x0001 arg=0x0
2021-05-21 13:09:16 us=526384 WE_WAIT enter n=1 to=0
2021-05-21 13:09:16 us=526384 [0] ev=0000000000000160 rwflags=0x0001 arg=0x0
2021-05-21 13:09:16 us=526384 WE_CTL n=0 ev=0000000000F28280 rwflags=0x0001 arg=0x0
2021-05-21 13:09:16 us=526384 WE_WAIT enter n=1 to=1000
2021-05-21 13:09:16 us=526384 [0] ev=0000000000000160 rwflags=0x0001 arg=0x0
2021-05-21 13:09:16 us=542007 WE_WAIT leave rwflags=0x0001 arg=0x0
2021-05-21 13:09:16 us=542007 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
2021-05-21 13:09:16 us=542007 WE_CTL n=0 ev=0000000000F28280 rwflags=0x0001 arg=0x0
2021-05-21 13:09:16 us=542007 WE_WAIT enter n=1 to=0
2021-05-21 13:09:16 us=542007 [0] ev=0000000000000160 rwflags=0x0001 arg=0x0
2021-05-21 13:09:16 us=542007 WE_CTL n=0 ev=0000000000F28280 rwflags=0x0001 arg=0x0
2021-05-21 13:09:16 us=542007 WE_WAIT enter n=1 to=1000
2021-05-21 13:09:16 us=542007 [0] ev=0000000000000160 rwflags=0x0001 arg=0x0
2021-05-21 13:09:16 us=546512 WE_WAIT leave rwflags=0x0001 arg=0x0
2021-05-21 13:09:16 us=546512 WE_CTL n=0 ev=0000000000F28280 rwflags=0x0001 arg=0x0
2021-05-21 13:09:16 us=546512 WE_WAIT enter n=1 to=0
2021-05-21 13:09:16 us=546512 [0] ev=0000000000000160 rwflags=0x0001 arg=0x0
2021-05-21 13:09:16 us=546512 WE_CTL n=0 ev=0000000000F28280 rwflags=0x0001 arg=0x0
2021-05-21 13:09:16 us=546512 WE_WAIT enter n=1 to=1000
2021-05-21 13:09:16 us=546512 [0] ev=0000000000000160 rwflags=0x0001 arg=0x0
2021-05-21 13:09:16 us=662478 WE_WAIT leave rwflags=0x0001 arg=0x0
2021-05-21 13:09:16 us=662478 MANAGEMENT: CMD 'state on'
2021-05-21 13:09:16 us=662478 WE_CTL n=0 ev=0000000000F28280 rwflags=0x0001 arg=0x0
2021-05-21 13:09:16 us=662478 WE_WAIT enter n=1 to=0
...
...
...
2021-05-21 13:13:35 us=751504 WE_CTL n=0 ev=0000000000F28280 rwflags=0x0001 arg=0x0
2021-05-21 13:13:35 us=751504 WE_WAIT enter n=1 to=1000
2021-05-21 13:13:35 us=751504 [0] ev=0000000000000160 rwflags=0x0001 arg=0x0
2021-05-21 13:13:36 us=754350 WE_CTL n=0 ev=0000000000F28280 rwflags=0x0001 arg=0x0
2021-05-21 13:13:36 us=754350 WE_WAIT enter n=1 to=1000
2021-05-21 13:13:36 us=754350 [0] ev=0000000000000160 rwflags=0x0001 arg=0x0
2021-05-21 13:13:37 us=756769 Signal received from management interface, exiting
2021-05-21 13:13:37 us=756769 PKCS#11: pkcs11_terminate - entered
2021-05-21 13:13:37 us=765263 PKCS#11: pkcs11_terminate - return

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

Re: Connecting to management Interface failed error on Windows 10

Post

by TinCanTech » Fri May 21, 2021 6:24 pm

Please add your client config file to this thread.

honor_the_vpn: OpenVpn Newbie; Posts: 7; Joined: Wed May 19, 2021 9:07 pm

Re: Connecting to management Interface failed error on Windows 10

Post

by honor_the_vpn » Mon May 24, 2021 5:33 pm

This is my config (address & certificate info have been redacted). The config was not changed between when the VPN was working and when it stopped working. There were no changes to the server during that period and no one else on my team has reported a problem like this.

Code: Select all

client
dev tun
proto udp
remote ***.***.***.*** 1194
resolv-retry 1
nobind
persist-key
persist-tun
remote-cert-tls server
auth SHA512
cipher AES-256-CBC
auth-user-pass
verb 10
keepalive 10 60
<ca>
-----BEGIN CERTIFICATE-----
...
...
...
-----END CERTIFICATE-----
</ca>
<cert>
-----BEGIN CERTIFICATE-----
...
...
...
-----END CERTIFICATE-----
</cert>
<key>
-----BEGIN PRIVATE KEY-----
...
...
...
-----END PRIVATE KEY-----
</key>
<tls-auth>
-----BEGIN OpenVPN Static key V1-----
...
...
...
-----END OpenVPN Static key V1-----
</tls-auth>

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

Re: Connecting to management Interface failed error on Windows 10

Post

by TinCanTech » Mon May 24, 2021 6:27 pm

You don’t want to use verb 10, use verb 4 then read your log.

honor_the_vpn: OpenVpn Newbie; Posts: 7; Joined: Wed May 19, 2021 9:07 pm

Re: Connecting to management Interface failed error on Windows 10

Post

by honor_the_vpn » Mon May 24, 2021 8:29 pm

So I figured out the issue and I’m embarrassed to say that it has nothing to do with OpenVPN or the Windows update. I recently migrated from one password manager to another. During the migration process it looks like the export/import added a character my OpenVPN password but I hadn’t noticed that due to the length of the password.
**facepalm**

honor_the_vpn: OpenVpn Newbie; Posts: 7; Joined: Wed May 19, 2021 9:07 pm

Re: Connecting to management Interface failed error on Windows 10

Post

by honor_the_vpn » Mon May 24, 2021 8:34 pm

My embarrassment aside I appreciate you taking the time to respond to my thread @TinCanTech.

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

Re: Connecting to management Interface failed error on Windows 10

Post

by TinCanTech » Tue May 25, 2021 12:54 am

There is no need to feel embarrassment, with a little guidance you solved the problem yourself.

And then you also fed back to the community, Kudos

We all have to start somewhere.

Источник

Comments

selvanair

added a commit
to selvanair/openvpn
that referenced
this issue

Jan 29, 2020

Check the config file location and command line options first
and membership in OpenVPNAdministrators group after that as
the latter could be a slow process for active directory users.

When connection to domain controllers is poor or unavailable, checking
the group membership is slow and causes timeouts in the GUI (Trac
1051). However, in cases where the config is in the global directory,
no group membership check should be required. The re-ordering here
avoids the redundant check in such cases.

In addition to this, its also proposed to improve the timeout handling
in the GUI, but this change is still useful as it will eliminate the
problem for many users.

Also see: OpenVPN/openvpn-gui#332

Signed-off-by: Selva Nair <selva.nair@gmail.com>

selvanair

added a commit
to selvanair/openvpn
that referenced
this issue

Jan 31, 2020

Check the config file location and command line options first
and membership in OpenVPNAdministrators group after that as
the latter could be a slow process for active directory users.

When connection to domain controllers is poor or unavailable, checking
the group membership is slow and causes timeouts in the GUI (Trac
1051). However, in cases where the config is in the global directory,
no group membership check should be required. The re-ordering here
avoids the redundant check in such cases.

In addition to this, its also proposed to improve the timeout handling
in the GUI, but this change is still useful as it should completely
eliminate the timeout issue for many users.

Also see: OpenVPN/openvpn-gui#332

Signed-off-by: Selva Nair <selva.nair@gmail.com>

selvanair

added a commit
to selvanair/openvpn
that referenced
this issue

Feb 9, 2020

Check the config file location and command line options first
and membership in OpenVPNAdministrators group after that as
the latter could be a slow process for active directory users.

When connection to domain controllers is poor or unavailable, checking
the group membership is slow and causes timeouts in the GUI (Trac
1051). However, in cases where the config is in the global directory,
no group membership check should be required. The re-ordering here
avoids the redundant check in such cases.

In addition to this, its also proposed to improve the timeout handling
in the GUI, but this change is still useful as it should completely
eliminate the timeout issue for many users.

v3: Do not send error message to the client pipe from ValidateOptions().
Instead save the error and send it on only if user authorization also
fails.

Also see: OpenVPN/openvpn-gui#332

Signed-off-by: Selva Nair <selva.nair@gmail.com>

selvanair

added a commit
to selvanair/openvpn
that referenced
this issue

Feb 10, 2020

Check the config file location and command line options first
and membership in OpenVPNAdministrators group after that as
the latter could be a slow process for active directory users.

When connection to domain controllers is poor or unavailable, checking
the group membership is slow and causes timeouts in the GUI (Trac
1051). However, in cases where the config is in the global directory,
no group membership check should be required. The re-ordering here
avoids the redundant check in such cases.

In addition to this, its also proposed to improve the timeout handling
in the GUI, but this change is still useful as it should completely
eliminate the timeout issue for many users.

v3: Do not send error message to the client pipe from ValidateOptions().
Instead save the error and send it on only if user authorization also
fails. The error buffer size is increased to 512 wide chars as these
messages could get long in some cases and may get truncated otherwise.

Also see: OpenVPN/openvpn-gui#332

Signed-off-by: Selva Nair <selva.nair@gmail.com>

cron2

pushed a commit
to OpenVPN/openvpn
that referenced
this issue

Feb 10, 2020

Check the config file location and command line options first
and membership in OpenVPNAdministrators group after that as
the latter could be a slow process for active directory users.

When connection to domain controllers is poor or unavailable, checking
the group membership is slow and causes timeouts in the GUI (Trac
1051). However, in cases where the config is in the global directory,
no group membership check should be required. The re-ordering here
avoids the redundant check in such cases.

In addition to this, its also proposed to improve the timeout handling
in the GUI, but this change is still useful as it should completely
eliminate the timeout issue for many users.

v3: Do not send error message to the client pipe from ValidateOptions().
Instead save the error and send it on only if user authorization also
fails. The error buffer size is increased to 512 wide chars as these
messages could get long in some cases and may get truncated otherwise.

Also see: OpenVPN/openvpn-gui#332

Signed-off-by: Selva Nair <selva.nair@gmail.com>
Acked-by: Lev Stipakov <lstipakov@gmail.com>
Message-Id: <1581309200-27870-1-git-send-email-selva.nair@gmail.com>
URL: https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg19388.html
Signed-off-by: Gert Doering <gert@greenie.muc.de>

selvanair

added a commit
to selvanair/openvpn
that referenced
this issue

Feb 18, 2020

Check the config file location and command line options first
and membership in OpenVPNAdministrators group after that as
the latter could be a slow process for active directory users.

When connection to domain controllers is poor or unavailable, checking
the group membership is slow and causes timeouts in the GUI (Trac
1051). However, in cases where the config is in the global directory,
no group membership check should be required. The re-ordering here
avoids the redundant check in such cases.

In addition to this, its also proposed to improve the timeout handling
in the GUI, but this change is still useful as it should completely
eliminate the timeout issue for many users.

v3: Do not send error message to the client pipe from ValidateOptions().
Instead save the error and send it on only if user authorization also
fails. The error buffer size is increased to 512 wide chars as these
messages could get long in some cases and may get truncated otherwise.

Also see: OpenVPN/openvpn-gui#332

Signed-off-by: Selva Nair <selva.nair@gmail.com>

cron2

pushed a commit
to OpenVPN/openvpn
that referenced
this issue

Mar 8, 2020

Check the config file location and command line options first
and membership in OpenVPNAdministrators group after that as
the latter could be a slow process for active directory users.

When connection to domain controllers is poor or unavailable, checking
the group membership is slow and causes timeouts in the GUI (Trac
1051). However, in cases where the config is in the global directory,
no group membership check should be required. The re-ordering here
avoids the redundant check in such cases.

In addition to this, its also proposed to improve the timeout handling
in the GUI, but this change is still useful as it should completely
eliminate the timeout issue for many users.

v3: Do not send error message to the client pipe from ValidateOptions().
Instead save the error and send it on only if user authorization also
fails. The error buffer size is increased to 512 wide chars as these
messages could get long in some cases and may get truncated otherwise.

Also see: OpenVPN/openvpn-gui#332

Signed-off-by: Selva Nair <selva.nair@gmail.com>
Acked-by: Lev Stipakov <lstipakov@gmail.com>
Message-Id: <1582077261-9467-1-git-send-email-selva.nair@gmail.com>
URL: https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg19474.html
Signed-off-by: Gert Doering <gert@greenie.muc.de>

Источник

by Loredana Harsana

Loredana is a passionate writer with a keen interest in PC software and technology. She started off writing about mobile phones back when Samsung Galaxy S II was… read more

Updated on March 28, 2022

OpenVPN users reported getting the Connecting to management interface failed error and it seems to be due to the core process.
You can download an executable file that will try to reconnect to the management interface and fix any error that pops up.
Don’t miss out on our section on why you should always use a VPN.

github-openvpn connecting to management interface failed

XINSTALL BY CLICKING THE DOWNLOAD FILE

To fix Windows PC system issues, you will need a dedicated tool
Fortect is a tool that does not simply cleans up your PC, but has a repository with several millions of Windows System files stored in their initial version. When your PC encounters a problem, Fortect will fix it for you, by replacing bad files with fresh versions. To fix your current PC issue, here are the steps you need to take:

Download Fortect and install it on your PC.
Start the tool’s scanning process to look for corrupt files that are the source of your problem
Right-click on Start Repair so the tool could start the fixing algorythm

Fortect has been downloaded by 0 readers this month.

OpenVPN implements OSI layer 2 or 3 secure network extensions using the industry-standard SSL/TLS protocol, as well as supports flexible client authentication methods based on certificates, smart cards, and/or username/password credentials.

It is a free and open-source software project developed by the Linux Foundation that can be accessed at any point in time. However, lately, it has been reported that the Connecting to management interface failed error popped up on users’ screens.

Thus, we will show you today how to fix the Connecting to management interface failed error, right after we see how OpenVPN works. Follow along!

How does OpenVPN work?

A Virtual Private Network (VPN) connects your company’s internet connection to your private network over the public internet, allowing you to work more securely and efficiently.

Protection through a virtual private network is an important component of a layered security protocol that is vital for securing both company data and an employee’s personal information.

OpenVPN products provide an almost limitless number of configuration choices. Small and medium-sized businesses (SMEs) and enterprises of all sizes use OpenVPN Cloud or OpenVPN Access Server to configure the exact access and granularity that they require for their organization.

The term Open-source refers to software that is freely available to the public. OpenVPN makes use of virtual private network technology to secure and encrypt data delivered over the internet. The key exchange protocol for its unique VPN protocol is SSL/TLS.

With more than 60 million downloads since its inception in 2001, it has established itself as the de facto standard in the open-source networking field.

What can I do when Connecting to management interface failed?

1. Retry on management timeout

Fortunately, users found a way to fix the Connecting to management interface failed error. Thus head to Github repository with the file you need to download.
Now scroll down and click on the link named openvpn-gui-timeout.exe in order to download it.
Once the file is downloaded, double-click on it to run it and wait for it to complete the process. What the file will do is retry to connect to management and fix any error that pops up, including the Connecting to management interface failed error.

That’s it. Sometimes, errors can be fixed by downloading executable files that attempt to fix the error at hand. Fortunately, this was the case for you too, without having to complicate things.

Read more about this topic

5+ best VPNs for Windows 10 PCs
Top 3 best VPN options fully compatible with Windows 11
NordVPN not working in Windows 11? Fix it now

2. Use another VPN service

VPNs have quickly established themselves as essential software solutions for customers who want to secure their online privacy while also protecting their devices from hackers. In addition, we believe that Private Internet Access (PIA) is the greatest in the industry.

A super-intuitive user interface wraps around PIA VPN, making it easy to use on a variety of platforms such as Windows, Mac OS X, Android, Linux, and even straight in your web browser.

No matter whether you’re securely browsing the web, downloading torrents or streaming video, or gaming with buddies, it provides superb connection speeds. If you get sick of the Connecting to management interface failed error, we recommend that you check out PIA.

⇒ Get PIA

Why should I use a VPN?

The primary function of a virtual private network is to conceal your internet activity. It is used to protect against hackers and snoopers on public networks, but it may also be used to hide your IP address, browsing activities, and personal data on any Wi-Fi network, including those at home.

And the more digitized our lives become, the more likely it is that our personal information may be compromised.

vpn connecting to management interface failed

Someone could be watching or following your online activities at any time, from your ISP (internet service provider) to organizations gathering data to monetize or sell to hackers attempting to steal your personal information for malevolent purposes.

Hackers can simply intercept and read anything you send and receive when you are connected to an unsecured public Wi-Fi network.

While the majority of your internet traffic is unimportant, it may contain vital information such as your bank account data, credit card numbers, or login credentials. Attackers cast wide nets, which is why using free public Wi-Fi puts you at greater risk of being attacked.

Источник

Студворк — интернет-сервис помощи студентам

Хочу подрубить впн. Импортировал файл «клиент». При попытке подключения выдаёт ошибку и посылает смотреть логи. Как решить проблему?
Вот логи:

Кликните здесь для просмотра всего текста

Options error: —ca fails with ‘ca.crt’: No such file or directory (errno=2)
Options error: —cert fails with ‘client.crt’: No such file or directory (errno=2)
Wed May 09 00:56:27 2018 WARNING: cannot stat file ‘client.key’: No such file or directory (errno=2)
Options error: —key fails with ‘client.key’
Wed May 09 00:56:27 2018 WARNING: cannot stat file ‘ta.key’: No such file or directory (errno=2)
Options error: —tls-auth fails with ‘ta.key’: No such file or directory (errno=2)
Options error: Please correct these errors.
Use —help for more information.

Добавлено через 30 минут
Что то я наделал и ошибка сменилась на «Не удалось подключиться к client»
Логи перезаписались, изменилась только дата

Добавлено через 5 минут
мда, я как обычно невнимателен. Нашёл в чём проблема.

Источник

OpenVPN не работает в Windows 10? Вот что делать

OpenVPN — это VPN-клиент с открытым исходным кодом, который вы можете использовать с различными провайдерами VPN. Пока ваш провайдер VPN поддерживает протокол OpenVPN TCP или UDP, вы можете установить соединение OpenVPN.

Вы можете запустить клиент OpenVPN со сценариями и настроить соединения через его файлы настроек.

Однако OpenVPN все еще может столкнуться с некоторыми трудностями. Это несколько разрешений, которые могут исправить соединения OpenVPN в Windows 10.

Как я могу исправить проблемы запуска OpenVPN в Windows 10?

Отключить брандмауэр Windows
Отключить стороннее антивирусное программное обеспечение
Перезапустите адаптер TAP
Переустановите и обновите драйвер TAP-Windows
Проверьте, работает ли служба DHCP
Очистить DNS
Сброс Winsock

1. Отключите брандмауэр Windows

Брандмауэры и VPN не всегда хорошо сочетаются друг с другом. Брандмауэр Windows может заблокировать ваше соединение OpenVPN, если вы не настроили исходящие порты .

Лучший способ проверить, так ли это, — отключить брандмауэр Windows. Вот как вы можете отключить брандмауэр в Windows 10:

Нажмите кнопку Cortana на панели задач, чтобы открыть это приложение.
Введите ключевое слово «Брандмауэр Windows» в поле поиска и выберите, чтобы открыть Брандмауэр Защитника Windows .

Нажмите Включить или выключить брандмауэр Защитника Windows, чтобы открыть настройки, показанные на снимке ниже.

включить брандмауэр Windows

Выберите оба параметра « Отключить брандмауэр Защитника Windows» .
Нажмите кнопку ОК .

2. Отключите стороннее антивирусное программное обеспечение

Также обратите внимание, что стороннее антивирусное программное обеспечение может препятствовать VPN с их собственными брандмауэрами. Таким образом, отключение сторонних антивирусных утилит может также помочь исправить соединение OpenVPN.

Вы можете временно отключить некоторые антивирусные программы, выбрав отключить настройки в их контекстных меню. Или вы также можете удалить программное обеспечение из автозагрузки Windows следующим образом:

Щелкните правой кнопкой мыши панель задач Windows и выберите « Диспетчер задач» в открывшемся контекстном меню.
Откройте вкладку «Автозагрузка» в окне «Диспетчер задач».

Выберите антивирусное программное обеспечение и нажмите кнопку « Отключить» .
Затем перезагрузите свой ноутбук или рабочий стол.

Если вы хотите узнать, как добавлять или удалять загрузочные приложения в Windows 10, ознакомьтесь с этим простым руководством . Кроме того, если вы не можете открыть диспетчер задач в Windows 10, не беспокойтесь. У нас есть правильное решение для вас.

3. Перезапустите адаптер TAP.

Добавление программного обеспечения OpenVPN в Windows также добавляет адаптер TAP-Windows. В одном сообщении об ошибке OpenVPN говорится: « Все адаптеры TAP-Windows в этой системе в настоящее время используются. »

Если вы получаете это сообщение об ошибке, перезапуск адаптера TAP может исправить OpenVPN. Вы можете перезапустить адаптер TAP следующим образом:

Нажмите сочетание клавиш Windows + R, чтобы открыть аксессуар «Запуск».
Введите «Панель управления» в «Выполнить» и нажмите кнопку ОК .
Нажмите « Центруправлениясетями и общим доступом», чтобы открыть настройки панели управления , показанные непосредственно ниже.

Нажмите Изменить настройки адаптера, чтобы открыть свои подключения, как показано ниже.

Затем щелкните правой кнопкой мыши Адаптер TAP-Windows и выберите Отключить .
Щелкните правой кнопкой мыши TAP-Windows Adapter и выберите Enable, чтобы перезапустить адаптер.

4. Переустановите и обновите драйвер TAP-Windows

Если перезапуск адаптера не помогает, попробуйте переустановить драйвер TAP-Windows. Для этого сначала откройте диспетчер устройств, чтобы удалить адаптер, нажав клавишу Windows + горячую клавишу X.

Выберите Диспетчер устройств, чтобы открыть окно в кадре прямо ниже.

набирая задержку / медленный отклик клавиатуры в Windows 10

Дважды щелкните Сетевые адаптеры, чтобы развернуть список сетевых адаптеров.
Щелкните правой кнопкой мыши TAP-Windows Adapter и выберите « Удалить устройство» .

Теперь откройте эту страницу OpenVPN в вашем браузере .
Прокрутите страницу до конца и нажмите tap-windows-9.21.2.exe, чтобы загрузить последнюю версию драйвера TAP (NDIS 6) для OpenVPN. Драйвер NDIS 5 предназначен для Windows XP.

Щелкните правой кнопкой мыши исполняемый файл TAP-Windows и выберите « Запуск от имени администратора».
Перезагрузите Windows после установки драйвера.

Ничего не происходит, когда вы нажимаете на Запуск от имени администратора? Не волнуйтесь, у нас есть правильное решение для вас.

5. Проверьте, работает ли служба DHCP

« Последовательность инициализации завершена с ошибками » — это еще одно сообщение об ошибке, которое может открыться для некоторых пользователей OpenVPN. Если это сообщение об ошибке открывается для вас, проверьте, что служба DHCP работает.

Вы можете запустить службу DHCP следующим образом:

Введите «services.msc» в «Выполнить» и нажмите кнопку « ОК» .
Прокрутите вниз до DHCP-клиента, показанного на снимке ниже.

Дважды щелкните DHCP-клиент, чтобы открыть окно его свойств.

Выберите « Автоматически» в раскрывающемся меню «Тип запуска».
Затем нажмите кнопку « Начать обслуживание».
Если DHCP-клиент уже запущен, нажмите кнопки « Стоп» и « Пуск», чтобы перезапустить его.
Нажмите кнопку Применить и ОК .

6. Очистите DNS

Различные ошибки подключения могут быть связаны с повреждением кэша DNS. Таким образом, очистка кеша DNS может стать потенциальным исправлением для OpenVPN. Вот как вы можете очистить DNS в Windows 10.

Откройте меню Win + X с помощью клавиши Windows + X.
Нажмите Командная строка (Администратор) в меню Win + X.
Введите следующие команды отдельно в окне подсказки:

интерфейс netsh ip удалить arpcache

Закройте командную строку и перезапустите Windows.

7. Сброс Winsock

Сброс поврежденных настроек TCP / IP Winsock также может исправить сообщения об ошибках OpenVPN. Для этого введите «Командная строка» в поле поиска Кортаны.

Щелкните правой кнопкой мыши Командную строку и выберите Запуск от имени администратора, чтобы открыть ее.
Затем введите «netsh int ip reset logfile.txt» в командной строке и нажмите клавишу Enter.

Войдите в каталог сброса netsh winsock и нажмите кнопку возврата.
Перезагрузите ваш рабочий стол или ноутбук.

Некоторые из этих решений могут исправить ошибки инициализации клиента OpenVPN в Windows 10. Ознакомьтесь с этой статьей, где приведены некоторые более общие советы по исправлению VPN-подключений.

Если у вас есть какие-либо другие предложения или вопросы, не стесняйтесь оставлять их в разделе комментариев ниже, и мы обязательно их рассмотрим.

OpenVPN GUI «Connection to management interface failed» error for domain user, with no local admin privileges #332

Client = OpenVPN GUI 11.14.0.0/2.4.8 (config and installer generated by pfSense client export plugin)
Server = OpenVPN on up-to-date pfSense
OS = Windows 10 Pro, feature pack 1803
Laptop = Lenovo ThinkPad E550

User is a domain user with no local admin privileges
OpenVPN GUI launches on Windows startup
Config file and TLS key are located at C:Program FilesOpenVPNconfig
OpenVPN Interactive Service is set to Automatic and is running
OpenVPNService and OpenVPN Legacy Service are disabled

Issue Description
Sometimes, when double clicking on the OpenVPN GUI, the error message «Connecting to management interface failed» is displayed and no VPN connection is established. However, sometimes the VPN connects normally.

My work pc uses openvpn gui and I’ve been randomly having this issue pop up. It will persist for several hours and then randomly I can connect again with seemingly no prompt on either end of the issue. We initially thought it was a firewall issue and turned off the firewall, adjusted the firewall settings, reset the firewall, etc.I attempted to append the config file with the —askpass setting, but I believe I may have entered it incorrectly into the file (if this is indeed a solution, it would be helpful to know how to correctly format it)

I am using openvpn gui 11.25.0.0

Here is the error that pops up:

r/OpenVPN - OpenVPN - connecting to management interface failed

Here is the text from the log file:

2021-09-16 10:36:14 OpenVPN 2.5.3 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Jun 17 2021

2021-09-16 10:36:14 Windows version 10.0 (Windows 10 or greater) 64bit

2021-09-16 10:36:14 library versions: OpenSSL 1.1.1k 25 Mar 2021, LZO 2.10

Enter Management Password:

2021-09-16 10:36:14 MANAGEMENT: TCP Socket listening on [AF_INET](IP ADDRESS)

2021-09-16 10:36:14 Need hold release from management interface, waiting.

Источник