Package Details: nordvpn-bin 3.5.0_1-1

Git Clone URL: https://aur.archlinux.org/nordvpn-bin.git (read-only, click to copy)
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: 56
Popularity: 4.98
First Submitted: 2018-08-29 12:13
Last Updated: 2019-12-09 14:18

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 »

hydra commented on 2019-12-12 12:26

I have had similar issues like the @doctorcolossus, but after trying different settings, it seems NordLynx buggy. Sometimes it works, sometimes it does not. Using technology set to openvpn always works in my case.

I also installed networkmanager-openvpn as a backup for when I do not feel like messing with nordvpn-bin. So far, the NetworkManager openvpn plugin has not given me any issues, so I am convinced it is something with NordLynx.

doctorcolossus commented on 2019-12-11 18:47

@archnix: My issue is not the same as klodep's. My issue is that the userspace console application is not able to communicate with the system daemon.

I don't think it has anything to networking. My resolv.conf is set by dhcp. Running any nordvpn command (including the ones you suggested: "nordvpn c de" and "nordvpn d") resulted in the "Whoops! Cannot reach system daemon" message. So this error occurs before a connection is even attempted - I was not even able to enter my login credentials - the command I wanted to run was "nordvpn login" - but that resulted in the same error message as always, so the stage of even attempting to initiate a connection was never even reached.

I am also pretty confident that nothing is wrong with my network configuration, since 1) that is what I am using to write to you now; 2) I was able to connect to NordVPN via openvpn using the open-source application openpyn; 3) I have now switched to Mullvad and it is working fine over either WireGuard or openvpn; and 4) I previously used Cyberghost and had no connection problems with it either.

For all of the reasons above, I highly doubt the particular problem I was experiencing had anything to do with network issues.

Unfortunately I am no longer able to help troubleshoot this issue, as I have now cancelled my NordVPN subscription, requested a refund, and switched to Mullvad, whose client works seamlessly out of the box on Arch.

archnix commented on 2019-12-11 11:20

@Lyxmyx @doctorcolossus @klodep

Your issues with nordvpn-bin is a symptom of something fundamentally wrong with your network configuration or maybe a result of using sudo connect - creating a config in the wrong place or with wrong permissions in home folder.

❯ nordvpn c de
Connecting to Germany #442 (de442.nordvpn.com)
You are connected to Germany #442 (de442.nordvpn.com)!
❯ cat /etc/resolv.conf
# Generated by resolvconf
nameserver 103.86.96.100
nameserver 103.86.99.100
❯ nordvpn d
You are disconnected from NordVPN.
How would you rate your connection quality on a scale from 1 (poor) to 5 (excellent)? Type 'nordvpn rate [1-5]'.
❯ cat /etc/resolv.conf
# Generated by NetworkManager
search localnet.lan
nameserver 10.10.1.6

jackhistoria commented on 2019-12-11 10:04

@Lyxmyx until nordvpn-bin is stable it might be a good solution for you to use https://github.com/jotyGill/openpyn-nordvpn - it double checks the resolve config and works very nice and the code is clean written. It also adds server load checks to linux and yeah, its in the aur. I use it as second layer over my nordvpn-bin even if the killswitch works nice in the script there still is a connection if it doesn't (direct on a 30 bucks open wrt 5G china router)

Hope that helps you

Lyxmyx commented on 2019-12-11 08:43

It no longer updates my resolv.conf after I disconnect from the VPN connection.

So then I'm left with an unusable internet connection because I can't access the DNS servers listed in my resolv.conf because you have to be connected to the VPN to access them.

And I can't bring the dhcpcd service to regenerate the resolv.conf unless I reboot.

It used to update the resolv.conf after I disconnected from the VPN.

doctorcolossus commented on 2019-12-06 11:41

I haven't updated the kernel since installing nordvpn. This is my first attempt to install nordvpn and it has not worked for me at all yet. I tried completely removing nordvpn as suggested at the Manjaro forum link you provided, by deleting /var/lib/nordvpn/. There were no immutable files there, in my case. I then restarted, reinstalled, reenabled the systemd service, and restarted again. The nordvpn command still gives me the error: "Whoops! Cannot reach System Daemon."

# nordvpn login
Whoops! Cannot reach System Daemon.
# uname -a
Linux xps3 5.4.1-arch1-1 #1 SMP PREEMPT Fri, 29 Nov 2019 13:37:24 +0000 x86_64 GNU/Linux
# systemctl status nordvpnd.service
● nordvpnd.service - NordVPN Daemon
     Loaded: loaded (/usr/lib/systemd/system/nordvpnd.service; enabled; vendor preset: disabled)
     Active: active (running) since Fri 2019-12-06 04:31:43 MST; 11min ago
TriggeredBy: ● nordvpnd.socket
   Main PID: 29011 (nordvpnd)
      Tasks: 13 (limit: 19034)
     Memory: 33.8M
     CGroup: /system.slice/nordvpnd.service
             └─29011 /usr/sbin/nordvpnd

Dec 06 04:31:43 xps3 systemd[1]: Started NordVPN Daemon.
# systemctl status nordvpnd.socket
● nordvpnd.socket - NordVPN Daemon Socket
     Loaded: loaded (/usr/lib/systemd/system/nordvpnd.socket; disabled; vendor preset: disabled)
     Active: active (running) since Fri 2019-12-06 04:31:43 MST; 11min ago
   Triggers: ● nordvpnd.service
     Listen: /run/nordvpnd.sock (Stream)
     CGroup: /system.slice/nordvpnd.socket

Dec 06 04:31:43 xps3 systemd[1]: Stopping NordVPN Daemon Socket.
Dec 06 04:31:43 xps3 systemd[1]: nordvpnd.socket: TCP_NODELAY failed: Operation not supported
Dec 06 04:31:43 xps3 systemd[1]: Listening on NordVPN Daemon Socket.

doctorcolossus commented on 2019-12-04 09:10

@archnix: It may work for you, but it does not work for me, in spite of restarting.

$ nordvpn login
Whoops! Cannot reach System Daemon.

archnix commented on 2019-12-04 08:22

@Klodep @doctorcolossus

Nordvpn works without issues. At least if your remember that network depends on kernel - so if you updated kernel - restart. If you update nordvpn - stop the daemon - update - start daemon.

Previous versions of Nordvpn did change rapidly between nordvpnd - nordvpnud and nordvpnsd services. The nordvpnsd service is a leftover.

If your resolver is cluttered - it is probably the installed gui. If you use nordvpn as it is supposed to - on CLI - there is no problems.

Nordvpn - using TCP or UDP is problematic if you are using UFW iptables based firewall - ditch it and use firewalld instead.

On Manjaro forum is guide to troubleshooting nordvpn including complete removal. https://forum.manjaro.org/t/howto-nordvpn-usage-installation-updating-and-troubleshooting/71268

Klodep commented on 2019-12-03 02:29

I have resolved the problem. I just add this line in /etc/resolv.conf [code]nameserver 103.96.99.99[/code] and all is now working correctly whith my Wifi It is the server that nordvpn use to resolve DNS (I think) But, however, i don't know if i will re-install nodrvpn-bin.

For more information see this post on the Arch-forum

https://bbs.archlinux.org/viewtopic.php?id=250491

Klodep

doctorcolossus commented on 2019-12-02 17:54

@archnix: Thanks, but I have already tried restarting many times. Every time I still get "Whoops! Cannot reach System Daemon." Any other ideas?