Package Details: nordvpn-bin 3.3.1_3-1

Git Clone URL: (read-only)
Package Base: nordvpn-bin
Description: NordVPN CLI tool for Linux
Upstream URL:
Keywords: networking nordvpn openvpn security vpn
Licenses: custom
Conflicts: openvpn-nordvpn
Provides: nordvpn
Submitter: metiis
Maintainer: metiis (Martoko, bubuntux)
Last Packager: Martoko
Votes: 50
Popularity: 6.138823
First Submitted: 2018-08-29 12:13
Last Updated: 2019-09-11 12:00

Pinned Comments

metiis commented on 2018-11-20 11:01

If you're seeing the message "Daemon is unreachable, is systemd running?", that means that the nordvpn daemon is not started. Please run "sudo systemctl enable --now nordvpnd" to start it and run it at boot, or "sudo systemctl start nordvpnd" to only start it once.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 ... Next › Last »

ajgraves commented on 2019-07-09 18:47

@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.

sfranchi commented on 2019-07-09 14:48

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

Archanfel80HUN commented on 2019-07-09 09:49

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.

archifer commented on 2019-07-06 20:20

@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.

s339 commented on 2019-06-13 10:24

@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.

przemub commented on 2019-06-12 16:22


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.

fhdk commented on 2019-06-06 08:53

Removed - another change with 3.1

mudrii commented on 2019-06-05 07:27

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.

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

ABOhiccups commented on 2019-06-05 02:32

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

cipley commented on 2019-05-23 19:03

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.