Package Details: nordvpn-bin 3.6.0_3-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: 61
Popularity: 5.10
First Submitted: 2018-08-29 12:13
Last Updated: 2020-01-16 15:01

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 »

blind_gh0st commented on 2020-01-24 01:09

@ludaval - This package is not out of date. 3.6.0-3 is the most recent version in the nordvpn debian repo. I am also not seeing the error having just installed.

archieslove commented on 2020-01-20 23:44

Is anybody facing random disconnections on an eduroam connection when auto connect is enabled in the settings ? Turning off auto connect completely eliminates the frequent disconnection. Anybody ?

*It behaves the same after the fresh install.

bhargu commented on 2020-01-18 06:13

Edit: I found the reason for this issue while running strace on nordvpn client. I had a local proxy server configured on my Arch system using /etc/environment. The trace showed that the client was accessing this proxy server for even the 'login' command. I removed these variables from my environment file, restarted the OS and the client started working.

Hi, I tried the nordvpn-bin and I am getting the error message "Whoops! Cannot reach System Daemon.". I tried building different versions of the AUR package, but none of it works. I did a clean install, restarted, etc. Also, yes, I did start the systemd service. I tried the Linux CLI tool with Ubuntu and it worked without any issues.

Does anyone know what this is really about? I have my nordvpn service running and socket listening.

SurlyCycler commented on 2020-01-17 16:44

Hi metils. I have noticed some hickups with the last 2 updates. The previous update openvpn stopped working and wireguard did. However, with this update nordlynx (wireguard) has stopped working and openvpn does.

Note: that there was an update with the kernel linux and linux-lts and wireguard-arch and wireguard-lts. The problem could be there.

I am curious if you might know why? thanks

UPDATE: it works now. I just had to reinstall and remove the ./config/nordvpn file.

Ubermensch commented on 2020-01-14 12:07

I still have problems with iptables and killswitch even with the latest version. To fix i disbled killswitch.

j.taala commented on 2020-01-14 11:55

Hey metiis, let me know if you could use another co-maintainer. Updated PKGBUILD to 3.6.0_2 and updpkgsums. Updated on my local machine, tested, and new ver works well. Happy to help keep this AUR pkg up to date if you could use a hand.

Cheers, Jay.

Zombie commented on 2020-01-01 11:22

@doctorcolossus my problem was that ther was no sysctl script for the binary.

So I downloaded the *.deb file extractet in a folder with

  1. ar xv nordvpn_3.5.0-2_amd64.deb

now there should be a file named data.tar.xz that you have to extract with

  1. tar -xvf data.tar.xz

the next step is got to the /etc/init.d folder of the extracted file and copy the file named nordvpn to your /etc/system.d/system folder

  1. cd /etc/init.d
  2. sudo cp nordvpn /etc/system.d/system/nordvpn.service
  3. systemctl enable nordvpn.service
  4. systemctl start nordvpn.service

Now should be able to login with nordvpn login.

drpossum commented on 2019-12-27 13:27

Had the same problem as wassup but only on one machine. The difference is the killswitch setting. Enabling killswitch destroys existing iptables and sets the policies to DROP and only allows DNS traffic and traffic to their CDN. This squashes my other iptables settings (seriously, NordVPN?!) making killswitch not viable anymore.

Third option that worked for me other than manually setting the policy to ACCEPT or downgrading is disabling killswitch

emulti commented on 2019-12-26 18:29

I noticed that after loss/re-establish of network connection (or suspend/resume cycle) the DNS settings were NOT restored by nordvpnd, leading to a DNS leak to whatever DNS servers are configured/used in non-VPN state. I investigated, and found:

nordvpn set technology openvpn

If openresolv is being used on the machine, then DNS settings are NOT restored on auto-reconnect. It is necessary to do 'nordvpn disconnect' and 'nordvpn connect' again to restore them.

If systemd-resolved is enabled (see https://wiki.archlinux.org/index.php/Systemd-resolved) and configured to use the stub resolver (ln -s /run/systemd/resolve/stub-resolv.conf) then DNS settings are correctly restored. nordvpnd is aware of the network connection status and performs an automatic reconnect.

The reason for the above behaviour I guess is because the .deb file used is designed for/tested on Ubuntu, which uses systemd-resolved by default.

nordvpn set technology nordlynx

If the nordlynx/wiregard technology is used the DNS settings are NOT restored after suspend/resume or network disconnect/reconnect. In nordlynx mode, nordvpnd seems not aware of network status and does not perform a reconnect. This applies both on Arch and an Ubuntu VM I used for testing.

In short if using nordvpn-bin, best use openvpn and systemd-resolved, otherwise if you forget to manually disconnect/reconnect nordvpn (for example after a suspend/resume) all DNS queries will be leaked outside the tunnel.

wassup commented on 2019-12-26 16:53

The newest update (3.5.0-2) seems to mess up the iptables rules once the nordvpnd.service is enabled via systemctl. The default behaviour is changed to -P INPUT DROP and -P OUTPUT DROP, thus dropping all the IPv4 in and out traffic. Only IPv6 works as it should in this scenario.

There are two solutions to this problem:

1. Either automatically or manually execute the following:
# iptables -P INPUT ACCEPT
# iptables -P OUTPUT ACCEPT
2. Or, downgrade the nordvpn-bin package to version 3.4.0_1-1.