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.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

Please disregard my question below, I fixed it another way. I'm now connecting to my dedicated NordVPN IP address through OpenVPN. I can do the same things I need as with the nordvpn client or cli, no issues speed-wise, it even seems to be 30-40% faster up and down. Maybe a today thing, can't verify that easily now. No DNS leaks afaict (https://www.dnsleaktest.com/results.html)and I can access the same functionality I used before.

=========================================================================

I rolled back to (pamac>aur) nordvpn 3.17.2-1 connected to nordlynx, no problems, fast and stable connection. Just tried to connect to udp (and tcp) to connect to my private ip address and bam, error connecting. Switching back to nordlynx, all is fine.

Steps taken from cli: nordvpn set technology openvpn nordvpn set protocol udp nordvpn connect nlxxxx (my server) nordvpn connect nl

result: Connecting to Netherlands nlxxxx The VPN connection has failed. Please check your internet connection and try connecting to the VPN again. If the issue persists, contact our customer support.

Then: nordvpn set technology nordlynx nordvpn connect nl

result: Connecting to Netherlands #881 (nl881.nordvpn.com) You are connected to Netherlands #881 (nl881.nordvpn.com)!

What am I missing? I'm far from a linux expert so I'm probably overlooking something. openvpn 2.6.9-1 and openvpn-update-resolv-conf-git are installed (pamac>aur).

hello everyone, I followed precisely the archlinux tutorial (https://wiki.archlinux.org/title/NordVPN#Setting_systemd-resolved_as_DNS_resolver) with wireguard-tools and systemd-resolvconf. Everything is ok except that if I start the VPN first Firefox is frozen (no startup) with nordlynx technology and openvpn.

On the other hand, if I open Firefox and then activate the VPN there is no longer a problem (closing FF, reopening...). This is beyond my skills.

If someone has an idea ? Thanks

EDIT 06/04/24 i stop and disable systemd-resolved.service, remove wireguard-tools and systemd-resolvconf and everything works fine again.

@mxzcabel, thank you for fixing this AND for the tip about systemctl restart systemd-resolved.service. I would not have thought of that.

If you setup your system using systemd-resolved then NordVPN will not leak dns.

https://wiki.archlinux.org/title/NordVPN#Setting_systemd-resolved_as_DNS_resolver

Instructions for downgrade to version 3.17.2:

wget https://aur.archlinux.org/cgit/aur.git/snapshot/aur-e4dbfacf758c41a3514702d25779ececc18f1bf9.tar.gz

unp aur-e4dbfacf758c.tar.gz

mv aur-e4dbfacf758c nordvpn-bin-3.17.2

cd nordvpn-bin-3.17.2

makepkg

sudo pacman -U nordvpn-bin-3.17.2-1-x86_64.pkg.tar.zst

as root edit /etc/pacman.conf and add "nordvpn-bin" to IgnorePkg, to avoid update to 3.17.3.

@FGD You're right, sorry for the sloppy typo. Was responding from my tablet, half asleep.

@Npa

@borw2024 i don't see it in Aur. Can you please give a link.

I think he's referring to the nordvpn non-bin package, which has "nordvpn client" as description.

https://aur.archlinux.org/packages/nordvpn

It's version 3.17.2, which explains why it works. He also probably did a typo by saying 3.17.12 and not 3.17.2.

It basically means dowgrading nordvpn-bin from 3.17.3 to 3.17.2. :)

@borw2024 i don't see it in Aur. Can you please give a link.

@Npa:using the package manager, it's in aur. It's also a cli tool btw, same commands as the nordvpn-bin package.