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 .. 44 45 46 47 48 49 50 51 52 53 54 Next › Last »

bubuntux commented on 2019-04-19 04:25 (UTC)

i have being trying to update to 3.0.0_4 but i'm getting an error saying that the daemon is not running, when it is, not sure what's up tbh

jasondaigo commented on 2019-04-12 10:35 (UTC)

i have a question and cant find a answer: does this support multihop or double vpn?

alexkorpas commented on 2019-04-09 17:50 (UTC) (edited on 2019-04-09 18:59 (UTC) by alexkorpas)

When I am trying to connect to any server, it is not responding. Any idea?

The output is the following:

$ nordvpn connect <server>

Connecting to <server>

plarpoon commented on 2019-04-05 12:22 (UTC)

@archieslove, i did the exact same before and flagged it as out-of-date. Customer support confirmed this older version has been blacklisted due to security bug.

archieslove commented on 2019-04-05 11:33 (UTC)

I contacted the Nord support regarding the connection issues 'Whoops! We can't connect you to 'uk777.nordvpn.com'. Please try again. If the problem persists, contact our customer support.'

It seems they have pushed 2.2.0-3 to fix this issue. Arch package is currently on 2.2.0-2.

archieslove commented on 2019-04-04 13:59 (UTC)

Anybody facing DNS leaks after boot-up until we reconnect it ?

<deleted-account> commented on 2019-04-04 11:57 (UTC)

@hE-01 I solved 'transport is closing' by uninstalling nordvpn-bin, then removing the folder '.config/nordvpn', and reinstalling again. It asked me again for credentials, but after that it worked.

RexHackbro commented on 2019-03-10 20:09 (UTC)

@hE-01 yeah I have the same problem 'transport is closing' every time I try to connect to a server. Not quite sure but I think that happens since a 2.x update. Probably 2.0

hE-01 commented on 2019-02-20 17:38 (UTC)

Is anyone else getting 'transport is closing' error with database bucket does not exist in the log?

The service is running and I can log in, I just can't connect.

https://pastebin.com/k9sQfa0i

« First ‹ Previous 1 .. 44 45 46 47 48 49 50 51 52 53 54 Next › Last »