Installed 3.8.8-1 and now I can't connect because the system daemon can't be reached.
This is what I see in journalctl after I tried to run the enable nordvpnd command. Any thoughts?
Dec 17 18:48:47 systemd[1]: nordvpnd.socket: TCP_NODELAY failed: Operation not supported
Dec 17 18:48:47 systemd[1]: Starting NordVPN Daemon Socket.
Subject: A start job for unit nordvpnd.socket has begun execution
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A start job for unit nordvpnd.socket has begun execution.
The job identifier is 1175.
Dec 17 18:48:47 systemd[1542]: nordvpnd.socket: Failed to resolve group nordvpn: No such process
Dec 17 18:48:47 systemd[1]: nordvpnd.socket: Control process exited, code=exited, status=216/GROUP
Subject: Unit process exited
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
An ExecStartChown= process belonging to unit nordvpnd.socket has exited.
The process' exit code is 'exited' and its exit status is 216.
Dec 17 18:48:47 systemd[1]: nordvpnd.socket: Failed with result 'exit-code'.
Subject: Unit failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The unit nordvpnd.socket has entered the 'failed' state with result 'exit-code'.
Dec 17 18:48:47 systemd[1]: Failed to listen on NordVPN Daemon Socket.
Subject: A start job for unit nordvpnd.socket has failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A start job for unit nordvpnd.socket has finished with a failure.
The job identifier is 1175 and the job result is failed.
Dec 17 18:48:47 systemd[1]: Dependency failed for NordVPN Daemon.
Subject: A start job for unit nordvpnd.service has failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A start job for unit nordvpnd.service has finished with a failure.
The job identifier is 1084 and the job result is dependency.
Dec 17 18:48:47 systemd[1]: nordvpnd.service: Job nordvpnd.service/start failed with result 'dependency'.
Dec 17 18:48:47 sudo[1512]: pam_unix(sudo:session): session closed for user root
Dec 17 18:48:47 audit[1512]: USER_END pid=1512 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Dec 17 18:48:47 audit[1512]: CRED_DISP pid=1512 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'
Pinned Comments
Mxzcabel commented on 2023-03-23 20:37 (UTC) (edited on 2025-05-12 22:12 (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."
Note from 3.20.2-4
Dependency included as mandatory earlier as community request.
If you're late for the party and only had updated up to 3.20.2-2.1:
If you're coming from Manjaro or e.g another Arch-based distro with no stable libxml2-legacy package just yet:
Note from 3.20.2-3
There is now a new package from official repositories named libxml2-legacy and with it two fresh considerations:
Despite the fact libxml2-legacy was included as optional, it is actually a mandatory dependency. This will change on next NordVPN's release if the legacy support remains.
This release only removes the previous symbolic link and purges the file within NordVPN library directory, otherwise it would result in an error before installation/upgrade.
Note from 3.20.2-2.1
A patch have been implemented due the absence of libxml2.so.2 after package upgrade to 2.14.2. This fix is not useful if:
You plan to keep your system update to a specific date until NordVPN officially uses the new library.
You are from a different distribution, which is a Arch-based one with other repositories, and libxml2 is not yet upgraded.
Note from 3.19.1:
The repository's hierarchy has been updated and a slightly divergence comes with it. It was from:
/debian/pool/main
To now as:
/debian/pool/main/n/nordvpn
Any previous commits you may like to try in the future will need a manual mediation to replace old links in favor of the new ones.
Note from 3.19.0:
This version introduces new libraries being used by NordVPN. I have created symbolic links and committed a patch for it not interposing with already existing libraries (like sqlite3). Although this is not a big deal, If you, however, upgraded nordvpn-bin before the fix and noticed some library-related issue from sqlite lately, I suggest reinstalling the affected package.
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
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:
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.
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 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