NordVPN won’t stay connected on Linux. You literally have to write a script that runs in a loop 24/7, to detect when the connection stalls, then try gently reconnecting, or gently restarting, or if those don’t work then sudo kill -9
all related processes, services, and socket. Then restart everything in the right order.
It’s ridiculous.
Seems fine on Windows though.
My script also sets the killswitch feature every time it reconnects, just in case that gets disabled - which does happen occasionally. (The point is to make sure there’s no internet connectivity while it resets.)
Depending on usage, my script can restart NordVPN hundreds of times per day.
If torrenting, it often gets so irreversibly fucked up, that a full OS reboot is required. I don’t know if it’s the volume of bits, or the protocol, that causes it to get so fucked up.
I once tried to run it on a pihole/wifi server. The amount of traffic caused it to hose itself so often, I eventually had to have it reboot itself every night, but even that wasn’t enough. Finally had to remove it.
Of course I’ve tried every “fix” imagineable, including the different protocols and different settings. No fix.
It’s been this way for years. The only reason I haven ditched it for good, is because I’ve literally been too busy! And my script for the most part keeps things going. I just don’t torrent.
I’ve had NordVPN installed on a dozen different (mostly) real and virtual installs, from Ubuntu 18.04 to latest Debian Test to OpenSUSE Tumbleweed - and everything in between (eg all versions of Ubuntu since 18.04 which NordVPN won’t run on anymore). And on all kinds of different hardware from brand new to ancient, from wired to wireless, etc. And on dozens if not hundreds of different host networks. (E.g. other homes, airports, ethernet with gigabit fiber or cable internet, etc.)
It works exactly the same on all of them.