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

What is?? "It's not you, it's us. We're having trouble reaching our servers. If the issue persists, please contact our customer support." I don't connected. Help, please. Thanks.

PS " If your password is over 48 characters" My pass is less 12

The connection was established using nordpy.!!

Can't download this package in a country that blocks nordvpn servers (like China).. I got this to work by editing PKGBUILD locally and replacing "nordvpn.com" in every sentence in the sources to the alternative website provided officially by Nordvpn >> "cqxqlbe.site".. You should do this here on Aur

One issue I ran into when I switched over to Linux from Windows was my password length. When logging in from the terminal you will get this error "It's not you, it's us. We're having trouble reaching our servers. If the issue persists, please contact our customer support." If your password is over 48 characters. After a few hours of frustrating conversations with tech support and trial and error I finally figured that out on my own though so hopefully it will save a few people some headaches.

@typewar

Worked for me as well (connected for 24 hours as of writing), thanks a lot!

For the last couple of months, I've experienced random disconnects (nordvpnd freezes, become unresponsive) while using NordLynx technology. Back and fourth with support didn't exactly help much.

It turns out I had to install wireguard.

https://www.reddit.com/r/nordvpn/comments/opnhlj/problems_with_nordlynx_on_linux/h6yarhx/

I can confirm it has been running stable now for 12 hours straight.

Can this be added as a recommendation ?

This thread may be of some help if you are have connection issues.

https://bbs.archlinux.org/viewtopic.php?id=268275

@manja2 I have the exact same issue as you and it still doesn't work, I wonder what they broke on their end.

@doctorcolossus hi and yes, one of the things I forgot to mention yesterday is 'we' deleted some conf files too... anyhow it's currently working for me with the following:

Technology: NordLynx Firewall: enabled Kill Switch: disabled CyberSec: disabled Notify: enabled Auto-connect: enabled IPv6: enabled DNS: 127.0.0.1 < Unbound DoH resolver :-)

@esdaniel: I also contacted Nord support and went through some of the same steps (deleting settings data, temporarily disabling ipv6, etc.). What finally worked was the guy asked me to downgrade to 3.8.4. Then on trying to connect it blocked my internet connection and hung for about a full minute, but eventually finally connected. Later I decided to upgrade back to 3.10 and... it also worked. Very strange. I am thinking it may be / have been (?) a temporary server-side issue.

Did you get yours working again?