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

@manja2 I have the exact same issue as you and it still doesn't work, I wonder what they broke on their end.

@doctorcolossus hi and yes, one of the things I forgot to mention yesterday is 'we' deleted some conf files too... anyhow it's currently working for me with the following:

Technology: NordLynx Firewall: enabled Kill Switch: disabled CyberSec: disabled Notify: enabled Auto-connect: enabled IPv6: enabled DNS: 127.0.0.1 < Unbound DoH resolver :-)

@esdaniel: I also contacted Nord support and went through some of the same steps (deleting settings data, temporarily disabling ipv6, etc.). What finally worked was the guy asked me to downgrade to 3.8.4. Then on trying to connect it blocked my internet connection and hung for about a full minute, but eventually finally connected. Later I decided to upgrade back to 3.10 and... it also worked. Very strange. I am thinking it may be / have been (?) a temporary server-side issue.

Did you get yours working again?

After normal use for a few months, today nordvpn-bin gave me issues: - nordvpn c prompts me to enter my login credentials. Upon entering, it says It's not you, it's us. We're having trouble reaching our servers. If the issue persists, please contact our customer support. - But killswitch was on before the issue, so now I also can't reach the internet without nordvpn. And if I do nordvpn set killswitch off, I get You are not logged in. - Restarting the daemon gave the same results. - The only solution so I can reach the internet NOW, was to uninstall nordvpn. - I later installed an old version which worked, 3.7.4.

Update for everyone: spent an hour with nordvpn support, they don't know what's broken after checking plenty > from disabling ipv6, using their DNS servers, deleting their settings data, switching from Lynx to OpenVPN, then switching from UDP to TCP. Nothing worked!! So don't waste time checking and re-configuring. Hopefully I can update us later today when I get some feedback from this morning's checks/attempts.

@doctorcolossus Yep, hit me this morning. I logged out and back in again, which was reassuring that was working, then got the same error message: "Your account has expired. Renew..." etc.. Like you, my account is in good standing. Going to DM NordVPN now on Twitter to see if they know more.

After about a year of working properly, today nordvpn connect started giving me this on both of my arch linux laptops:

$ nordvpn connect
Opening the web browser...
If nothing happens, please visit https://join.nordvpn.com/order/?utm_medium=app&utm_source=linux
Your account has expired. Renew your subscription now to continue enjoying the ultimate privacy and security with NordVPN.

My subscription will not expire for a long time. In Windows, the NordVPN client connects to the same account with no problem.

Anybody else suddenly getting this? Any ideas? Thanks.

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.