Package Details: nordvpn-bin 3.10.0_1-1

Git Clone URL: (read-only, click to copy)
Package Base: nordvpn-bin
Description: NordVPN CLI tool for Linux
Upstream URL:
Keywords: networking nordvpn openvpn security vpn
Licenses: custom
Conflicts: openvpn-nordvpn
Provides: nordvpn
Submitter: metiis
Maintainer: metiis (Martoko, bubuntux)
Last Packager: Martoko
Votes: 112
Popularity: 4.11
First Submitted: 2018-08-29 12:13
Last Updated: 2021-05-31 11:01

Pinned Comments

Martoko commented on 2020-12-20 09:10

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:

Latest Comments

1 2 3 4 5 6 ... Next › Last »

Th30 commented on 2021-05-24 02:01

Hi, for those who have a disconnection problem and are forced to restart the daemon, you need to downgrade to version 3.9.2 or activate OpenVPN instead of Nordlynx. To do this you need to run the command nordvpn s technology OpenVPN and reconnect to a server.

@Martoko: as suggested by joehillen think about adding in the PKGBUILD the 644 permissions for the concerned files. Thank you.

joehillen commented on 2021-05-17 21:14

I'm constantly seeing these log messages. Please fix this:

May 17 14:09:25 t480 systemd[1]: Configuration file /usr/lib/systemd/system/nordvpnd.service is marked world-writable. Please remove world writability permission bits. Proceeding anyway.
May 17 14:09:25 t480 systemd[1]: Configuration file /usr/lib/systemd/system/nordvpnd.socket is marked world-writable. Please remove world writability permission bits. Proceeding anyway.

s1lv3r commented on 2021-05-16 22:38

@rezanmz marked this package as outdated with the reason "Outdated", but according to the release notes the latest version is 3.9.4, the same as the PKGBUILD is providing.

Additionally, the NordVPN deb pool lists 3.9.4 as the latest version.

What should be done in situations like these?

Arawindor commented on 2021-04-27 14:27

Hi to all, the subnet whitelist doesn't work with my Arch Linux Thinkpad T570: I've whitelisted both LAN and VPN subnet, but I can't ping LAN.
I've reinstalled twice, switched from OpenVPN to NordLynx technology, restarted several time systemd's nordvpnd service, but I can't ping local network while I'm connected to NordVPN.
Any advice?
Here's my nordvpn settings:
Technology: NordLynx
Firewall: enabled
Kill Switch: disabled
CyberSec: disabled
Notify: enabled
Auto-connect: disabled
DNS: disabled
Whitelisted subnets:

esdaniel commented on 2021-04-21 07:04

@arizonajoe iptables confs could be a red herring. As you say.. everything else works and then it slowly deteriorates, you've got a decent connection too which could mean traffic shaping via your ISP is taking place or perhaps even at Nordvpn. Might be best to send Nordvpn a DM on Twitter to help them diagnose given you've checked everything 'your side'. FYI I asked for their help once before and they were responsive, supportive and effective in helping me diagnose my issues.

arizonajoe commented on 2021-04-20 16:21

I have been having issues with nordvpn-bin for over a year. Within 10 - 15 minutes "on the clock," something happens to severely restrict though-put, whether I use NetworkManager in Plasma/KDE or Gnome. It matters not. Yes, I make sure that the service is started and enabled. Yes, this user is a member of the group. The connection always starts out to be excellent whether using NordLynx or OpenVPN, and whether Cybersec is on or off. And it makes no difference which server I connect to. Sometimes the connection deteriorates slowly, and at other times, it becomes "constricted" faster, and requires a reboot or iptables restart. I have not looked at the IP tables but assumed that nordvpn broke them. And the system tray icon in Plasma/KDE gets the requisite exclamation mark telling me my connectivity is limited.

This happens whether on WiFi or on Ethernet. I am using a fast fiber connection near 1000MB/sec. A restart of the iptables fixes the though-put temporarily, but the exclamation point warning of limited connectivity in the system tray connection icon remains.

sadiqu commented on 2021-04-19 17:35

@ledom05 When my connection randomly closes I usually do a pkill nordvpnd and then sudo systemctl restart iptables and everything goes running again.

5DcNu23aph commented on 2021-03-23 20:31

Still have an issue with "limited connectivity" in Plasma. About 5 minutes in after connecting NetworkManager would notify about "limited connectivity", e.g. no internet access. After that connectivity in some apps (Spotify for example) would be lost, but browser works normally.

Have tried various combinations of settings for the package, but no luck so far. Support agent didn't even try to help, since they have no official support for arch. Flushing iptables and changing permissions for resolv.conf didn't help either.

I have found no working solution for my problem so far.

sylgar commented on 2021-03-23 20:28

@Martoko: have you checked the dependencies of the 3.9.0 Debian package? They have changed from previous versions, so the dependencies of your package may need adjustments too.

LuciRose431 commented on 2021-03-23 11:49

There is mistake at line number 26

bsdtar -O -xf *.deb data.tar.xz | bsdtar -C "${pkgdir}" -xJf -

there should be data.tar.gz