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

Hi, keeps nagging me to update the client. Any chance of updating this to "nordvpn_3.3.1-1_arm64.deb"? thanks for your work

@esdaniel Actually no, I didn't find a fix. The autostart functionality is very fragile and from time to time it stops working.

sfncmp1729: RE: autoconnect, me2 :-( Did you find a fix? I resorted to autostart script until 'we' can resolve this.

Could you please add awk to the list of dependencies?

When I try to connect I see this message: "transport is closing". On my laptop it works fine, but on my Raspberry it doesn't. The daemon is up and running. Thx

Add missing armel architecture. It's for RPI1 and RPI zero devices (devices with armv6 architecture).

It's also provided by NordVPN: https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/

Please replace wireguard-arch with WIREGUARD-MODULE, as this is provided by wireguard-arch, wireguard-lts, and wireguard-dkms

Add missing armel architecture. It's for RPI1 and RPI zero devices (devices with armv6 architecture).

It's also provided by NordVPN: https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/

Anyone else having problems with autoconnect? Any hint on how to solve this issue? Also, I suspect that the killswitch is not working as it should. For example, if I disconnect from nordvpn after a while my downloads resume.

@Martoko That link resolved my issue. If anyone else has the problem, I was needed to install linux headers and select my kernel.

sudo pacman -S linux-headers

Thanks!