Package Details: nordvpn-bin 3.1.0_6-1

Git Clone URL: https://aur.archlinux.org/nordvpn-bin.git (read-only)
Package Base: nordvpn-bin
Description: NordVPN CLI tool for Linux
Upstream URL: https://nordvpn.com/download/linux/
Keywords: networking nordvpn openvpn security vpn
Licenses: custom
Conflicts: openvpn-nordvpn
Provides: nordvpn
Submitter: metiis
Maintainer: metiis (Martoko, bubuntux)
Last Packager: Martoko
Votes: 39
Popularity: 7.224064
First Submitted: 2018-08-29 12:13
Last Updated: 2019-06-13 17: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

1 2 3 4 5 6 ... Next › Last »

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

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

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

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.

colearrington commented on 2019-05-21 16:03

@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

Ubermensch commented on 2019-05-15 08:59

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

aleksz commented on 2019-05-13 01:45

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

NygelLyndley commented on 2019-05-11 11:57

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.