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

Dependency included as mandatory earlier as community request.

If you're late for the party and only had updated up to 3.20.2-2.1:

• Simply uninstall nordvpn-bin and install again.

If you're coming from Manjaro or e.g another Arch-based distro with no stable libxml2-legacy package just yet:

• No need to upgrade. It's best keeping with the 3.20.2-3 version. But if you already had, then you can downgrade.

Note from 3.20.2-3

There is now a new package from official repositories named libxml2-legacy and with it two fresh considerations:

• Despite the fact libxml2-legacy was included as optional, it is actually a mandatory dependency. This will change on next NordVPN's release if the legacy support remains.

• This release only removes the previous symbolic link and purges the file within NordVPN library directory, otherwise it would result in an error before installation/upgrade.

Note from 3.20.2-2.1

A patch have been implemented due the absence of libxml2.so.2 after package upgrade to 2.14.2. This fix is not useful if:

• You plan to keep your system update to a specific date until NordVPN officially uses the new library.

• You are from a different distribution, which is a Arch-based one with other repositories, and libxml2 is not yet upgraded.

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

For some reason Manjaro can't see and install the aforementioned dependency: pacman -S libxml2-legacy error: target not found: libxml2-legacy Trying to install nordvpn-bin from the AUR fails: yay -S nordvpn-bin -> No AUR package found for libxml2-legacy -> could not find all required packages: libxml2-legacy

ok I sudo pacman -U --overwrite '*' libxml2-legacy-2.13.8-1-x86_64.pkg.tar.zst

and was able to update nordvpn-bin

MANJARO. My updates usually works well.

Am trying to upgrade from 3.20.2.3 to 3.20.2.4 ( AUR nordvpn-bin) I get could not satisfy dependencies: - unable to satisfy dependency 'libxml2-legacy' required by nordvpn-bin

@kensmith there's a reason of why I included as optional and it is because of the previous patch I committed. The third release needs to first unlink the symbolic link and purges the temporary fix file.

No, it is not possible to install libxml2-legacy first and include as mandatory, because it won't install the package with a previous file or symbolic link in library's folder.

To make things easier for the unaware folks, better installing the dependency as last step rather have to unlink with root privileges, not to mention here would be flooded with users not knowing what to do and why it happened in the first place, doing that way it's far more disturbing for the user.

And honestly, I also have added a note in pacman installation/upgrade to notify the change. You can't just install packages and do not read what pacman has to say.

I hope you understand now.

Would it be possible to add libxml2-legacy to depends rather than optdepends? I didn't have it installed and nordvpnd was failing to start due to the missing shared library.

nordvpnd[2693502]: /usr/sbin/nordvpnd: error while loading shared libraries: libxml2.so.2: cannot open shared object file: No such file or directory

Manually installing libxml2-legacy fixed it. I acknowledge that the pinned note mentions this but it seems like it would be better just to add it as a mandatory dependency for the current release rather than waiting until the next one.

Sad to say that the last fully working version w/o any issues is 3.17.2. I stoppped updating it after the downgrade to that version and I think that was a good decision...

Latest updates broke nordvpn. Update: I can confirm installing libxml2-legacy fixes the issue. Thank you @archvh Here is the log:

May 07 19:26:45 rog-strix nordvpnd[5172]: /usr/sbin/nordvpnd: error while loading shared libraries: libxml2.so.2: cannot open shared object file: No such file or directory May 07 19:26:45 rog-strix systemd[1]: nordvpnd.service: Main process exited, code=exited, status=127/n/a May 07 19:26:45 rog-strix systemd[1]: nordvpnd.service: Failed with result 'exit-code'. May 07 19:26:50 rog-strix systemd[1]: nordvpnd.service: Scheduled restart job, restart counter is at 1. May 07 19:26:50 rog-strix systemd[1]: Stopped NordVPN Daemon. May 07 19:26:50 rog-strix systemd[1]: Started NordVPN Daemon.

@archvh I had already installed libxml2-legacy. After a reinstall, it worked. Thank you very much.

@DarthRidar:

Please read the pinned comment regarding libxml2-legacy. You probably need to install that.

After updating to 3.20.2-3 nothing works for me anymore.

$ nordvpn login /run/nordvpn/nordvpnd.sock not found. The NordVPN background service isn't running. Execute the "systemctl enable --now nordvpnd" command with root privileges to start the background service. If you're using NordVPN in an environment without systemd (a container, for example), use the "/etc/init.d/nordvpn start" command.