Well shoots. As it turns out, starting from command line doesn't really put
messages into the gnome-system-log. I'll post it anyway.
Here's what the Unsuccessful attempt to the NordVPN site "US365" in Chicago
looks like using the network manager applet (correctly configured, exactly as
it is on the other vpn site (us_82) that works consistently):
......
Jul 27 12:19:40 trisquet NetworkManager[902]: Starting VPN service
'openvpn'...
Jul 27 12:19:40 trisquet NetworkManager[902]: VPN service 'openvpn' started
(org.freedesktop.NetworkManager.openvpn), PID 5816
Jul 27 12:19:40 trisquet NetworkManager[902]: VPN service 'openvpn'
appeared; activating connections
Jul 27 12:19:40 trisquet NetworkManager[902]: VPN plugin state changed:
starting (3)
Jul 27 12:19:40 trisquet NetworkManager[902]: VPN connection
'us365.nordvpn.com.udp1194' (Connect) reply received.
Jul 27 12:19:40 trisquet nm-openvpn[5821]: OpenVPN 2.3.2 x86_64-pc-linux-gnu
[SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [eurephia] [MH] [IPv6] built on Jun 22
2017
Jul 27 12:19:40 trisquet nm-openvpn[5821]: NOTE: the current
--script-security setting may allow this configuration to call user-defined
scripts
Jul 27 12:19:40 trisquet nm-openvpn[5821]: UDPv4 link local: [undef]
Jul 27 12:19:40 trisquet nm-openvpn[5821]: UDPv4 link remote:
[AF_INET]173.234.62.163:1194
Jul 27 12:20:20 trisquet NetworkManager[902]: VPN connection
'us365.nordvpn.com.udp1194' (IP Config Get) timeout exceeded.
Jul 27 12:20:20 trisquet NetworkManager[902]: Policy set 'HomeNetwork'
(wlan0) as default for IPv4 routing and DNS.
Jul 27 12:20:20 trisquet nm-openvpn[5821]: SIGTERM[hard,] received, process
exiting
Jul 27 12:20:25 trisquet NetworkManager[902]: VPN service 'openvpn'
disappeared
........
As you can see, the connection times out and then hangs up.
After failing to connect with network manager, I connected from the terminal
without any problem. In fact, I'm on that VPN connection right now.
Ideas?
