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

After a fresh Gnome install with archinstall, nordvpn login did not work with 'console' So I installed and used 'gnome-terminal' instead and logging in and connecting worked just fine.

I get an error message on installing:

chattr: No such file or directory while trying to stat /var/lib/nordvpn/data/*
error: command failed to execute correctly

Looking at nordvpn-bin.install, it seems the pre_install() function generates this. I've little experience with install files, but it seems that files from the package are referenced before they are installed. The package seems to have been installed correctly though.

For those who are having problems logging in or don't want to use the new method: the decripated method via cli and username/password still works. I got rid of the not connecting to any server problem by restarting the service: sudo systemctl restart nordvpnd.

Hey @gofree,

I had the same error message. In my case, it was the DNS servers I was using at /etc/resolv.conf

From the support article on NordVPN: https://support.nordvpn.com/Connectivity/Linux/1134945702/Change-your-DNS-servers-on-Linux.htm

I was able to get the DNS addresses, and after I executed the below command, I was able to get the connection working again.

nordvpn set dns 103.86.96.100 103.86.99.100

I hope this helps!

On archlinuxarm ( aarch64 ) I get error recently ( guess after last update )

-Whoops! Connection failed. Please try again. If the problem persists, contact our customer support.

Anybody else ?

I have an updated PKGBUILD working. Let me know if you want my contribution by adding me as a co-maintainer.

Happy to help keep the package updated <3

I cannot login at all today via CLI. It works fine in Network Manager GUI with OpenVPN

nordvpn login --legacy
It's not you, it's us. We're having trouble reaching our servers. If the issue persists, please contact our customer support.

nordvpn login unexpected end of JSON input

For the last few years, connecting to nordvpn at the command line to a city like Los Angeles required:

nordvpn c Los_Angeles

(where both parts of the locale name were capitalized, separated by an underscore)

If I try that today, I get this output:

New feature - Meshnet! Link remote devices in Meshnet to connect to them directly over encrypted private tunnels, and route your traffic through another device. Use the `nordvpn meshnet --help` command to get started. Learn more: https://nordvpn.com/features/meshnet/
The specified server is not available at the moment or does not support your connection settings.

Nord Support told me on chat that apparently, the "system" will no longer accept capitalization. They advised to go with all lowercase...so I tried it and I got connected without incident. I tried connecting to numerous other cities, and the Nord-traditional requirement of using a capitalized first letter (e.g., Denver, Seattle, Dallas, etc.) but they won't connect anymore. Now it only takes lower case cities/locales, at least on my machine.

I'm not sure if a recent arch update on my linux box caused this or whether Nord made changes on their servers. Support didn't know either.

Finally, I tried to diagnose the connection problem with this before contacting support:

cat /var/log/nordvpn/daemon.log >> ~/Desktop/daemonlog.txt

but on my computer, there is no such nordvpn directory under /var/log. Doing a "mkdir nordvpn" does not enable nordvpn-bin to place a daemonlog.txt file in /var/log/nordvpn. I'm not sure if this is an issue of directory non-writability or permissions.

Is anyone else having similar experiences? Is the generation of a daemonlog file by nordvpn-bin from our AUR repo no longer able to generate the connection daemonlog file?

@PainfulByte

My understanding is that the login URL is sometimes deliberately weird to get around censorship. Otherwise you couldn't login from countries where NordVPN's main domains are banned.

Personally I hate having to involve the browser, and use "nordvpn login --username X --password Y" instead. Unfortunately they said it might be deprecated at some point, if I recall.

I wouldn't panic about the URL being weird. Put it that way: if you are running a compromised nordvpn executable, you're already thoroughly boned, whether you click a URL or not :-)

@Gamall, I'm using the manual connection using openvpn in the meantime... I can't bring myself to trust such a weird domain name.