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.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 version 3.0.0 there are now two systemd services you need to start:

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

If you are using Antergos then please be aware that systemctl is by default aliased to sudo systemctl in .bashrc.aliases. You might want to comment out the line alias systemctl='sudo systemctl' to disable the alias.

You will probably need to reconfigure the nordvpn. Look at the output of systemctl status nordvpnd after attempting to run the daemon.

i have being trying to update to 3.0.0_4 but i'm getting an error saying that the daemon is not running, when it is, not sure what's up tbh

i have a question and cant find a answer: does this support multihop or double vpn?

When I am trying to connect to any server, it is not responding. Any idea?

The output is the following:

$ nordvpn connect <server>

Connecting to <server>

@archieslove, i did the exact same before and flagged it as out-of-date. Customer support confirmed this older version has been blacklisted due to security bug.

I contacted the Nord support regarding the connection issues 'Whoops! We can't connect you to 'uk777.nordvpn.com'. Please try again. If the problem persists, contact our customer support.'

It seems they have pushed 2.2.0-3 to fix this issue. Arch package is currently on 2.2.0-2.

Anybody facing DNS leaks after boot-up until we reconnect it ?

@hE-01 I solved 'transport is closing' by uninstalling nordvpn-bin, then removing the folder '.config/nordvpn', and reinstalling again. It asked me again for credentials, but after that it worked.