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

After installing this version, I ran "nordvpn login" and got the following output:

A new version of NordVPN is available! Please update the application. Continue in the browser: https://mad4todo.com/v1/users/oauth/login-redirect?attempt=6db0c314-7700-47dd-a262-7ea517014fd3

This URL clearly does not belong to Nord - is something wrong with this package?

Either 'libtelio' errors or issues with nordlynx technology not detecting a network interface are being experienced despite the presence of functional interfaces. Mysteriously, "libtelio" errors in daemonlog.txt have disappeared, and today interface errors. Invoking daemonlog.text,

$ sudo journalctl -u nordvpnd > /home/"user"/Desktop/daemonlog.txt

These issues are specifically with NordLynx; openvpn technology has not been problematic (although now - 04/29/2023 - it is also now rejecting a udp protocol).

https://bbs.archlinux.org/viewtopic.php?id=285071

I re-duplicated these errors on a newly configured archlinux box home video server today,and have two different ISPs. This problem is not ISP related or related to a specific or idiosyncratic arch installation.

Nord has referred us to the AUR community. Any assistance or criticisms would be appreciated.

Note:(04-29-23) Nordlynx "functional" now after update; protocol tcp(?) only. This makes no sense to me since Wireguard's code relies upon udp (user datagram protocol), not tcp. So is this a novel development? There are at least two projects that explore tcp tunneling in Wireguard. Tcp is traditionally less than ideal for larger packets. Example of this Nordlynx tcp connection:

$ nordvpn status Status: Connected Hostname: us8585.nordvpn.com IP: 91.196.220.48 Country: United States City: Los Angeles Current technology: NORDLYNX Current protocol: TCP Transfer: 8.66 KiB received, 15.21 KiB sent Uptime: 17 seconds

Using Wireshark, I did in fact verify that Nordlynx is now using tcp.

Shouldn't the license be changed to GPL3 now that the NordVPN Linux client is open-source?

My steps:

1. run nordvpn login
2. copy URL
3. process steps on NordVPN's website
4. copy URL fron "continue"
5. run nordvpn login --callback URL

do not forget escape &s in URL

@PC2022 As in many web applications Nordvpn offer the option to log in with a token for us who use CLI, that is provided in page's account and work with 2FA. I wouldn't recommend to use legacy since you can revoke the token if needed and no risk to change or save the password directly on desktop.

@gary9872 - thanks for the tips. This would allow me to use 2fa and I may do this future (for long running vpn connections)

In my case though, Im just trying to automate it via bash scripts, so I can spin up very short lived vpn sessions for dev/testing. Id like to avoid manually copying links from browser into terminal

@PC2022 I didn't know there was a legacy option till today after I already managed to do the web thing for a headless machine.

You can login into a headless device, copy the link provided, run in on another machine that has web browser, (with fully enabled javascript) then copy and paste the resulting nordvpn:// url into "nordvpn login --callback <url>" on the headless machine.

* make sure to whitelist your other non headless machine before testing a connection

@a3dman - thankyou! Had to disable 2fa, but I can live with that for now

@PC2022 I use 'nordvpn login --legacy' to avoid the hassle.