Package Details: nordvpn-bin 3.20.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: GPL3
Conflicts: openvpn-nordvpn
Provides: nordvpn
Submitter: metiis
Maintainer: Mxzcabel
Last Packager: Mxzcabel
Votes: 171
Popularity: 1.61
First Submitted: 2018-08-29 12:13 (UTC)
Last Updated: 2025-03-21 04:02 (UTC)

Pinned Comments

Mxzcabel commented on 2023-03-23 20:37 (UTC) (edited on 2024-11-21 01:57 (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.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 .. 6 7 8 9 10 11 12 13 14 15 16 .. 54 Next › Last »

Vincent_Hugot commented on 2022-10-04 15:43 (UTC)

@PainfulByte

My understanding is that the login URL is sometimes deliberately weird to get around censorship. Otherwise you couldn't login from countries where NordVPN's main domains are banned.

Personally I hate having to involve the browser, and use "nordvpn login --username X --password Y" instead. Unfortunately they said it might be deprecated at some point, if I recall.

I wouldn't panic about the URL being weird. Put it that way: if you are running a compromised nordvpn executable, you're already thoroughly boned, whether you click a URL or not :-)

PainfulByte commented on 2022-10-04 13:56 (UTC)

@Gamall, I'm using the manual connection using openvpn in the meantime... I can't bring myself to trust such a weird domain name.

Vincent_Hugot commented on 2022-10-04 13:47 (UTC)

@PainfulByte That's just the "new" way they handle login.

You can still use --username etc... until they remove it.

PainfulByte commented on 2022-10-04 13:45 (UTC) (edited on 2022-10-04 13:53 (UTC) by PainfulByte)

I'm getting a weird link when logging in.

➜  ~ nordvpn login
Continue in the browser: https://my1337jog.run/v1/users/oauth/

phdpe commented on 2022-09-26 19:58 (UTC)

why is this marked out of date? i see nordvpn server still showing same version number (3.14.2)

McQueen commented on 2022-08-31 04:11 (UTC)

@isryn yes -- that does work. thank you!

isryn commented on 2022-08-09 19:15 (UTC)

you can fix the "rotating:transport rotator: ptr timer is locked" output like this: 1. sudo systemctl stop nordvpnd.service 2. sudo mkdir /run/nordvpn/ 3. touch nordpvnd.sock 4. sudo systemctl start nordvpnd.service cheers

demiluxmed commented on 2022-08-09 16:33 (UTC)

Getting the same message as ygurin when I try to login

"rotating: transport rotator: ptr timer is locked"

ygurin commented on 2022-08-06 23:14 (UTC)

I seem to be getting this on login

nordvpn login

rotating: transport rotator: ptr timer is locked

Any idea what this could be?