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

Sorry, everyone. NordVPN team reminded me to use whitelist command ($ nordvpn whitelist add subnet <my_subnet/mask>) so issue resolved :-)

Just a heads-up to users... sometime in last couple of days something 'changed'. Before then, no issue pinging RFC1918 (local) addresses then today no joy when VPN 'connected'. Disconnect VPN and can ping, thus it's a firewall issue with how NordVPN interprets existing rules and overlays their own binding to the VPN host IP and dropping 'everything' else based on my tests today. Workaround is f'ing tedious till I script it... first, before connecting to VPN, do an iptables-save of the good conf. After connecting to NordVPN, check the NordVPN IP given that is in the updated firewall rules (take note of those new rules), then restore old fire rules and add the NordVPN rules thereafter thus ensuring LAN Allow is before local nic DROP statement etc. etc..

The package is out of date and no longer works for me. If you have time, please update this to the newest version (3.8.1 https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/) which fixed my issue

@MXI i use nordvpn on 2 laptops but the most recent has the same problem, i managed to get it to work by deleting the config file, but it only works once!

Hi,

Thank you for the work, been using it for quite a few months now, with no issue till yesterday.

I am however encountering the following issue since I updated last: whenever I try to use "nordvpn c", or "nordvpn [option]", I have the following message in red:"It seems there's an issue with the config file. If the issue persists, please contact our customer support."

Is anyone else encountering this or having any suggestion to address?

@Fifis Thanks, it works. And having that as an alias is kind of a temporary fix for this, but i guess i shouldn't have to do that.

@eesau I am using NetworkManager, so sudo systemctl restart NetworkManager did the job. I have an official reply from the support: Most likely a DNS issue. After you connect to our servers, your local DNS is being overwritten with our DNS to ensure a secure connection to the server. After disconnecting, the DNS is removed so this might be the issue if restarting network manager helps.

Thanks for the app.

Small problem though, I have to reboot to get the connection back after using vpn. Killswitch is off.

Any solution, apart from manually correcting iptables every time?

Seems that nordvpn-bin3.7.4 has resolved the issue i was encountering about connection being impossible ...