OpenVPN thru network manager fails for non-password configurations

Bug #475694 reported by mescator
50
This bug affects 9 people
Affects Status Importance Assigned to Milestone
network-manager-openvpn (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: network-manager-openvpn

After upgrade to 9.10 my machine failed to connect to previously working OpenVPN config.
The connection ends prematurely with following log:

Nov 5 19:28:12 NetworkManager: <info> Starting VPN service 'org.freedesktop.NetworkManager.openvpn'...
Nov 5 19:28:12 NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.openvpn' started (org.freedesktop.NetworkManager.openvpn), PID 3877
Nov 5 19:28:12 NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.openvpn' just appeared, activating connections
Nov 5 19:28:12 NetworkManager: <info> VPN plugin state changed: 1
Nov 5 19:28:12 NetworkManager: <info> VPN plugin state changed: 3
Nov 5 19:28:12 NetworkManager: <info> VPN connection 'VPN connection 1' (Connect) reply received.
Nov 5 19:28:12 NetworkManager: <WARN> nm_vpn_connection_connect_cb(): VPN connection 'VPN connection 1' failed to connect: 'No VPN secrets!'.
Nov 5 19:28:12 NetworkManager: <WARN> connection_state_changed(): Could not process the request because no VPN connection was active.
Nov 5 19:28:12 NetworkManager: <info> (eth0): writing resolv.conf to /sbin/resolvconf
Nov 5 19:28:12 NetworkManager: <info> Policy set 'Auto eth0' (eth0) as default for routing and DNS.
Nov 5 19:28:25 NetworkManager: <debug> [1257445705.001560] ensure_killed(): waiting for vpn service pid 3877 to exit
Nov 5 19:28:25 NetworkManager: <debug> [1257445705.001786] ensure_killed(): vpn service pid 3877 cleaned up

I noticed the "No VPN secrets" and googled around finding that the cause of it can be secrets ring thing.
So, I took my private key and encrypted it to make network manager rise query for password. It did and since that point I am able to use the connection.

Revision history for this message
Jim Cheetham (jim.cheetham) wrote :

I have an OpenVPN configuration that works from the command-line, without requiring any passwords to be entered (simple possession of the keys & certs is sufficient).

When I import the configuration file into Network Manager, and do not specify a "Private Key Password' value, connections fail, logging into /var/log/syslog :-

Nov 12 12:59:41 roro NetworkManager: <WARN> nm_vpn_connection_connect_cb(): VPN connection 'testvpn' failed to connect: 'No VPN secrets!'.

When I specify a useless value for the Private Key Password field (e.g. a space character), the connection works.

Revision history for this message
Mike (0x656b694d) wrote :
Revision history for this message
Jim Cheetham (jim.cheetham) wrote :

No, I don't think it is; that bug seems to be discussing a case where stored secrets are not correctly applied; this bug is discussing a case where secrets are not even present in the first place. However there are people with this problem who have joined on to 284212, from comment #60 onwards, which confuses matters. Whether they are related to the original fault or not isn't clear to me.

Revision history for this message
Andrea Garbarini (garba) wrote :

I am using a password-less private cert and I have the same problem as Jim, problem is, providing a random password doesn't do the trick for me because I run into yet-another-bug kind of problem: the password gets discarded i.e. when i get back to the configuration dialog it's no longer there... Brilliant.

Revision history for this message
jorno (jorn-odberg) wrote :

Somehow, I can't remember how, I got this working again in 9.10.

But now again, after installing 10.04 LTS Release Candidate, I'm unable to make a VPN connection with the choice "Certificates (TLS)", without specifying a password. I make the connection, but get a notification while trying to connect telling me there's no valid password present... But I'm not using a password for this VPN-connection (to my work)!

Installed 10.04 today, have installed all the updates, and I installed the package network-manager-openvpn-gnome.

Revision history for this message
Michael Schobert (m-schobert) wrote :

Can not get it working either. It does connect to the vpn via $ sudo openvpn --config $HOME/.openvpn/myvpn.ovpn.
The config is the very one that I imported into the network manager. I tried with and without a dummy password.

Revision history for this message
papukaija (papukaija) wrote :

This bug is affecting 6 people and no one has marked is as confirmed?!

In response to comment 2: No (the error messsages don't match).

tags: added: karmic lucid
Changed in network-manager-openvpn (Ubuntu):
status: New → Confirmed
tags: added: metabug
Revision history for this message
papukaija (papukaija) wrote :

This bug is a regression from jaunty.

tags: added: regression-release
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Maverick Meerkat. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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