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

@Techi-Joe

Have you tried connecting to other servers, changing to another protocol, deleting config folder and logging in again, reinstalling, etc ?

getting this error currently: nordvpn c transport is closing

I also confirm that, wireguard-tools fix the disconnect issues. It also fixed "nordvpn set autoconnect" in my case.

I'd like to also confirm that since installing wireguard-tools and rebooting I have not had any disconnecting issues. I am currently on 10 hours of uptime, where prior to installing wireguard-tools I would have to restart every ~2 hours to fix NordVPN.

As a further datapoint, installing wireguard-tools on kubuntu also fixed the ~2h10m (previously ~4h20) issue (connected 5h41 and going). I did nothing other than installing the package and rebooting. This issue is not specific to Arch, nor, it appears, is its solution.

@rabcor: Thanks a lot for your information. Using wireguard-tools fixes the issue with NordLynx for me. No disconnection and service drop after more than 4 hours of usage. Before, with version 3.12, nordvpn only worked for 2 hours before service dropped.

I add fallback DNS to resolved.conf. Not sure how it's gonna work out since I need nordvpn to break first :))

//I'm using systemd-networkd and systemd-resolved.

It seems after installing wireguard-tools the VPN connection is recognized by NetworkManager Also as mentioned by @jrichard326 removing .config/nordvpn config folder and reinstalling solved the issue that although nordvpn connect was possible, the connection seemed broken (not able to connect/ping to any server).

However, I did not explicitly test whether the connection problems were solved by installing wireguard-tools or by removing the config folder.

EDIT: After going to suspend the nordvpn again was not able to send any requests/pings to any server. The solution was to delete .config/nordvpn/ and nordvpn connect

For everyone who has been having issues with nordvpn disconnecting every X hours ( @Libly_Fait @equalis3r )

I had the same issue for a while now where every 4 hours and 20 minutes I would be disconnected and have to restart nordvpn to be able to connect again, after the latest update (3.12.1) it changed and started doing it every 2 hours and 10 minutes instead.

The issue was solved for me by installing the wireguard-tools package. At least it appears perfectly solved (I've had no issue with the connection for 12 hours)

I think maybe if more users confirm it solving their issue it should be added as an optional dependency for this package (for people who want to use nordlynx)

Also, for the DNS issue, you can resolve it by configuring your system to use systemd-resolved to manage your DNS. There's a guide for doing it here (although for manjaro): https://forum.manjaro.org/t/root-tip-nordvpn-on-manjaro/81016

Thank you very much @GoldenDreamcast and @langtudeplao. Downgraded to nordvpn-bin 3.10.0_1-1 and everything works as it should. Just had to delete old config file and login again. Thanks again

@Mundamugus: You can use git log and then git checkout to the suitable commit. git checkout e01bd1fc828c Then cd to the dir and makepkg -si