6

I'm in China and on Ubuntu 16.04 and have installed NordVPN through apt. When I run nordvpn login or nordvpn X I just get:

"Whoops! Cannot reach User Daemon."

I also tried running nordpnsd which runs without output and then terminates and then nordvpnud. This runs without output until I try "nordvpn login", at which point it goes:

2019/05/30 12:51:49 [Error] rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial unix /run/nordvpnsd.sock: connect: no such file or directory
8

If you're seeing Daemon is unreachable, is systemd running? or Whoops! Cannot reach System Daemon. your NordVPN daemon isn't currently running.

To start the daemon, and have it also enabled the next time you boot, run:

sudo systemctl enable --now nordvpnd.service

To just start the daemon once and have it disabled the next time you reboot your system, run:

sudo systemctl start nordvpnd
1

NordVPN seems to require two daemons: nordvpnsd and nordvpnud. These are provided in the install package and reside in /usr/bin. They are binaries and not scripts, so can't be modified.

The error message probably means that the daemon was not found in the user context. The reason is, I believe, that nordvpnud is supposed to be run per user. I would suggest to run it yourself, rather than during startup.

If you wish to run it during startup, use the chpst -u:

exec nordvpnsd 2&>1
exec chpst -u <user-account> nordvpnud 2&>1

As I'm not using NordVPN, I cannot go any further than that. For more information, see this post.

2
  • I tried running nordpnsd which runs without output and then terminates and then nordvpnud. This runs without output until I try "nordvpn login", at which point it goes: 2019/05/30 12:51:49 [Error] rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial unix /run/nordvpnsd.sock: connect: no such file or directory" – ezekiel May 30 '19 at 5:03
  • If they were started by the boot, you should stop at least nordvpnud before running it under user. – harrymc May 30 '19 at 7:10
1

sudo service start nordvpn

or

sudo systemctl start nordvpn

For me none of the above worked, but they were right that a service was needed so I checked all my services after installing nordvpn sudo service --status-all and found nordvpn (no d). I'm assuming they changed the name?

1

Just in case somebody else has that issue; for me worked adding myself to nordvpn group:

sudo usermod -aG nordvpn <username>
newgrp nordvpn

From: https://www.reddit.com/r/nordvpn/comments/kfewlb/solution_whoops_cannot_reach_system_daemon_after/ggtiq5t/?utm_source=reddit&utm_medium=web2x&context=3

nordvpnd service was already running.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.