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

How can we choose between countries normal/P2P/Double/TOR? When I try to connect to Netherlands it picks the onion server by itself. Also, the man page says something about groups. What is that? I cannot find any reference to groups, apart from the 3 examples in the man page.

Warning: the systemd unit files included in this package give NordVPN full access to your entire system. Adding sandboxing options in the [Service] section of each systemd service file can reduce the security risks.

For example the following options can be added in nordvpnsd.service:

NoNewPrivileges=true
ProtectSystem=strict
ReadWritePaths=/var/lib/nordvpn /var/log/nordvpn
TemporaryFileSystem=/run
ProtectHome=true
PrivateTmp=true
ProtectKernelModules=true
ProtectControlGroups=true
InaccessiblePaths=/mnt
SystemCallFilter=@system-service
SystemCallErrorNumber=EPERM

See man systemd.exec for details.

I love you so much guys. I did what @RidderJoris mentions and then entered all the commands without "sudo". It worked perfectly. Happy days!

WOW! @RidderJoris, you are absolutely right, I didn't even think to check there. It's strange indeed that Antergos aliases systemctl >_> but you are absolutely right, that did the trick thanks so much!

@hahnt9009 I found the issue. In Antergos linux "systemclt" is the alias of "sudo systemctl" which makes no sense to me. Therefore if you comment the line "alias systemctl='sudo systemctl'" in ".bashrc.aliases" it will work fine ;)

I had the same issue that @RidderJoris and @hahnt9009 are reporting.

"Failed to connect to bus: No such file or directory" when using systemctl --user enable --now nordvpnud.

When using nordvpn status I receive Whoops! Cannot reach User Daemon.

I'm also using Antergos linux.

First I had to sudo rm /var/lib/nordvpn/data before the update could get through.

Then, after running

sudo systemctl enable --now nordvpnsd
systemctl --user enable --now nordvpnud

I ran nordvpn connect (without sudo), and it worked.

@Ridder Joris Interesting; I as well, am on Antergos. I recently had my wife (also an Antergos user) attempt to update. She is now experiencing the issue. So it appears it may be Antergos related? I'll look into openpyn-nordvpn as well thanks. Will keep attempting to research this more and keep up with any updates on nordvpn-bin, feel a bit lost without it!