OpenVPN connects on CLI, not on GUI [2.1.4]
I realize VPN with settings GUI is still in beta. This is to report my experience with it.
I set up an OpenVPN server on my VPS following this guide. Using the .ovpn file generated following the guide I can connect in the terminal
devel-su openvpn --config client1.ovpn
Using the browser I can confirm that a VPN connection is succesfully working.
Next I set up a connection using the same .ovpn file in the settings GUI import feature. When trying to enable the connection, it says "connecting" for two seconds, then without any error message the status goes back to "unused".
EDIT1: Thanks for the hints on logs! This is the error I get:
openvpn[11958]: setgid('nobody') failed: Operation not permitted (errno=1)
openvpn[11958]: Exiting due to fatal error
openvpn[11958]: Closing TUN/TAP interface
Should I use some other group in Step 12/Linux section of the referred guide?
Are you using certificates, I suggest making sure the full path is in the ovpn file, and not just a ./ or similar. If you are using username/password only, may be an issue.
Nieldk ( 2018-03-06 09:03:08 +0200 )editThe certs and keys are embedded on the ovpn file as per step 10 on the guide.
J24 ( 2018-03-06 09:15:21 +0200 )editHi.
I usually check the logs this way:
If you don't see any messages while trying restart journald with:
And try again. (This has happened to my while trying this answer.:D )
Regards.
Pasko ( 2018-03-06 10:44:58 +0200 )editUsing the
journalctl
command above, I get the following:I didn't follow the guide, but the behaviour is similar for me: works on the command-line, but doesn't using the UI.
Éibhear ( 2018-03-06 12:40:37 +0200 )editHi @Éibhear
Instead, try this sequence (I suppose you're logging in remotely via ssh? )
And then try to start the VPN from the GUI....keep in mind that once the VPN connection is established you may loose access via ssh :-)
Regards.
Pasko ( 2018-03-06 16:17:56 +0200 )edit