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

I have also been getting the error message: Whoops! Connection failed. Please try again. If the problem persists, contact our customer support.

Running systemctl status nordvpnd there seems to be a restriction accessing the following path:

Jul 19 07:35:56 primary systemd[1]: Started NordVPN Daemon.

Jul 19 07:37:12 primary nordvpnd[530]: 2019/07/19 07:37:12 open /var/lib/nordvpn/data/.config.ovpn: operation not permitted

Each time I try to connect with nordvpn c another error is appended to systemctl status.

I tried to completely uninstall and remove all system files like ajgraves recommended for a different issue and I could not delete, even when logged in as su, /var/lib/nordvpn .

Version: 3.2.0-4

started getting an error

"Whoops! Connection failed. Please try again. If the problem persists, contact our customer support."

reinstalled but still giving an error.

I have the same problem and couldn't solve it, I use networkmanager and ufw as killswitch now. I wrote this on the archwiki : https://wiki.archlinux.org/index.php/NordVPN#Alternative_Method_:_connecting_to_NordVPN_using_NetworkManager

@sfranchi I had issues too, and I literally had to remove any reference of nordvpn anywhere from my system. As root, type "find / -name nord*" and see what it spits out. There were many locations where nord had leftovers on my system. I removed every directory, old systemd definition, etc I could find anywhere. I then restarted, and re-installed. It appears to be working for me now.

I have the same issue as Archanfel80HUN , but removing the app + config dir and reinstalling did not solve the issue. S

After the upgrade i got this: parsing time "" as "2006-01-02 15:04:05": cannot parse "" as "2006"

Any help?

SOLVED: fully removed the app, deleted the config directory and the systemd service, reinstall and it works now.

@s339 I had this issue I solved it by completely removing the package then restart the system and install it fresh. After that:

$ sudo systemctl enable nordvpnd.service

$ sudo systemctl start nordvpnd.service

And it got back to normal.

@przemub I seem to be having a similar problem to @cipley. Output of systemctl status nordvpndis:

$ systemctl status nordvpnd * nordvpnd.service - NordVPN Daemon Loaded: loaded (/usr/lib/systemd/system/nordvpnd.service; enabled; vendor preset: disabled) Active: activating (auto-restart) (Result: exit-code) since Thu 2019-06-13 12:19:41 CEST; 1s ago Process: 8458 ExecStart=/usr/sbin/nordvpnd (code=exited, status=203/EXEC) Main PID: 8458 (code=exited, status=203/EXEC)

Output of systemd-cgls | grep nord is:

$ systemd-cgls | grep nord | | |-nordvpnud.service | | |-763 /usr/sbin/nordvpnud | -8067 grep --color=auto nord |-nordvpnsd.service |-641 /usr/sbin/nordvpnsd`

The error I get from the recent update is:

$ nordvpn c Whoops! Cannot reach System Daemon.

Any clues? I'm at a loss as to what's going on here. Removing and reinstalling doesn't help.