Vivid VPN does not connect, "No valid VPN secrets"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I use VPN in every Ubuntu version, usually pptp type.
Starting with Vivid new problem raised: the connection, which is properly configured and working first time after the fresh OS installation, does not initiate when the computer is rebooted.
Scenario:
- installing Vivid, from scratch
- configuring WiFi access
- connecting to the WiFi
- verifying: everything works fine, including Internet access and browsing
- using right-screen network icon, creating the VPN pptp tunnel
- connecting to the VPN, animated wifi icon runs and connects
- checking : everything works fine
reboot
- reconnecting to the WiFi with the menu icon: ok
- checking : Internet works, everything OK
- clicking on VPN name connection in the network menu in the right, upper side menu icon: nothing happens. There is no usual "connecting" animated icon, the VPN does not starts
- rebooting, restarting network manager, recreating the new VPN under the new name does not solve the problem.
Trying with the nmcli from Terminal au a normal user:
$ nmcli con up vpnname (or sudo nmcli con up vpnname)
nothing happens. After the 90 seconds, there is a time-out message .
Connecting as a root:
root@.... nmcli con up vpnname
instantaneous message : "No valid VPN secrets"
Restarting the network-manager does not solve the problem.
In /etc/NetworkMan
The same situation occurs with other VPN types; I tried OpenVPN.
affects: | ubuntu → network-manager (Ubuntu) |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1477728/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]