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

does not work for me at all .. removed everything and reinstalled but still the same error

Whoops! Connection failed. Please try again. If the problem persists, contact our customer support.

@typicallinuxuser I have noticed exactly the same ufw problem on Manjaro Linux - so it is not just you. Don't know what to do about it though except restart ufw every time I connect to a nordvpn server.

I'm now noticing anytime I connect with nordvpn c my ufw becomes inactive and will not enable on startup. I can activate it manually and all is well, and will remain active if I nordvpn d but then becomes inactive again any time I connect with nordvpn c.

Using nordvpn-bin version 3.2.0-4

@typicallinuxuser no such file or directory

chattr -i /var/lib/nordvpn/data/.config.ovpn

@ajgraves thank you. chattr -i /var/lib/nordvpn/data/.config.ovpn fixed my issue without having to reinstall the snapshot. Works as intended, version 3.2.0-4.

the version has changed now its 1.0 again ..

https://repo.nordvpn.com/deb/nordvpn/debian/pool/main/nordvpn-release_1.0.0_all.deb

after removing /var/lib/nordvpn , it still does not work

@typicallinuxuser the reason you can’t delete even as root is because there is a file in that directory with the immutable bit set. I can’t recall off the top of my head which but if you’ve already attempted to delete the folder it should be the only file left inside that folder. You can verify it is set by using the lsattr command. To remove the bit, as root run chattr -i followed by the name of the file. You’ll then be able to completely delete the directory.

I have also been getting the error message: Whoops! Connection failed. Please try again. If the problem persists, contact our customer support.

Running systemctl status nordvpnd there seems to be a restriction accessing the following path:

Jul 19 07:35:56 primary systemd[1]: Started NordVPN Daemon.

Jul 19 07:37:12 primary nordvpnd[530]: 2019/07/19 07:37:12 open /var/lib/nordvpn/data/.config.ovpn: operation not permitted

Each time I try to connect with nordvpn c another error is appended to systemctl status.

I tried to completely uninstall and remove all system files like ajgraves recommended for a different issue and I could not delete, even when logged in as su, /var/lib/nordvpn .

Version: 3.2.0-4

started getting an error

"Whoops! Connection failed. Please try again. If the problem persists, contact our customer support."

reinstalled but still giving an error.