Arch Linux User Repository

"Please, do not flag this package as out-of-date until there's the official release on Github page."

"Maybe the announcement is delayed, but wait for some other possible forward release, which is patching the previous one before the actual publishing."

Note from 3.19.1:

The repository's hierarchy has been updated and a slightly divergence comes with it. It was from:

/debian/pool/main

To now as:

/debian/pool/main/n/nordvpn

Any previous commits you may like to try in the future will need a manual mediation to replace old links in favor of the new ones.

Note from 3.19.0:

This version introduces new libraries being used by NordVPN. I have created symbolic links and committed a patch for it not interposing with already existing libraries (like sqlite3). Although this is not a big deal, If you, however, upgraded nordvpn-bin before the fix and noticed some library-related issue from sqlite lately, I suggest reinstalling the affected package.

Note from 3.17.4v:

The previous bug exposing DNS servers is fixed.

Note from 3.17.3v:

Caution! This version needs heed while using it and should be avoided. I strongly advice downgrading to 3.17.2 and wait for a new version or patching. Some big problems are:

• There's DNS leak present. Your original ISP servers can be exposed, as reported already on #343 issue.

• Unable to connect on nordvpn servers. Your journal might show the follow output: networker setting dns: setting dns with resolvectl: setting dns with resolvectl: Failed to set DNS configuration: Could not activate remote peer: activation request failed: unknown unit.: exit status 1

  After restarting resolve with systemctl restart systemd-resolved.service you may get it working again, enough for connecting normally, as reported, but not exclusively an ARM platform issue, on #342.

Also huge thanks for the community warnings in prior comments before I could've noticed all.

Note from 3.16.2v:

As the published note from the version above has mentioned on Github's page:

• Logging in with a username and password is no longer available in the terminal.

Please, consider using a token to logging in from now on.

Note from 3.16.0v:

The 'countries.dat' may differ between versions. Be aware to remove the file before upgrading the package.

If you're seeing the message "Daemon is unreachable, is systemd running?", then one of two things is probably happening.

The nordvpn daemon might not be started
Start it using:
sudo systemctl enable --now nordvpnd

You might not have been added to the nordvpn group
Add yourself:
sudo gpasswd -a USERNAME nordvpn
And then restart in order for the group to be created:
reboot

@hydra: Yes, I have the same problem.

On 3.7.3 is anyone else having iptables rules messed up after disconnect? It seems iptables rules are not restored to pre-vpn connection state after disconnecting or stopping the daemon. I can only get traffic through after manually resetting iptables.

Also having the error "Whoops! Connection failed. Please try again." or "Whoops! We couldn't connect you to 'germany'. Please try again. " ... any idea how to solve this issue ?!

• either through OpenVPN, either through Nordlynx ("nordvpn set technology openvpn" then "... nordlynx")
• either from my own country ("nordvpn connect"), either from another one ("nordvpn connect Germany")
• same problem after restarting nordvpnd.service through systemctl ("systemctl stop nordvpnd && systemctl start nordvpnd")
• same problem after forcing a logout/login ("nordvpn logout" then "nordvpn login")
• same problem after removing everything and reinstalling ("yay --remove nordvpn-bin && sudo rm -rf /var/lib/nordvpn/")

My account is valid (from their website) : "Private and secure internet access (VPN)Active 3 Year Subscription · Next payment at Jan 11th, 2021 "

But from time to time i get : "Opening the web browser... If nothing happens, please visit https://join.nordvpn.com/order/?utm_medium=app&utm_source=linux Your account has expired. Renew your subscription now to continue enjoying the ultimate privacy and security with NordVPN."

Of course most of the time i get "Whoops! We couldn't connect you to 'Germany'. Please try again. If the problem persists, contact our customer support."

Once contacted, support is not helpful at all ("Archlinux is not supported, we only support Ubuntu/Debian"). Interestingly, if i set up a local debian docker container (from scratch) and then install the supported nordvpn package ... i still have the exact same problems ...

I have pb with Nordvpn since 4 days : Whoops! Cannot reach System Daemon.

Anyone having problems when trying to disconnect, and killswitch is on? [NordLynx and CyberSec enabled in settings]

Edit: The package is up-to date, showing the latest version 3.7.2.

According to the official documentation, the wireguard-tools package is no longer needed for NordLynx to work. In the first NordLynx implementations, there was an explicit indication of the installation of the kernel modules and support tools for WireGuard. I've tested it and it works 100%!

https://support.nordvpn.com/Connectivity/Linux/1362931332/How-can-I-use-NordLynx-in-the-NordVPN-app-for-Linux.htm

Newer version has been available for a few days now.

ipset should be added as dependency, it's needed to disconnect (at least with nordlynx)

Would it be possible to add aarch64 support back? It's upstream at https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/nordvpn_3.7.1_arm64.deb (I don't know why the name changed to arm64 instead of aarch64, but I'm running this on aarch64 right now).