Package Details: nordvpn-bin 3.16.3-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: GPL3
Conflicts: openvpn-nordvpn
Provides: nordvpn
Submitter: metiis
Maintainer: Mxzcabel
Last Packager: Mxzcabel
Votes: 150
Popularity: 3.39
First Submitted: 2018-08-29 12:13 (UTC)
Last Updated: 2023-06-05 16:17 (UTC)

Pinned Comments

Mxzcabel commented on 2023-03-23 20:37 (UTC) (edited on 2023-04-26 17:40 (UTC) by Mxzcabel)

If you want to see the change between newer versions just check the Github page.

Note from 3.16.0 Version:

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:

Latest Comments

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

seds commented on 2023-05-24 12:36 (UTC)

@zencefil, not with the package, this looks like some weird stuff from NordVPN itself

zencefil commented on 2023-05-24 12:31 (UTC)

After installing this version, I ran "nordvpn login" and got the following output:

A new version of NordVPN is available! Please update the application. Continue in the browser:

This URL clearly does not belong to Nord - is something wrong with this package?

arizonajoe commented on 2023-04-20 19:22 (UTC) (edited on 2023-05-02 01:16 (UTC) by arizonajoe)

Either 'libtelio' errors or issues with nordlynx technology not detecting a network interface are being experienced despite the presence of functional interfaces. Mysteriously, "libtelio" errors in daemonlog.txt have disappeared, and today interface errors. Invoking daemonlog.text,

$ sudo journalctl -u nordvpnd > /home/"user"/Desktop/daemonlog.txt

These issues are specifically with NordLynx; openvpn technology has not been problematic (although now - 04/29/2023 - it is also now rejecting a udp protocol).

I re-duplicated these errors on a newly configured archlinux box home video server today,and have two different ISPs. This problem is not ISP related or related to a specific or idiosyncratic arch installation.

Nord has referred us to the AUR community. Any assistance or criticisms would be appreciated.

Note:(04-29-23) Nordlynx "functional" now after update; protocol tcp(?) only. This makes no sense to me since Wireguard's code relies upon udp (user datagram protocol), not tcp. So is this a novel development? There are at least two projects that explore tcp tunneling in Wireguard. Tcp is traditionally less than ideal for larger packets. Example of this Nordlynx tcp connection:

$ nordvpn status Status: Connected Hostname: IP: Country: United States City: Los Angeles Current technology: NORDLYNX Current protocol: TCP Transfer: 8.66 KiB received, 15.21 KiB sent Uptime: 17 seconds

Using Wireshark, I did in fact verify that Nordlynx is now using tcp.

begin-theadventu commented on 2023-04-07 05:39 (UTC)

Shouldn't the license be changed to GPL3 now that the NordVPN Linux client is open-source?

radio_rogal commented on 2023-04-03 13:37 (UTC) (edited on 2023-04-03 13:38 (UTC) by radio_rogal)

My steps:

  1. run nordvpn login
  2. copy URL
  3. process steps on NordVPN's website
  4. copy URL fron "continue"
  5. run nordvpn login --callback URL

do not forget escape &s in URL

Mxzcabel commented on 2023-04-03 03:06 (UTC) (edited on 2023-04-04 17:55 (UTC) by Mxzcabel)

@PC2022 As in many web applications Nordvpn offer the option to log in with a token for us who use CLI, that is provided in page's account and work with 2FA. I wouldn't recommend to use legacy since you can revoke the token if needed and no risk to change or save the password directly on desktop.

PC2022 commented on 2023-04-02 21:30 (UTC)

@gary9872 - thanks for the tips. This would allow me to use 2fa and I may do this future (for long running vpn connections)

In my case though, Im just trying to automate it via bash scripts, so I can spin up very short lived vpn sessions for dev/testing. Id like to avoid manually copying links from browser into terminal

gary9872 commented on 2023-04-02 21:10 (UTC)

@PC2022 I didn't know there was a legacy option till today after I already managed to do the web thing for a headless machine.

You can login into a headless device, copy the link provided, run in on another machine that has web browser, (with fully enabled javascript) then copy and paste the resulting nordvpn:// url into "nordvpn login --callback <url>" on the headless machine.

* make sure to whitelist your other non headless machine before testing a connection

PC2022 commented on 2023-04-01 01:11 (UTC)

@a3dman - thankyou! Had to disable 2fa, but I can live with that for now