HDAConnect fails to connect via OpenVPN (Windows 8.1)

[PatrickDickey]

Hi there,

I noticed someone else having this issue on a Mac, but I'm having it with the official HDAConnect app running on Windows 8.1 (64). I've verified that the openvpn service is running, and in my control panel, it says that it's working.

Here is the log for the most recent attempt:

Code: Select all

Tue Feb 17 09:07:29 2015 OpenVPN 2.1_rc15 i686-pc-mingw32 [SSL] [LZO2] [PKCS11] built on Nov 19 2008 Enter Auth Password: Tue Feb 17 09:07:29 2015 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info. Tue Feb 17 09:07:29 2015 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables Tue Feb 17 09:07:30 2015 LZO compression initialized Tue Feb 17 09:07:30 2015 Control Channel MTU parms [ L:1542 D:138 EF:38 EB:0 ET:0 EL:0 ] Tue Feb 17 09:07:30 2015 Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:135 ET:0 EL:0 AF:3/1 ] Tue Feb 17 09:07:30 2015 Local Options hash (VER=V4): '41690919' Tue Feb 17 09:07:30 2015 Expected Remote Options hash (VER=V4): '530fdded' Tue Feb 17 09:07:30 2015 Socket Buffers: R=[65536->65536] S=[65536->65536] Tue Feb 17 09:07:30 2015 UDPv4 link local: [undef] Tue Feb 17 09:07:30 2015 UDPv4 link remote: 67.7.24.157:1194 Tue Feb 17 09:08:30 2015 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) Tue Feb 17 09:08:30 2015 TLS Error: TLS handshake failed Tue Feb 17 09:08:30 2015 TCP/UDP: Closing socket Tue Feb 17 09:08:30 2015 SIGUSR1[soft,tls-error] received, process restarting Tue Feb 17 09:08:30 2015 Restart pause, 2 second(s)

And here is my config file from HDAConnect:

Code: Select all

client dev tun0 proto udp resolv-retry infinite nobind persist-key persist-tun ca ca.crt cert homehda.crt key homehda.key comp-lzo verb 3 auth-user-pass route-method exe route-delay 2

This setup has worked in the past, but now it's not. I wasn't using it very frequently, so I honestly don't know when it broke.

On the HDA, I get this for the systemctl status openvpn\@amahi.service

Code: Select all

[root@localhost ~]# systemctl status openvpn\@amahi.service openvpn@amahi.service - OpenVPN Robust And Highly Flexible Tunneling Application On amahi Loaded: loaded (/usr/lib/systemd/system/openvpn@.service; enabled) Active: active (running) since Sun 2015-02-08 09:31:55 CST; 1 weeks 4 days ago Process: 712 ExecStart=/usr/sbin/openvpn --daemon --writepid /var/run/openvpn/%i.pid --cd /etc/openvpn/ --config %i.conf (code=exited, status=0/SUCCESS) Main PID: 1238 (openvpn) CGroup: name=systemd:/system/openvpn@.service/openvpn@amahi.service ├─1119 /usr/sbin/openvpn --daemon --writepid /var/run/openvpn/amah... └─1238 /usr/sbin/openvpn --daemon --writepid /var/run/openvpn/amah... Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

My Amahi.conf file looks like this:

Code: Select all

[root@localhost openvpn]# cat amahi.conf port 1194 proto udp #mode server #tls-server # dev tap0 dev tun ca /etc/openvpn/amahi/ca.crt cert /etc/openvpn/amahi/server.crt # This file should be kept secret key /etc/openvpn/amahi/server.key dh /etc/openvpn/amahi/dh1024.pem server 192.168.200.0 255.255.255.0 ifconfig-pool-persist /var/run/openvpn-ipp.cache push "route 192.168.2.0 255.255.255.0" push "dhcp-option DNS 192.168.2.98" push "dhcp-option DOMAIN local.lan" push "default_gateway 192.168.2.1" keepalive 10 220 comp-lzo persist-key persist-tun status /var/log/openvpn-status.log verb 3 ;mute 20 plugin /usr/lib64/openvpn/plugins/openvpn-plugin-auth-pam.so "login login USERNAME password PASSWORD" script-security 2 up ./amahi.up down ./amahi.down

So I'm clueless, as I don't think I've made any changes other than script-security 2 (to try and resolve the your current user configuration allows for running applications warning), and adding in the default-gateway information.

Thanks for any help.
Patrick.

[bigfoot65]

Is it possible that script might have changed something? Honestly I have not heard of any major issues with Windows 8. Of course all the MS updates could have caused the problem as well.

I will do some poking around and see if I can find anything that might help.

Are you HDA OS updates current?