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.90
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 .. 12 13 14 15 16 17 18 19 20 21 22 .. 54 Next › Last »

Mundamugus commented on 2021-11-22 07:20 (UTC)

@GoldenDreamcast | sorry I'm a real noob but I cloned the repo using
"git clone https://aur.archlinux.org/nordvpn-bin.git" then "git checkout" returned Your branch is up to date with 'origin/master'.

Any other help would be appreciated

GoldenDreamcast commented on 2021-11-22 06:04 (UTC)

@Mundamugus If you clone the repo, you can use git checkout to go back to the previous commit, which was the previous version in this case.

Mundamugus commented on 2021-11-22 02:54 (UTC) (edited on 2021-11-22 02:59 (UTC) by Mundamugus)

Version 3.12.1_1-1 not connecting at all here. After typing norvpn connect command cursor just spins until I kill the process. I tried the solution @jrichard326 posted but it didn't work for me. Can someone tell me how to downgrade the package please. Previous version worked fine.

equalis3r commented on 2021-11-21 13:44 (UTC)

@Libly_Fait: I experience the same issue. Every after 2 hours, VPN connection drops and the DNS (systemd-resolved) is gone. I have to manually kill and restart nordvpn. Apparently, the restart only works when using OpenVPN, not when using NordLynx.

Libly_Fait commented on 2021-11-20 22:44 (UTC)

Latest version randomly disconnects from the VPN, especially after logout. Also, as previous versions it changes to nordvpn DNS, which are not replaced after disconnecting leading to unusable connection. To solve that I have to sudo pkill nordvpn and sudo systemctl restart iptables.

allexj commented on 2021-11-18 19:55 (UTC)

If you don't have connection after that you have disconnected from VPN, you may disable killswitch feature, it appears buggy.

jrichard326 commented on 2021-11-06 23:27 (UTC) (edited on 2021-11-06 23:29 (UTC) by jrichard326)

I got 3.12 to work. IIRC here is how I did it:

1- remove nordvpn

2-Delete config folder for nordvpn in your home folder

3-re-install nordvpn

4- reboot

5- Open terminal and type nordvpn login

6-enter username and password

7-then nordvpn connect

archtefo commented on 2021-11-06 21:11 (UTC)

Same here, I have to stay with 3.10; neither 3.12 nor 3.11 work for me. 3.12 is saying "Whoops! /run/nordvpn/nordvpnd.sock not found" everytime I try to connect.

h4xnoodle commented on 2021-11-06 01:12 (UTC)

After upgrading to 3.12.0_1 I couldn't connect, or did nordvpn recognize my login information. Something seems to be wrong with this version wrt connecting to the nord servers, at least for me. Downgrading restored usual functioning.

Archking commented on 2021-11-05 08:03 (UTC)

After nordvpn is disconnected under archlinux, the DNS of this machine is still the DNS of nordvpn. This is a fatal error. Can it be solved if it exists all the time? But there is no such problem under debian, I have no such problem with protonvpn. Hope to be fixed such an error