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

@cipley

Restart the system. (If you have installed a new kernel version simultaneously, it might have caused the problem.)

If it's not that, paste the result of command systemctl status nordvpnd.

Removed - another change with 3.1

After latest updated to version nordvpn-bin 3.1.0_4-1 and after fixing startup issue with Daemon now I can't make nordvpn to connect and getting below error. Is anybody else have the same issue?

We're having trouble configuring your DNS settings. If the issue persists, please contact our customer support

For now, I managed to connect using openvpn. https://support.nordvpn.com/Connectivity/Linux/1047409422/How-can-I-connect-to-NordVPN-using-Linux-Terminal.htm

EDIT: Seems issue is with systemd-resolved service that manages /etc/resolv.cong and needs to be stopped 1st before connecting to nordvpn

After a new update. I get this error message.

Whoops! Cannot reach System Daemon.

Edit: You have to open Terminal and enter this command.

sudo systemctl enable nordvpnd.service

I can't seem to connect to nordvpn.

The last successful command was login. Then, anything else yields this:

Whoops! Something went wrong. Please try again. If the problem persists, contact our customer support.

@Ubermensch - I ran into the same issue (on GalliumOS in my case), and ultimately just uninstalled and reinstalled via apt. Some of the non-reinstallation options have worked in the past but this time around seemed to require the reinstall

I report frequently "Whoops! Cannot reach User Daemon." error message when i use nordvpn command. Removing ~/.config/nordvpn/ don't fix it

I get the issue "systemclt" is the alias of "sudo systemctl" in Antergos linux. https://bit.ly/2PZV25R

Anyone else having issue whitelisting ports for access on the local lan?

nordvpn whitelist add port 1234

transport is closing or Whoops! Cannot reach User Daemon.

Both nordvpnsd and nordvpnud are showing as running.

EDIT: fixed by removing ~/.config/nordvpn/ and reconfiguring.

Hey everyone! For some reason outgoing traffic halts when I connect to a server:

• I login with my credentials: Welcome to NordVPN! You can now connect to VPN by using 'nordvpn connect'.
• nordvpn c ireland dublin: Connecting to Ireland #21 (ie21.nordvpn.com) You are connected to Ireland #21 (ie21.nordvpn.com)!
• ping google.com returns nothing, my connection goes down.

I checked the service logs (through journalctl), looks ok. Only a couple of lines that say "kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized" but after a quick search on google it seems to be unrelated.

Any ideas?

System:

Manjaro 18.0.4

Kernel 4.14.93-rt53-MANJARO

NordVPN Version 3.0.0-4