Package Details: nordvpn-bin 3.19.2-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: 168
Popularity: 0.88
First Submitted: 2018-08-29 12:13 (UTC)
Last Updated: 2024-11-28 13:50 (UTC)

Pinned Comments

Mxzcabel commented on 2023-03-23 20:37 (UTC) (edited on 2024-11-21 01:57 (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.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.


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 .. 22 23 24 25 26 27 28 29 30 31 32 .. 54 Next › Last »

manjarouser23453 commented on 2020-12-18 08:57 (UTC)

@kamil: your advice works for me as well, I rebooted to get it to work. (Using Manjaro)

doctorcolossus commented on 2020-12-18 03:37 (UTC) (edited on 2020-12-18 03:42 (UTC) by doctorcolossus)

@Techi-Joe, @Th30: Are you guys by any chance using an HTTP proxy?

dapolinario commented on 2020-12-18 02:19 (UTC) (edited on 2020-12-18 02:19 (UTC) by dapolinario)

The file is missing to create the group dynamically, using systemd-sysusers.

https://www.freedesktop.org/software/systemd/man/systemd-sysusers.html

https://www.freedesktop.org/software/systemd/man/sysusers.d.html#

nallekarhu commented on 2020-12-17 23:58 (UTC)

@kamil: following your advice exactly worked for me. Thanks!

Techi-Joe commented on 2020-12-17 23:45 (UTC) (edited on 2020-12-17 23:50 (UTC) by Techi-Joe)

@kamil I tried that as well, no luck. sudo systemctl enable --now nordvpnd no longer produces an error, but when I rum nordvpn c I get the error message: Whoops! Cannot reach System Daemon

Edit: Tried 3.8.5, same issue.

Th30 commented on 2020-12-17 23:17 (UTC)

@kamil: I had already tried to add the group (without the -r option). So I deleted the group created and followed your procedure, without result. The error message Whoops! Cannot reach System Daemon.

<deleted-account> commented on 2020-12-17 22:48 (UTC)

The version 3.8.8 is working fine but you need to create the system group manually and add yourself to that group:

sudo groupadd -r nordvpn
yay -Syu nordvpn-bin
sudo systemctl enable --now nordvpnd.service
sudo gpasswd -a <username> nordvpn

Log out and in to finish group update process.

Techi-Joe commented on 2020-12-17 22:32 (UTC) (edited on 2020-12-17 22:35 (UTC) by Techi-Joe)

https://aur.archlinux.org/ipset-git.git is required to install, but it isn't included in the repositories despite being listed. I had to clone it manually into the nordvpn-bin folder before it would build.

Topocount commented on 2020-12-17 20:41 (UTC)

Because 3.8.8 doesn't seem to be working for many people, I want to bump syscall1001's suggestion to use 3.8.5 for now