VPN doesn't connect automatically
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
New
|
Low
|
Unassigned |
Bug Description
I have set up my Network Connections manager to automatically connect to my VPN. My VPN is saved with its credentials. When I first log in (newly started, rebooted or woken from sleep/suspend), the VPN doesn't connect on its own.
It sometimes doesn't connect at all, and sometimes it tells me that the VPN requires a password. I haven't noticed a pattern.
Description: Ubuntu 20.10
Release: 20.10
network-manager:
Installed: 1.26.2-1ubuntu1
Candidate: 1.26.2-1ubuntu1
Version table:
*** 1.26.2-1ubuntu1 500
500 http://
100 /var/lib/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu50.1
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.10
InstallationDate: Installed on 2020-10-25 (22 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
default via 192.168.1.1 dev wlp1s0 proto dhcp metric 600
169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.106 metric 600
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
Package: network-manager 1.26.2-1ubuntu1
PackageArchitec
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
Tags: groovy
Uname: Linux 5.8.0-29-generic x86_64
UpgradeStatus: Upgraded to groovy on 2020-10-25 (22 days ago)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
running 1.26.2 connected started full enabled enabled enabled enabled enabled
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1902596
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https:/ /wiki.ubuntu. com/ReportingBu gs.
Could you also add the 'journalctl -b 0' log of a session showing the issue?