Package Details: nordvpn-bin 3.20.2-4

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: GPL3
Conflicts: openvpn-nordvpn
Provides: nordvpn
Submitter: metiis
Maintainer: Mxzcabel
Last Packager: Mxzcabel
Votes: 172
Popularity: 0.71
First Submitted: 2018-08-29 12:13 (UTC)
Last Updated: 2025-05-09 18:47 (UTC)

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:

  • Simply uninstall nordvpn-bin and install again.

If you're coming from Manjaro or e.g another Arch-based distro with no stable libxml2-legacy package just yet:

  • No need to upgrade. It's best keeping with the 3.20.2-3 version. But if you already had, then you can downgrade.

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

    After restarting resolve with systemctl restart systemd-resolved.service you may get it working again, enough for connecting normally, as reported, but not exclusively an ARM platform issue, on #342.

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:

  • Logging in with a username and password is no longer available in the terminal.

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

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 57 Next › Last »

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).

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

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: us8585.nordvpn.com IP: 91.196.220.48 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?

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

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

a3dman commented on 2023-04-01 01:04 (UTC)

@PC2022 I use 'nordvpn login --legacy' to avoid the hassle.

PC2022 commented on 2023-04-01 00:59 (UTC)

Nordvpn Arch wiki says that since April 2022, nordvpn login now steers you to a web login.

It seems I have to log in via browser, then copy and paste the resulting nordvpn:// url into "nordvpn login --callback <url>"

I'm wondering how people are using this CLI? Is there something I'm missing, or is this as good as it gets?

Mxzcabel commented on 2023-03-24 14:37 (UTC) (edited on 2023-03-24 16:59 (UTC) by Mxzcabel)

Hi @esauvisky

I already check the wiki (even before my first submission), and there's nothing explaining about not being allowed to warning users to remove some file that conflicts with other versions before installing. Can you please explain why it's against AUR guidelines?

The reason I didn't place a removal for the package pre_install is because super user permissions are needed to make this since is on root territory. Despite pacman itself, I don't think would be wise to place a removal without a fully user consentment, even with me and all users being aware the file will be generated again and is a binary, it's still on file system directory and require sudo to workout.

If you guys think there's something wrong with this approach and there's a simple workaround, I'll be glad to checkout the feedbacks in my free time and update the package again.

Edit: Thanks for your support. I'm just trying to figure out these things with you. If it's fine the removal with sudo permissions on pacman and not a issue at all, should the file be renamed as old or be removed? What's the best way to deal with without been invasive as a AUR package?