[GNOME][NETWORK-MANAGER-GNOME] VPN connection timeout

I’m having an issue when I try to connect to a vpn with a ovpn config file via GNOME’s network manager. I select the ‘Import file…’ option, select the VPN config file, add my username and password and save. Whenever I activate the connection, it asks me the admin password, which I give, only to get a ‘Connection failed’ message after a while.

This is what journalctl shows:


Dec 03 20:43:32 sam-PC NetworkManager[1166]: <info>  keyfile: add connection /etc/NetworkManager/system-connections/ch40.nordvpn.com.tcp443_ (8dff1099-a298-48aa-a78f-39b7ccff4bdd,"ch40.nordvpn.com.tcp443")
Dec 03 20:44:09 sam-PC NetworkManager[1166]: <info>  Starting VPN service 'openvpn'...
Dec 03 20:44:09 sam-PC NetworkManager[1166]: <info>  VPN service 'openvpn' started (org.freedesktop.NetworkManager.openvpn), PID 4371
Dec 03 20:44:09 sam-PC kernel: tun: Universal TUN/TAP device driver, 1.6
Dec 03 20:44:09 sam-PC kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Dec 03 20:44:09 sam-PC NetworkManager[1166]: <info>  VPN service 'openvpn' appeared; activating connections
Dec 03 20:44:16 sam-PC polkitd[1051]: Operator of unix-session:1 successfully authenticated as unix-user:root to gain TEMPORARY authorization for action org.freedesktop.NetworkManager.settings.modify.system for unix-process:2451:3893 [/usr/bin/gnome-shell] (owned by unix-user:sameyepatch)
Dec 03 20:44:17 sam-PC NetworkManager[1166]: (nm-openvpn-service:4371): nm-openvpn-WARNING **: Directory '/var/lib/openvpn/chroot' not usable for chroot by 'nm-openvpn', openvpn will not be chrooted.
Dec 03 20:44:17 sam-PC NetworkManager[1166]: nm-openvpn-Message: openvpn started with pid 4382
Dec 03 20:44:17 sam-PC NetworkManager[1166]: (nm-openvpn-service:4371): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed
Dec 03 20:44:17 sam-PC NetworkManager[1166]: <info>  VPN plugin state changed: starting (3)
Dec 03 20:44:17 sam-PC NetworkManager[1166]: <info>  VPN connection 'ch40.nordvpn.com.tcp443' (ConnectInteractive) reply received.
Dec 03 20:44:17 sam-PC nm-openvpn[4382]: OpenVPN 2.3.8 x86_64-suse-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [MH] [IPv6] built on Aug  4 2015
Dec 03 20:44:17 sam-PC nm-openvpn[4382]: library versions: OpenSSL 1.0.2j-fips  26 Sep 2016, LZO 2.08
Dec 03 20:44:17 sam-PC nm-openvpn[4382]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Dec 03 20:44:17 sam-PC nm-openvpn[4382]: NOTE: UID/GID downgrade will be delayed because of --client, --pull, or --up-delay
Dec 03 20:44:17 sam-PC nm-openvpn[4382]: Attempting to establish TCP connection with [AF_INET]185.9.18.83:443 [nonblock]
Dec 03 20:44:18 sam-PC nm-openvpn[4382]: TCP connection established with [AF_INET]185.9.18.83:443
Dec 03 20:44:18 sam-PC nm-openvpn[4382]: TCPv4_CLIENT link local: [undef]
Dec 03 20:44:18 sam-PC nm-openvpn[4382]: TCPv4_CLIENT link remote: [AF_INET]185.9.18.83:443
Dec 03 20:44:18 sam-PC nm-openvpn[4382]: Connection reset, restarting [0]
Dec 03 20:44:18 sam-PC nm-openvpn[4382]: SIGUSR1[soft,connection-reset] received, process restarting
Dec 03 20:44:23 sam-PC nm-openvpn[4382]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Dec 03 20:44:23 sam-PC nm-openvpn[4382]: Attempting to establish TCP connection with [AF_INET]185.9.18.83:443 [nonblock]
Dec 03 20:44:24 sam-PC nm-openvpn[4382]: TCP connection established with [AF_INET]185.9.18.83:443
Dec 03 20:44:24 sam-PC nm-openvpn[4382]: TCPv4_CLIENT link local: [undef]
Dec 03 20:44:24 sam-PC nm-openvpn[4382]: TCPv4_CLIENT link remote: [AF_INET]185.9.18.83:443
Dec 03 20:44:25 sam-PC nm-openvpn[4382]: Connection reset, restarting [0]
Dec 03 20:44:25 sam-PC nm-openvpn[4382]: SIGUSR1[soft,connection-reset] received, process restarting
Dec 03 20:44:30 sam-PC nm-openvpn[4382]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Dec 03 20:44:30 sam-PC nm-openvpn[4382]: Attempting to establish TCP connection with [AF_INET]185.9.18.83:443 [nonblock]
Dec 03 20:44:31 sam-PC nm-openvpn[4382]: TCP connection established with [AF_INET]185.9.18.83:443
Dec 03 20:44:31 sam-PC nm-openvpn[4382]: TCPv4_CLIENT link local: [undef]
Dec 03 20:44:31 sam-PC nm-openvpn[4382]: TCPv4_CLIENT link remote: [AF_INET]185.9.18.83:443
Dec 03 20:44:31 sam-PC nm-openvpn[4382]: Connection reset, restarting [0]
Dec 03 20:44:31 sam-PC nm-openvpn[4382]: SIGUSR1[soft,connection-reset] received, process restarting
Dec 03 20:44:36 sam-PC nm-openvpn[4382]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Dec 03 20:44:36 sam-PC nm-openvpn[4382]: Attempting to establish TCP connection with [AF_INET]185.9.18.83:443 [nonblock]
Dec 03 20:44:37 sam-PC nm-openvpn[4382]: TCP connection established with [AF_INET]185.9.18.83:443
Dec 03 20:44:37 sam-PC nm-openvpn[4382]: TCPv4_CLIENT link local: [undef]
Dec 03 20:44:37 sam-PC nm-openvpn[4382]: TCPv4_CLIENT link remote: [AF_INET]185.9.18.83:443
Dec 03 20:44:37 sam-PC nm-openvpn[4382]: Connection reset, restarting [0]
Dec 03 20:44:37 sam-PC nm-openvpn[4382]: SIGUSR1[soft,connection-reset] received, process restarting
Dec 03 20:44:42 sam-PC nm-openvpn[4382]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Dec 03 20:44:42 sam-PC nm-openvpn[4382]: Attempting to establish TCP connection with [AF_INET]185.9.18.83:443 [nonblock]
Dec 03 20:44:43 sam-PC nm-openvpn[4382]: TCP connection established with [AF_INET]185.9.18.83:443
Dec 03 20:44:43 sam-PC nm-openvpn[4382]: TCPv4_CLIENT link local: [undef]
Dec 03 20:44:43 sam-PC nm-openvpn[4382]: TCPv4_CLIENT link remote: [AF_INET]185.9.18.83:443
Dec 03 20:44:44 sam-PC nm-openvpn[4382]: Connection reset, restarting [0]
Dec 03 20:44:44 sam-PC nm-openvpn[4382]: SIGUSR1[soft,connection-reset] received, process restarting
Dec 03 20:44:49 sam-PC nm-openvpn[4382]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Dec 03 20:44:49 sam-PC nm-openvpn[4382]: Attempting to establish TCP connection with [AF_INET]185.9.18.83:443 [nonblock]
Dec 03 20:44:50 sam-PC nm-openvpn[4382]: TCP connection established with [AF_INET]185.9.18.83:443
Dec 03 20:44:50 sam-PC nm-openvpn[4382]: TCPv4_CLIENT link local: [undef]
Dec 03 20:44:50 sam-PC nm-openvpn[4382]: TCPv4_CLIENT link remote: [AF_INET]185.9.18.83:443
Dec 03 20:44:50 sam-PC nm-openvpn[4382]: Connection reset, restarting [0]
Dec 03 20:44:50 sam-PC nm-openvpn[4382]: SIGUSR1[soft,connection-reset] received, process restarting
Dec 03 20:44:55 sam-PC nm-openvpn[4382]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Dec 03 20:44:55 sam-PC nm-openvpn[4382]: Attempting to establish TCP connection with [AF_INET]185.9.18.83:443 [nonblock]
Dec 03 20:44:56 sam-PC nm-openvpn[4382]: TCP connection established with [AF_INET]185.9.18.83:443
Dec 03 20:44:56 sam-PC nm-openvpn[4382]: TCPv4_CLIENT link local: [undef]
Dec 03 20:44:56 sam-PC nm-openvpn[4382]: TCPv4_CLIENT link remote: [AF_INET]185.9.18.83:443
Dec 03 20:44:56 sam-PC nm-openvpn[4382]: Connection reset, restarting [0]
Dec 03 20:44:56 sam-PC nm-openvpn[4382]: SIGUSR1[soft,connection-reset] received, process restarting
Dec 03 20:44:57 sam-PC NetworkManager[1166]: <warn>  VPN connection 'ch40.nordvpn.com.tcp443' connect timeout exceeded.
Dec 03 20:44:57 sam-PC nm-openvpn[4382]: SIGTERM[hard,init_instance] received, process exiting
Dec 03 20:44:57 sam-PC NetworkManager[1166]: nm-openvpn-Message: Terminated openvpn daemon with PID 4382.

The importart part here is

<warn>  VPN connection 'ch40.nordvpn.com.tcp443' connect timeout exceeded.

.

If I do a command line instruction with the config file, however, the connection succeeds. But I got to have a terminal open at all times, and I need to start the connection manually. I could try to make a bash script, but I’m not knowledgeable at the moment for that. Has any of you encountered the same issue by any chance?

Thanks beforehand.

Actually, the TCP connection keeps getting reset. That needs to be investigated.

Hello!

Thanks for answering. Is there something on my end that need to check or do, or is this something developers should fix themselves? Please bear with me, it’s been a while since I’ve used openSUSE until recently.

You’re probably best to take this up with the VPN provider. You mentioned that this works when you start the VPN manually from a terminal? If so, you could observe the connection process by watching the connection process from a terminal when you connect in another perhaps…

sudo journalctl -f

Then compare the output from the NetworkManager when attempting to connect that way.