can't connect to management interface 2.4.0

DigitalHurricane

Hi

After updating to 2.4.0 using openvpn-install-2.4.0-I601.exe I can no longer connect to the client management interface. I'm using windows 10.

I gave it a shot on a fresh win 10 virtual machine as well and encountered the same problem. Everything was working fine on 2.3.14

I use management localhost 7000 in my client config

If I open powershell and do telnet 127.0.0.1 7000 I get:

Connecting To 127.0.0.1...Could not open connection to the host, on port 7000: Connect failed

client management interface still works fine on ubuntu 16.04 after upgrade to 2.4.0

If you need more info please let me know.

DigitalHurricane

By the way here is the output when I connect.

Tue Jan 10 14:19:11 2017 OpenVPN 2.4.0 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Dec 27 2016
Tue Jan 10 14:19:11 2017 Windows version 6.2 (Windows 8 or greater) 64bit
Tue Jan 10 14:19:11 2017 library versions: OpenSSL 1.0.2i 22 Sep 2016, LZO 2.09
Tue Jan 10 14:19:11 2017 setsockopt(IPV6_V6ONLY=0)
Tue Jan 10 14:19:11 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]192.241.182.97:1194
Tue Jan 10 14:19:11 2017 UDP link local: (not bound)
Tue Jan 10 14:19:11 2017 UDP link remote: [AF_INET]192.241.182.97:1194
Tue Jan 10 14:19:11 2017 [server] Peer Connection Initiated with [AF_INET]192.241.182.97:1194
Tue Jan 10 14:19:12 2017 open_tun
Tue Jan 10 14:19:12 2017 TAP-WIN32 device [Ethernet 4] opened: \\.\Global\{A44BD45B-EC1E-49BA-BF9A-DC3AC3A69AA1}.tap
Tue Jan 10 14:19:12 2017 Set TAP-Windows TUN subnet mode network/local/netmask = 10.8.0.0/10.8.0.2/255.255.255.0 [SUCCEEDED]
Tue Jan 10 14:19:12 2017 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.8.0.2/255.255.255.0 on interface {A44BD45B-EC1E-49BA-BF9A-DC3AC3A69AA1} [DHCP-serv: 10.8.0.254, lease-time: 31536000]
Tue Jan 10 14:19:12 2017 Successful ARP Flush on interface [22] {A44BD45B-EC1E-49BA-BF9A-DC3AC3A69AA1}
Tue Jan 10 14:19:12 2017 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Tue Jan 10 14:19:12 2017 Block_DNS: WFP engine opened
Tue Jan 10 14:19:12 2017 Block_DNS: Using existing sublayer
Tue Jan 10 14:19:12 2017 Block_DNS: Added permit filters for exe_path
Tue Jan 10 14:19:12 2017 Block_DNS: Added block filters for all interfaces
Tue Jan 10 14:19:12 2017 Block_DNS: Added permit filters for TAP interface
Tue Jan 10 14:19:17 2017 Initialization Sequence Completed

DigitalHurricane

OK found the solution.

Looks like openvpn 2.4.0 is using IPv6 for the management interface at least on windows.

So if you have 'management localhost 7000' in your client config, you would connect to the management interface like this:

telnet ::1 7000

TinCanTech

DigitalHurricane wroteLooks like openvpn 2.4.0 is using IPv6 for the management interface

Openvpn uses what ever you have configured.

DigitalHurricane wroteSo if you have 'management localhost 7000' in your client config, you would connect to the management interface like this:

telnet ::1 7000

Because "localhost" is resolves as ::1 by Windows.

If you want IPv4 use:

management 127.0.0.1 7000

which is specifically IPv4.

DigitalHurricane

Before the update it was using IPv4 with the same client config. That's all I can tell you. No doubt about it. But thanks.

Eternal.Optimist

I'm sorry but I'm having the same problem and I have no clue on where to go fixing this issue.
I don't even get an output log. It fails right away with the Connect to Management Interface error

The only thing I have when I check my log after is
Options error: --ca fails with 'ca.ipvanish.com.crt': No such file or directory
Options error: Please correct these errors.
Use --help for more information.

Been having this problem since I reformatted my computer. Uninstalled and reinstalled. I'm about to give up.

DigitalHurricane

OpenVPN is looking for the CA certificate file called 'ca.ipvanish.com.crt' and can't find it.