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

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.

You don't need to restart for the group to be created, that happens when the package is installed. Restarting the services after the group has been added should be enough for users updating the package. You should probably add a post-upgrade note telling people to restart the services after every update.

With 3.8.8-4 the same trouble after enable demon and added to the nordvpn group still not work

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, same here. My solution: Completely remove nordvpn-bin and reinstall following the wiki instructions:

$ sudo groupadd -r nordvpn

$ makepkg -si (or whatever you use to install the AUR package)

$ sudo gpasswd -a <username> nordvpn

After install: sudo systemctl enable --now nordvpnd

And of course:

systemctl enable nordvpnd.service

systemctl start nordvpnd.service

And works fine. Good luck !!!

EDIT: It works now, I only needed to restart Arch apparently!

@xmonster same here, now on 3.8.8-2 and although I see that all of the services are running:

nordvpnd.service loaded active running NordVPN Daemon

nordvpnsd.service loaded active running NordVPN System Daemon

nordvpnd.socket loaded active running NordVPN Daemon Socket

nordvpnsd.socket loaded active running NordVPN System Daemon Socket

And I've added my username to the nordvpn group, I'm still getting this when I ran nordvpn: "Whoops! Cannot reach System Daemon".