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

@FabioLolix so in other words, NordVPN open sourced the source code, but its only source available? because we cant actually build or use it from source...

While nordvpn can now be built from source https://github.com/NordSecurity/nordvpn-linux/issues/3#issuecomment-1478516721 it will very likely not work at the moment as it need tokens and a public salt value don't seem very useful

@a3dman well if you can find the source code, you are free to push a new package yourself?

@PolarianDev I agree, that would be better.

@a3dman if it is open source this package should remain -bin and a new package should be created without the -bin which installs and compiles from source.

This is because source installs take longer, thus users should have a choice between source installs and binary installs, the latter being safer as you can verify its not malicious.

I think it's open source now, so probably -bin should be removed if it's compiled directly from the source.

If the software is proprietary, and nordvpn does not exist, you can remove the -bin :)

Makes the package easier to install.

error: failed to commit transaction (conflicting files)  
nordvpn-bin: /var/lib/nordvpn/data/countries.dat exists in filesystem  
Errors occurred, no packages were upgraded.

@Neurognostic :

It worked for me, after a bit of --overwrite during install.

Have you installed "wireguard-tools"? This should be a dependency of this package, given that the connection can fail in various ways without it (I have experienced the connection dropping after a fixed amount of time, for instance; there are multiple discussions of this in the comments below.)

I don't know if that still applies to 3.16, but given that this new problem is wireguard-related, that would be the first thing to try imo.

@a3dman Something broke in 3.16.0 for nordlynx/wireguard protocol. 3.16.0 is working fine on a Pop!_OS system I have.

[Error] TELIO: telio_start_named: Err(AlreadyStarted)
[Warning] executing 'ip -4 rule del from all lookup main suppress_prefixlength 0' command: exit status 2: RTNETLINK answers: No such file or directory
[Warning] executing 'ip -4 rule del from all lookup main suppress_prefixlength 0' command: exit status 2: RTNETLINK answers: No such file or directory
[Warning] executing 'ip -4 rule del from all lookup main suppress_prefixlength 0' command: exit status 2: RTNETLINK answers: No such file or directory
[Error] opening the tunnel: starting libtelio on retry with boring-tun: 6
[Error] TELIO: libtelio-build/libtelio/crates/telio-wg/src/adapter/linux_native_wg.rs:102 LinuxNativeWg: [GET01] Unable to get interface from WireGuard. Make sure it exists and you have permissions to access it.
[Error] TELIO: [repeated 100 times!] libtelio-build/libtelio/crates/telio-wg/src/adapter/linux_native_wg.rs:102 LinuxNativeWg: [GET01] Unable to get interface from WireGuard. Make sure it exists and you have permissions to access it.

I worked on it for a while, didn't figure it out, and downgraded to 3.15.4.

Is nordlynx on 3.16.0 working for anyone?