When you use Network Manager, the file locations and entries are different, so setting up a NM VPN connection is starting from scratch without using any of the files in the locations they are in now.
TSU
Not quite. When setting up the connection, you just point it at the appropriate (in situ) certificate and key files. The .ovpn file is of course not used, and those client settings are stored in the connection profile file located in the /etc/NetworkManager/system-connections/ directory.
I’ve tried setting it up by opening up networkmanager, clicking “add” and then “import VPN”
from there I choose the relevant .ovpn file. It then says “do you want to copy your certificates to /home/ross/.local/share/networkmanagement/certificates” to which I say “yes”. I then enter my root password.
It says connection has been added. I then edit the connection and in the editor I enter my username and password for the VPN. I leave all other settings the same. If I try to connect it asks me for a password…I don’t understand this, because I’ve already entered my password in the settings page…but if I enter it again it says “starting the service providing the VPN failed”.
If I edit my connection which DOES work and in the “general configuration” tab click “automatically connect to VPN when using this connection” and choose the VPN I’ve just created…disconnect it, then go to reconnect it asks me for my root password and then asks me for the VPN password (again…why…I’ve added this in the settings…) and after doing this it says “a secondary connection of the base connection failed”
Any thoughts?
If using networkmanager means I still have to enter my root password and VPN password each time I want to connect, I don’t see the benefit of doing that over using the terminal? Or am I missing something? If I then disconnect, edit it to say NOT to connect to the VPN and reconnect, it connects back…but I’m then left with the “resolving host” issue I had before…
Thanks again for your help guys, it really is appreciated!
On Sat 22 Apr 2017 12:06:01 PM CDT, thestig wrote:
deano_ferrari;2820509 Wrote:
> Not quite. When setting up the connection, you just point it at the
> appropriate (in situ) certificate and key files. The .ovpn file is of
> course not used, and those client settings are stored in the
> connection profile file located in
> the /etc/NetworkManager/system-connections/ directory.
I’ve tried setting it up by opening up networkmanager, clicking “add”
and then “import VPN”
from there I choose the relevant .ovpn file. It then says “do you want
to copy your certificates to
/home/ross/.local/share/networkmanagement/certificates” to which I say
“yes”. I then enter my root password.
It says connection has been added. I then edit the connection and in the
editor I enter my username and password for the VPN. I leave all other
settings the same. If I try to connect it asks me for a password…I
don’t understand this, because I’ve already entered my password in the
settings page…but if I enter it again it says “starting the service
providing the VPN failed”.
If I edit my connection which DOES work and in the “general
configuration” tab click “automatically connect to VPN when using this
connection” and choose the VPN I’ve just created…disconnect it, then
go to reconnect it asks me for my root password and then asks me for the
VPN password (again…why…I’ve added this in the settings…) and
after doing this it says “a secondary connection of the base connection
failed”
Any thoughts?
If using networkmanager means I still have to enter my root password and
VPN password each time I want to connect, I don’t see the benefit of
doing that over using the terminal? Or am I missing something.
Thanks again for your help guys, it really is appreciated!
Hi
Is this relevant…?
http://forums.opensuse.org/showthread.php?t=524418
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.22.2|4.4.57-18.3-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Hi,
I ran into the same issue that chap had so had to use other .zip files but now it works absolutely fine. I’m not sure where I’m going wrong with configuring it with networkmanager but, to be honest, I’m happy with it via the console anyway. I’ve done a few DNS leak tests online too and it’s not leaking which is good 
Without reviewing the NetworkManager log and possibly the connection profile, one can only speculate about what is going wrong here. It is possible to configure the VPN connection manually (as opposed to importing the credentials), but one does need to make sure that the working .ovpn file settings are understood so that they can be applied in NM VPN advance settings appropriately.
If I edit my connection which DOES work and in the “general configuration” tab click “automatically connect to VPN when using this connection” and choose the VPN I’ve just created…disconnect it, then go to reconnect it asks me for my root password and then asks me for the VPN password (again…why…I’ve added this in the settings…) and after doing this it says “a secondary connection of the base connection failed”
Any thoughts?
I see a lot of users reporting similar behaviour with passwords being requested in these forums, and I wonder if it’s due to a password manager (eg kwallet) being launched for a user-defined connection perhaps?
If using networkmanager means I still have to enter my root password and VPN password each time I want to connect, I don’t see the benefit of doing that over using the terminal? Or am I missing something? If I then disconnect, edit it to say NOT to connect to the VPN and reconnect, it connects back…but I’m then left with the “resolving host” issue I had before…
Thanks again for your help guys, it really is appreciated!
NM is just another means to an end. Use what you find most convenient. I think you mean that you get prompted by a password manager? That only happens the first time within a given session.