On Fri, 2016-04-29 at 11:37 -0400, Mike Miller wrote: > > Can you say which graphical tool you are using to connect to the VPN? > If > gnome-shell or gnome-control-center network, which version? Does the > same behavior occur with "nmcli con up VPN-NAME"? When it does occur, > do > you see a stray nm-openconnect-service process running after the > failure? > > This sounds like a symptom I used to see with both OpenConnect and > OpenVPN connections, but has recently disappeared since upgrading to > Gnome 3.20 and NetworkManager 1.2.0. >
gnome-shell current stretch version 3.18.1-1 yes, nmcli has the same behavior: $ nmcli con up 'IBM openconnect' Error: Connection activation failed: no valid VPN secrets. brente@brente:~$ nmcli con up 'IBM openconnect' A password is required to connect to 'IBM openconnect'. Warning: password for 'vpn.secrets.gateway' not given in 'passwd-file' and nmcli cannot ask without '--ask' option. The first time I run nmlci I get an immediate prompt back after the Error. The second time I get the Warning but the login dialog shows and I can click login. Here is what ps shows after the failure: root 3394 1 0 10:46 ? 00:00:00 /usr/lib/NetworkManager/nm-openconnect-service --bus-name org.freedesktop.NetworkManager.openconnect.Connection_2 When the "connect to VPN" dialog shows up for me to login, I have "Automatically start connecting next time" checked and "Save passwords" checked and the password is there. However, it has never automatically connected. I have always had to click "Login" to be connected. It seems like with those two boxes checked and a password in the field, it should just connect automatically. Shouldn't it? What is vpn.secrets.gateway and passwd-file? I did some experimenting and found that if I disconnect from the vpn that reconnecting always brings up the connect dialog box. Also, if I log out and back in the first time clicking on connect to vpn always brings up the connect dialog box. I also tried waiting 5 or 10 minutes after I log in to gnome to see if that makes any difference. It appears that no matter how long I wait, the first attempt after a boot fails. I hope this helps to figure out what the problem is.
