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

Manjaro Arm64

Failed to prepare transaction: could not find or read package

I downloaded the screenshot and did makepkg but it doesn't even create a installable package which might be the issue or part of it.

Great! Thanks!

@speedytux, the one linked on the website is nearly 2 years old.

$ wget https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/nordvpn-release_1.0.0_all.deb
$ bsdtar -tvf nordvpn-release_1.0.0_all.deb
-rw-r--r--  0 0      0           4 Apr 15  2019 debian-binary
-rw-r--r--  0 0      0         402 Apr 15  2019 control.tar.gz
-rw-r--r--  0 0      0        3140 Apr 15  2019 data.tar.xz
-rw-r--r--  0 0      0        1262 Apr 15  2019 _gpgbuilder
$ wget https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/nordvpn_3.8.9_amd64.deb
$ bsdtar -tvf nordvpn_3.8.9_amd64.deb 
-rw-r--r--  0 0      0           4 Dec 28 08:07 debian-binary
-rw-r--r--  0 0      0        6776 Dec 28 08:07 control.tar.xz
-rw-r--r--  0 0      0    10440308 Dec 28 08:07 data.tar.xz
-rw-r--r--  0 0      0        1267 Dec 28 08:19 _gpgbuilder

Is this deb package the same offered on the NordVPN website? That one has the 1.0.0 release version and this one 3.8.9. Would you clarify?

I've had the same issue as @Zeros with all 3.8.x releases for the past several months, including the recent ones with group-related issues. I've been reverting back to 3.7.4 for quite a while, after attempting to update after every new 3.8.x release. I'm still able to connect fine with 3.7.4 today.

I just today found this post. Disabling the killswitch before connecting, I've finally been able to connect with 3.8.9-- the first time I've been able to connect with any 3.8.x release. (Re-enable killswitch after connecting.)

@Zeros: Are you sure the service is running? If so, have you by chance configured an $HTTP_PROXY? I discovered that this can interfere with communications between the client and service, but I found workaround in case you need it.

I've added myself to the nordvpn group and rebooted, but no matter what, I'm unable to log into my account via "nordvpn login" or "sudo nordvpn login", keep getting "Whoops! We're having trouble reaching our servers. Please try again later. If the issue persists, please contact our customer support." after about 30 seconds. I can connect through openvpn, and on the Android app just fine. Version: 3.8.9-1

Any plans to add the armel (armv6l) version? The deb in the same path as the others.

Would be even better to use the $USER variable instead of whoami

Pedantic note: would be nice to use whoami instead of the USERNAME placeholder.