Ubuntu
tracker package

VPN connection failed.

Bug #1375106 reported by Larry McNaughton
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

My VPN connection was working fine but now I get the error message 'VPN connection failed because there were no valid VPN secrets'.

I am using Ubuntu 14.10 with Network Manager 0.9.8.8-0ubunty27 and openvpn 2.3.2-9ununtu1

I tried to connect to my VPN server (Private Internet Access) but got the above error message instead.

Revision history for this message
Larry McNaughton (larry-mcnaughton) wrote :

I was able to resolve my VPN connection issue by deleting the connection and re-configuring it in the Network Manager.
I thought it was a bug in either the Network Manager or openvpn because the error occurred just after a couple of larger recent system updates.
Sorry for jumping the gun on this, I've been using Linux since the mid 90's and Ubuntu since about 2005, but only as an end user with just intermediate knowledge and skills at best, sorry for any inconvenience this may have caused.
Larry

Revision history for this message
Rejean Groleau (rejeangroleau) wrote :

I have the exact same issue, with the same symptoms. My computer (64-bit ubuntu 14.10 laptop) sometimes cannot access any vpn at all, whether it is an openvpn or an ipsec vpn. From the GUI front end of the Network Manager, clicking on the vpn connection in the menu to initiate a connection just fails silently (the menu closes, and nothing happens). When using the command line tool (nmcli c up uuid ...) the result is: "Error: Connection activation failed: no valid VPN secrets".

It seems to be related to the networkmanager not being able to retrieve the password information from the gnome keyring, but I have no idea how to permanently fix this. So far, I just delete the connection and re-create it again to make it works. It is time-consuming, and I would really like a real fix for this bug.

Note that the keyring seems to be unlocked just fine since my ssh id_rsa is working without asking me for the password.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in tracker (Ubuntu):
status: New → Confirmed
Revision history for this message
Waldmeisda (frank-waldmeisda) wrote :

onetime solution is delete ~/.gconf/apps/nm-applet/%gconf.xml
and logout/login

But I'm looking for a final solution too

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.