How you make it automatically connect to the closest server when you start manjaro?
On plasma, I made a simple script nordvpn_startup.sh, which is added to KDE’s “Autostart” scripts in system settings. It has the following:
#!/bin/bash
nordvpn set autoconnect on
nordvpn set killswitch on
sleep 10s
nordvpn c
It used to work fine some time ago, but now whenever I start the system, it won’t connect, and find myself having to manually open the terminal and typing nordvpn c every time I start my computer, which is annoying. Is there a way I can call that command whenever my computer connects to a wifi network?
@linux-aarhus I’m not the only one experiencing the issue that 3.8.5 connects only to costa rica. Others have commented the same in the link I shared to the AUR package. I also just tried the next version, and still behaved the same way."
I used to rely on the autoconnect enabled feature, but it only works sometimes. I was constantly having to mannually check if my vpn was connected or not, because it would simply ignore the autoconnect feature about 50% of the time.
I am now using the network manager instead of the CLI. I imported a ovpn configuration (downloadable from nordvpn website) into the NM, and then you can choose to autoconnect to this vpn whenever I connect to my WLAN. It autoconnects 100% of the time without manual intervention, and it provides me with a visual indicator (A “lock” symbol within the “wifi” symbol) that stays displayed for as long as the connection is active. In contrast, the CLI only provides notifications whenever it connects or disconnects, but you can’t simply monitor the current status unless you type nordvpn status in the terminal.
So I’m happier now.
@sawdoctor I haven’t tried that. How’s the experience so far? I simply got annoyed at how the CLI doesn’t really autoconnect most of the time, and sometimes it asks me for my login credentials again. It’s incredibly annoying.