Version 5.1.0 is causing a 2 minute delay at boot before the daemon starts. Is anyone else experiencing this?
Jun 20 12:40:14 arch-charlie systemd[1]: Starting NordVPN Daemon Socket...
Jun 20 12:40:14 arch-charlie systemd[1]: Listening on NordVPN Daemon Socket.
Jun 20 12:42:15 arch-charlie systemd[1]: Started NordVPN Daemon.
These are the same events with version 5.0.0 installed.
Jun 20 12:53:28 arch-charlie systemd[1]: Starting NordVPN Daemon Socket...
The delay is the same each boot, 2 minutes, so it appears something is timing out before it starts.
Jun 20 12:53:28 arch-charlie systemd[1]: Listening on NordVPN Daemon Socket.
Jun 20 12:53:28 arch-charlie systemd[1]: Started NordVPN Daemon.
Pinned Comments
Mxzcabel commented on 2023-03-23 20:37 (UTC) (edited on 2026-06-15 20:33 (UTC) by Mxzcabel)
"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."
martoko commented on 2020-12-20 09:10 (UTC) (edited on 2020-12-20 09:12 (UTC) by martoko)
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 nordvpndYou might not have been added to the nordvpn group
Add yourself:
sudo gpasswd -a USERNAME nordvpnAnd then restart in order for the group to be created:
reboot