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

I have the same issue as @Sidestepp and @rk9 with the 3.17.3-1

Exactly same issue for me as @Sidestepp after the latest update.

"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." This is what I get since the latest update (Mar 29, 2024). I do have an internet connection.

I think it's not necessary to print the info in post_upgrade(), I would remove it.

Anyone having issues with this, perhaps after the most recent update? After a suspend-resume cycle, nordvpn status and nordtray claim I'm connected, but I'm actually not, from checking my public IP. I have to disconnect and reconnect, or restart the systemd job. Interestingly nordvpn c suggests it connects fine, but I actually need to manually nordvpn d then nordvpn c to actually get a connection up.

EDIT: 3.17.0-1 is indeed broken for me. Reverting to 3.16.9-1 automatically connects again.

Heyho, nordpvn c does not work at all anymore for me. (For quiet a while now) with nordvpn c de I get:

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

I obviously already did that.

systemctl status --now nordvpnd returns:

● nordvpnd.service - NordVPN Daemon Loaded: loaded (/usr/lib/systemd/system/nordvpnd.service; disabled; preset: disabled) Active: activating (auto-restart) (Result: exit-code) since Fri 2023-12-29 15:26:28 CET; 1s ago TriggeredBy: ● nordvpnd.socket Process: 805986 ExecStart=/usr/sbin/nordvpnd (code=exited, status=1/FAILURE) Main PID: 805986 (code=exited, status=1/FAILURE) CPU: 133ms

and journalctl -e -u nordvpnd.service returns:

Dec 29 15:32:01 tomT480s systemd[1]: Started NordVPN Daemon. Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 [Info] Daemon has started Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 Kill Switch set to: disabled Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 Firewall set to: enabled Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 Routing set to: enabled Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 Auto-connect set to: disabled Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 DNS set to: Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 ThreatProtectionLite set to: disabled Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 Protocol set to: UNKNOWN_PROTOCOL Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 Allowlist set to: {Subnets:[192.168.0.0/24 192.168.1.0/24] TCPPorts:[] UDPPorts:[]} Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 Meshnet set to: disabled Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 IPv6 set to: disabled Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 Technology set to: UNKNOWN_TECHNOLOGY Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 Obfuscate set to: enabled Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 Notify set to: enabled Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 [Info] HTTP CALL Duration: 173.040409ms Dec 29 15:32:02 tomT480s nordvpnd[3338]: Request: HTTP/1.1 GET https://downloads.nordcdn.com/configs/dns/cybersec.json map[Accept-Encoding:[gzip, deflate] Content-Length:[] Content-Type:[] User-Agent:[NordApp Linux 3.16.9 Linux 6.6.8-arch1-1]] Dec 29 15:32:02 tomT480s nordvpnd[3338]: Response: HTTP/1.1 200 - map[Age:[6134] Cache-Control:[public, max-age=1800] Cf-Cache-Status:[HIT] Cf-Ray:[83d2c004ff9239d6-FRA] Connection:[keep-alive] Content-Encoding:[gzip] Content-Type:[application/json] Date:[Fri, 29 Dec 2023 14:32:02 GMT] Expires:[Fri, 29 Dec 2023 15:02:02 GMT] Last-Modified:[Fri, 23 Jun 2017 07:26:04 GMT] Server:[cl> Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 error retrieving nameservers: cdn api: X-Accept-Before UNIX value is lower than current local time Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 [Info] http transports to use (environment): Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 [Info] http transports to use (after validation): [http1 http3] Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 [Warning] moose: init was successful Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 [Warning] setting moose technology: unknown technology Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 remote config version field: telio_config_3_16_5 Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 [Info] libtelio final config: {"lana":{"event_path":"/var/lib/nordvpn/data/moose.db","prod":true},"nurse":{"fingerprint":"6780781a6c7b50a6688b03a28aadcb1312d6b0c2b77fef7ad787d39e362f9612","qos":{}},"direct":{}} Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 [Info] TELIO(v4.0.9): "telio::device":345 Created libtelio instance v4.0.9, dev Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 [Info] TELIO(v4.0.9): "telio::device":347 libtelio is starting up with features : Features { wireguard: FeatureWireguard { persistent_keepalive: FeaturePersistentKeepalive { vpn: Some(25), direct: 5, proxying: Some(25), stun: Some(25) } }, nurse: Some(FeatureNurse { fingerprint: "6780781a6c7b50a6688b03a28aadcb1312d6b0c2b> Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 [Info] TELIO(v4.0.9): "telio_lana::moose_callbacks":21 [Moose] Init callback success: Ready Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 [Warning] TELIO(v4.0.9): "telio_lana::event_log":64 [Lana] couldn't find foreign context field device_info.brand Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 [Warning] TELIO(v4.0.9): "telio_lana::event_log":64 [Lana] couldn't find foreign context field device_info.location.city Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 [Warning] TELIO(v4.0.9): "telio_lana::event_log":64 [Lana] couldn't find foreign context field device_info.location.country Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 [Warning] TELIO(v4.0.9): "telio_lana::event_log":64 [Lana] couldn't find foreign context field device_info.location.region Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 [Warning] TELIO(v4.0.9): "telio_lana::event_log":64 [Lana] couldn't find foreign context field device_info.model Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 [Warning] TELIO(v4.0.9): "telio_lana::event_log":64 [Lana] couldn't find foreign context field device_info.resolution Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 [Warning] TELIO(v4.0.9): "telio_lana::event_log":64 [Lana] couldn't find foreign context field user_info.fp Dec 29 15:32:02 tomT480s nordvpnd[3338]: 2023/12/29 15:32:02 no such technology Dec 29 15:32:02 tomT480s systemd[1]: nordvpnd.service: Main process exited, code=exited, status=1/FAILURE Dec 29 15:32:02 tomT480s systemd[1]: nordvpnd.service: Failed with result 'exit-code'. I'm not sure what the problem is... It seems as if it's a problem with my current local time, but I did ntpd -qg and hwclock -w and date returns the right current time. some ideas?

@ Mxzcabel : I'm sorry i flagged the package out of date because i did not read your pinned comment... You are right. Thanks you.

@notjas You can just use a token and read the changelog first instead of blindly complain about developers decisions.

TONS of trash messages "http/3.0 200 cache control" in system journal when using higher than 3.15.5-1
What the hell was the point "improving" username/password login not allowed from terminal, this isn't crapOS 🙄
..decreased functionality in the name of trying to look all proper forcing a login thru the browser.
I guess they think it makes their product look "cool". Some legit idjits over at nordvpn🖕

Annoying as hell to say the least