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.20.2-4

Dependency included as mandatory earlier as community request.

If you're late for the party and only had updated up to 3.20.2-2.1:

• Simply uninstall nordvpn-bin and install again.

If you're coming from Manjaro or e.g another Arch-based distro with no stable libxml2-legacy package just yet:

• No need to upgrade. It's best keeping with the 3.20.2-3 version. But if you already had, then you can downgrade.

Note from 3.20.2-3

There is now a new package from official repositories named libxml2-legacy and with it two fresh considerations:

• Despite the fact libxml2-legacy was included as optional, it is actually a mandatory dependency. This will change on next NordVPN's release if the legacy support remains.

• This release only removes the previous symbolic link and purges the file within NordVPN library directory, otherwise it would result in an error before installation/upgrade.

Note from 3.20.2-2.1

A patch have been implemented due the absence of libxml2.so.2 after package upgrade to 2.14.2. This fix is not useful if:

• You plan to keep your system update to a specific date until NordVPN officially uses the new library.

• You are from a different distribution, which is a Arch-based one with other repositories, and libxml2 is not yet upgraded.

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

Despite proper configuration of this fully-updated version of nordvpn-bin, particularly when using Nordlynx's Wireguard-based protocol, connection to a server using nordvpn c "server_of_your_choice" works well and does connect to the server and data will flow for a few minutes, but on "this" older 2013 vintage Dell 7737 laptop, using an Intel 7260 WiFi card and kernel-supplied driver, the connection slows gradually over several minutes and then completely stops. Within the Plasma GUI, the NetworkManager wifi icon in the panel ("system tray") shows the requisite "!" indicating limited connectivity. The particular Nord server choice does not seem to matter. The system must be rebooted to restore a functional network stack. I have not experienced this problem using the OpenVPN protocol.

When I access the very same Nord server a minute later on a different (Windows 10 Pro) machine, the server syncs quickly and functions with unfettered throughput. I suspect that the problem on "this" laptop may be a Plasma/NM issue. I have also not been able to replicate this deterioration in Gnome or classic Gnome, nor have I experienced it in console mode either as root or as a standard user.

I sorted out my issues with the latest release. Seems that just nordvpn connect no longer picks a server near you geographically. It previously did so automatically. No worries. Specify country and city all is good.

@tyler19820201: By referring to the news I was highlighting the fact that developers of AUR package managers needed to update their code, not yourself. So, you just need to get your latest/favourite package manager 'updated'. You then can manually build that package, most have been updated. I use Yay today: https://aur.archlinux.org/packages/yay/

@esdaniel: i was trying to update my ssh keys for AUR but unable to find the file includes the keys. however if i try to run ssh -keygen -R aur.archlinux.org in terminal i will get no file or directory error...How should i update SSH keys then?? ssh -keygen -R aur.archlinux.org

There is definitely some different with the 3.8.3-1 release. It does work but I can only connect to 1 server in Costa Rica. Additionally if I issue nordvpn logout and try to login again providing email address and password it fails to connect every time. Anyone else experiencing this?

3.7.4-1 does not exhibit this behavior.

@tyler19820201: If you can download https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=nordvpn-bin, extract to folder and run makepkg, then run pacman -U <package> successfully you should update/change your pkg manager. BTW there were recent key changes for AUR: https://www.archlinux.org/news/aur-migration-new-ssh-hostkeys/

On my package manager still only nordvpn-bin 3.7.4-1 available only no 3.8.3-1... On the terminal i am getting warning about update available but nothing in my package manager....Anyway until 3.7 still works fine i am okay with that.

Sorry, everyone. NordVPN team reminded me to use whitelist command ($ nordvpn whitelist add subnet <my_subnet/mask>) so issue resolved :-)

Just a heads-up to users... sometime in last couple of days something 'changed'. Before then, no issue pinging RFC1918 (local) addresses then today no joy when VPN 'connected'. Disconnect VPN and can ping, thus it's a firewall issue with how NordVPN interprets existing rules and overlays their own binding to the VPN host IP and dropping 'everything' else based on my tests today. Workaround is f'ing tedious till I script it... first, before connecting to VPN, do an iptables-save of the good conf. After connecting to NordVPN, check the NordVPN IP given that is in the updated firewall rules (take note of those new rules), then restore old fire rules and add the NordVPN rules thereafter thus ensuring LAN Allow is before local nic DROP statement etc. etc..

The package is out of date and no longer works for me. If you have time, please update this to the newest version (3.8.1 https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/) which fixed my issue