Package Details: nordvpn-bin 3.17.4-1

Git Clone URL: https://aur.archlinux.org/nordvpn-bin.git (read-only, click to copy)
Package Base: nordvpn-bin
Description: NordVPN CLI tool for Linux
Upstream URL: https://nordvpn.com/download/linux/
Keywords: networking nordvpn openvpn security vpn
Licenses: GPL3
Conflicts: openvpn-nordvpn
Provides: nordvpn
Submitter: metiis
Maintainer: Mxzcabel
Last Packager: Mxzcabel
Votes: 161
Popularity: 0.97
First Submitted: 2018-08-29 12:13 (UTC)
Last Updated: 2024-04-05 12:55 (UTC)

Pinned Comments

Mxzcabel commented on 2023-03-23 20:37 (UTC) (edited on 2024-04-05 13:02 (UTC) by Mxzcabel)

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

martoko commented on 2020-12-20 09:10 (UTC) (edited on 2020-12-20 09:12 (UTC) by martoko)

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

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 53 Next › Last »

Npa commented on 2024-04-04 14:19 (UTC)

@borw2024 Hi how did you install NordVPN client for Linux 3.17.12.1 ? Thanks

borw2024 commented on 2024-04-04 13:04 (UTC)

FYI: nordvpn-bin 3.17.3-1 also gave me problems, not allowing any sort of connection anymore. I uninstalled it and installed the NordVPN client for Linux 3.17.12.1 instead which connects fine with the nordlynx protocol. Openvpn with UDP/TCP can connect at country level but does not work with permanent IP / named server.

HotblackDesiato commented on 2024-04-01 11:07 (UTC)

I updated the package today to version 3.17.3-1. I am getting this error:

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.

I just see the previous warning by Mxzcabel. After "systemctl restart systemd-resolved.service" I was able to connect.

I guess this is not a permanent fix. I suggest the package maintainer downgrades the package until this issue is solved.

jrichard326 commented on 2024-03-30 11:18 (UTC)

3.17.3-1 (amd64) is leaking DNS. It is showing the DNS provided by nord and my default DNS, OpenDNS. Downgraded to 3.17.2-1 and all is fine again.

leoneill commented on 2024-03-30 10:26 (UTC)

Same issue with 3.17.3-1. Had to downgrade to 3.17.2-1

CooperArchy commented on 2024-03-30 10:18 (UTC)

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

rk9 commented on 2024-03-30 09:27 (UTC)

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

Sidestepp commented on 2024-03-30 04:17 (UTC) (edited on 2024-03-30 06:57 (UTC) by Sidestepp)

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

tippfehlr commented on 2024-02-16 09:25 (UTC)

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

Rhinoceros commented on 2024-01-19 11:52 (UTC) (edited on 2024-01-23 08:22 (UTC) by Rhinoceros)

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.

« First ‹ Previous 1 2 3 4 5 6 7 .. 53 Next › Last »