VPN stopped working with network manager

[TinyCritter]

Hello :) I recently did an update to my MX system (Wildflower), and using Network Manager with my VPN (Nord) stopped working. Normally I just connect to it via network manager when I turn the system on, but now every time it asks for "Authentication Required (A password is required)", and when I input the password there, it still refuses to connect, seconds later giving another of the same popups.

Does anyone know of a fix for this?

[siamhie]

Post your QSI (Quick System Info)

[TinyCritter]

Post your QSI (Quick System Info)

Hey, sorry it took me so long to reply, I got very sidetracked.

Code: Select all

System:    Kernel: 5.10.0-23-amd64 [5.10.179-2] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-23-amd64 root=UUID=<filter> ro splash 
           nouveau.modeset=1 ipv6.disable=1 
           Desktop: Xfce 4.18.1 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.18.0 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-21.3_x64 Wildflower September 18  2022 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop System: Gigabyte product: v: N/A serial: <filter> Chassis: 
           type: 3 serial: <filter> 
           Mobo: Gigabyte model: v: x.x serial: <filter> BIOS: American Megatrends 
           v: F6 date: 06/17/2014 
CPU:       Info: Quad Core model: Intel Core i5-4690K bits: 64 type: MCP arch: Haswell family: 6 
           model-id: 3C (60) stepping: 3 microcode: 28 cache: L2: 6 MiB 
           flags:
           Speed: 1200 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 1200 2: 1200 3: 1200 
           4: 1200 
Graphics:  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
           vendor: Gigabyte driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:0412 
           class-ID: 0300 
           Device-2: NVIDIA GM204 [GeForce GTX 970] vendor: Micro-Star MSI driver: nouveau 
           v: kernel bus-ID: 01:00.0 chip-ID: 10de:13c2 class-ID: 0300 
           Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.18.0 driver: 
           loaded: modesetting unloaded: fbdev,vesa display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
           s-diag: 582mm (22.9") 
           Monitor-1: HDMI-3 res: 1920x1080 hz: 60 dpi: 96 size: 509x286mm (20.0x11.3") 
           diag: 584mm (23") 
           OpenGL: renderer: NV124 v: 4.3 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel 
           v: kernel bus-ID: 00:03.0 chip-ID: 8086:0c0c class-ID: 0403 
           Device-2: Intel 9 Series Family HD Audio vendor: Gigabyte driver: snd_hda_intel 
           v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8ca0 class-ID: 0403 
           Device-3: NVIDIA GM204 High Definition Audio vendor: Micro-Star MSI 
           driver: snd_hda_intel v: kernel bus-ID: 01:00.1 chip-ID: 10de:0fbb class-ID: 0403 
           Sound Server-1: ALSA v: k5.10.0-23-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Intel Ethernet I217-V vendor: Gigabyte driver: e1000e v: kernel port: f080 
           bus-ID: 00:19.0 chip-ID: 8086:153b class-ID: 0200 
           IF: eth0 state: down mac: <filter> 
           Device-2: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152 
           bus-ID: 4-3:4 chip-ID: 0bda:8153 class-ID: 0000 serial: <filter> 
           IF: eth1 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:   
Partition:
Swap:    
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nouveau temp: 40.0 C 
           Fan Speeds (RPM): N/A gpu: nouveau fan: 530 
Repos:    
Info:     
Boot Mode: BIOS (legacy, CSM, MBR)

__________________


I also attached an image of what the authentication error looks like, when I try to connect to any of my VPN connections via the network manager:

authentication error.png

Basically it won't take my (correct) password, no matter what way I input it - it just fails to connect and this popup comes up again, endlessly

[siamhie]

@TinyCritter I've only ever connected to Nord via the terminal.

nordvpn connect or nordvpn connect P2P (for torrenting)

nordvpn disconnect (when I want to disconnect from Nord)

[TinyCritter]

@TinyCritter I've only ever connected to Nord via the terminal.

nordvpn connect or nordvpn connect P2P (for torrenting)

nordvpn disconnect (when I want to disconnect from Nord)

mm, so NordLynx (via the installed Nord application) does work via terminal ('nordvpn connect'), but I'd still like to connect manually using network manager, if possible.

Also, I have a (possibly separate, possibly highly related) issue where network manager itself simply dies (nonfunctional/nonresponsive, internet connection stops working) after x number of minutes or hours. When I try

Code: Select all

sudo service network-manager restart

, which works when network manager hasn't yet died for the session, it doesn't do anything, just hangs indefinitely without actually restarting network manager.

Also, if network manager does happen to become nonfunctional, whenever I shut down the PC, it always fails to actually fully shutdown (it goes to a black screen and displays various processes that are shutting down in the (usually, seconds) that it takes to power off, but stops at something like (paraphrased) "stopping Network Manager" ... failed!", and I end up having to use ctrl + alt + sysrq + reisub to restart the system.

This has been happening more and more periodically the longer I've been using MX (Wildflower). Does anyone have any ideas on what could be done to fix this? Is there anything in particular I should post to give more information - some kind of log somewhere?

[j2mcgreg]

@TinyCritter
We need the complete QSI, not the edited version. FWIW, the QSI output has already been scrubbed of any personal identifiers.

[siamhie]

mm, so NordLynx (via the installed Nord application) does work via terminal ('nordvpn connect'), but I'd still like to connect manually using network manager, if possible.

After you have posted your QSI, take a look at the Settings section. There is an auto-connect function.


https://support.nordvpn.com/Connectivit ... x-Mint.htm