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

Hi, i've the same issue of lknix, after nordvpn connet command.

@metiis how did you solve this after installing and logging in:

$ nordvpn connect
NordVPN needs access to these files to ensure Your privacy:
/etc/sysctl.conf
/etc/resolv.conf
Immutability and append-only flags need to be removed from the files above. You can achieve that by running `sudo chattr -ia /path/to/file` for each of them.
Would you like NordVPN to do it for you?[Y/N]

I already have those attributes disabled for both files. It seems nordvpn wants write access to /etc/sysctl.conf and /etc/resolv.conf. Changing file permissions to +rw did the trick. But then I hit:

$ nordvpn connect
It seems there's an issue with the config file ("/etc/nordvpn/nordvpn-config") permissions. If the issue persists, please contact our customer support.

$ ls /etc/nordvpn/nordvpn-config
ls: cannot access '/etc/nordvpn/nordvpn-config': No such file or directory

$ yay -Ql nordvpn-bin | grep config
$

How did you resolve this?