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

This is probably an upstream issue, but shouldn't nordvpn.service and nordvpn.socket be writable only by root?

From journalctl -f:

systemd[1]: Configuration file /usr/lib/systemd/system/nordvpnd.service is marked world-writable. Please remove world writability permission bits. Proceeding anyway.
systemd[1]: Configuration file /usr/lib/systemd/system/nordvpnd.socket is marked world-writable. Please remove world writability permission bits. Proceeding anyway.

Apparently, a problem at NordVPN appears to have been responsible for the NordLynx protocol failure earlier today. Re-installing nordvpn-bin works fine now.

Despite having enabled the nordvpn daemon and adding my username to the 'nordvpn' group, and having been a three-year user of NordVpn, today, I can connect to no servers that I desire by server number or city, and in terminal, when waiting for my credentials to authenticate and sign into a specific server, (which took 2 minutes!) the command 'nordvpn status' yields my own town and whatsmyip.org's location feature reveals a map of my street address using their google maps applet. (Of course, I have disabled WebRTC and Geo-enablement in Firefox, and the nord app still betrays my location).

Here's a sample of what I get on terminal: https://pastebin.com/embed_js/Yd9YdkNu

I selected L.A., I got Phoenix. Another time, selected Dallas, I got Phoenix. But I was not protected by the encrypted tunnel. My house was dead center on the map in Phoenix at https://whatsmyip.org.
Just removed nordvpn-bin; installed nordpy, which works.

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