Arch Linux User Repository

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

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

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

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

I'm getting a weird link when logging in.

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

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

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

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

Getting the same message as ygurin when I try to login

"rotating: transport rotator: ptr timer is locked"

I seem to be getting this on login

nordvpn login

rotating: transport rotator: ptr timer is locked

Any idea what this could be?

Any idea how to use meshnet according to https://support.nordvpn.com/General-info/Features/1872910282/How-to-use-Meshnet-on-Linux.htm?

$ nordvpn set meshnet on                                                                                                                                                                                           
Command 'meshnet' doesn't exist.

Having issues with this last update. In order to connect to any specific server using

"nordvpn c Seattle" (or any general or specific server locale, for that matter)

Connecting to United States #8952 (us8952.nordvpn.com) Whoops! We couldn't connect you to 'Seattle'. Please try again. If the problem persists, contact our customer support.

But when I explicitly specify the Nord-preferred DNS server addresses using

"nordvpn set dns 103.86.96.100 103.86.99.100"

resulting in a proven settings change to this:

$ nordvpn settings Technology: NORDLYNX Firewall: enabled Kill Switch: disabled Threat Protection Lite: disabled Notify: disabled Auto-connect: disabled IPv6: disabled DNS: 103.86.96.100, 103.86.99.100

the problem vanishes and a successful connection is almost immediate. Whether using Nordlynx or OpenVPN technology, or UDP or TCP protocol, I must explicitly set the DNS addresses or I get no connection. I looked over the PKGBUILD and install files but see nothing that could explain this. Also, I am logged in, the daemon is enabled and I am a member of the nordvpn group. I do allow Networkmanager to control the writing of resolv.conf. Thoughts? I've reached out to tech support. Situation persists after I flush IP tables. UPDATE, UNRESOLVED: Nord tech support simply recommends adding Cloudflare nameservers 1.1.1.1 and 1.0.0.1 to resolv.conf and making that file immutible: chattr +i /etc/resolv.conf The need for explicit DNS servers in nordvpn-bin was nevertheless unchanged.

UPDATE: The nordvpn-bin update seems to have resolved the above issue.