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

nrtr commented on 2020-12-17 20:29 (UTC) (edited on 2020-12-17 20:35 (UTC) by nrtr)

I am informing of the same issue. I had an earlier version installed today before I updated to 3.8.8. The earlier version which was installed with the following process and I was able to connect to the VPN even after a restart.

For info on how I got it running which may be helpful in resolving this.

Commands were entered in the following order.

sudo yay-S nordvpn-bin

sudo systemctl enable nordvpnd.service

sudo systemctl start nordvpnd.service

I have also tried the pinned comments command "sudo systemctl enable --now nordvpnd"

And I get the following "A dependency job for nordvpnd.service failed. See 'journalctl -xe' for details."

I see @nimbusflow has the same I didn't see the drop down show more option. I have the same.

Th30 commented on 2020-12-17 20:06 (UTC)

Hi, +1 loiccoyle. Creating the nordvpn group removes the error message on installation but it is not possible to use the application (error with the service).

loiccoyle commented on 2020-12-17 19:38 (UTC) (edited on 2020-12-17 19:39 (UTC) by loiccoyle)

With the 3.8.8-1 version I'm also having trouble getting the nordvpn service to start, I suspect it has something to do with the error msg I got during installation:

/usr/lib/tmpfiles.d/nordvpn.conf:1: Failed to resolve group 'nordvpn'.
error: command failed to execute correctly

nimbusflow commented on 2020-12-17 19:08 (UTC) (edited on 2020-12-17 20:13 (UTC) by nimbusflow)

Installed 3.8.8-1 and now I can't connect because the system daemon can't be reached.

This is what I see in journalctl after I tried to run the enable nordvpnd command. Any thoughts?

Dec 17 18:48:47 systemd[1]: nordvpnd.socket: TCP_NODELAY failed: Operation not supported

Dec 17 18:48:47 systemd[1]: Starting NordVPN Daemon Socket. Subject: A start job for unit nordvpnd.socket has begun execution Defined-By: systemd Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel A start job for unit nordvpnd.socket has begun execution. The job identifier is 1175.

Dec 17 18:48:47 systemd[1542]: nordvpnd.socket: Failed to resolve group nordvpn: No such process

Dec 17 18:48:47 systemd[1]: nordvpnd.socket: Control process exited, code=exited, status=216/GROUP Subject: Unit process exited Defined-By: systemd Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel An ExecStartChown= process belonging to unit nordvpnd.socket has exited. The process' exit code is 'exited' and its exit status is 216.

Dec 17 18:48:47 systemd[1]: nordvpnd.socket: Failed with result 'exit-code'. Subject: Unit failed Defined-By: systemd Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel The unit nordvpnd.socket has entered the 'failed' state with result 'exit-code'.

Dec 17 18:48:47 systemd[1]: Failed to listen on NordVPN Daemon Socket. Subject: A start job for unit nordvpnd.socket has failed Defined-By: systemd Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel A start job for unit nordvpnd.socket has finished with a failure. The job identifier is 1175 and the job result is failed.

Dec 17 18:48:47 systemd[1]: Dependency failed for NordVPN Daemon. Subject: A start job for unit nordvpnd.service has failed Defined-By: systemd Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel A start job for unit nordvpnd.service has finished with a failure. The job identifier is 1084 and the job result is dependency.

Dec 17 18:48:47 systemd[1]: nordvpnd.service: Job nordvpnd.service/start failed with result 'dependency'.

Dec 17 18:48:47 sudo[1512]: pam_unix(sudo:session): session closed for user root

Dec 17 18:48:47 audit[1512]: USER_END pid=1512 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'

Dec 17 18:48:47 audit[1512]: CRED_DISP pid=1512 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success'

syscall1001 commented on 2020-12-05 16:51 (UTC)

I couldn't login with 3.8.7 and 3.8.6 versions. It worked with the 3.7.4 but I couldn't connect to any server using NordLynx technology, only OpenVPN. The version that everything worked 100% for me is 3.8.5. I went to "view changes", downloaded version 3.8.5, extracted, cd to that, installed with makepkg -si. Everything working.

Zeros commented on 2020-12-05 02:03 (UTC)

On version 3.8.7 I am completely unable to login, tried restarting the nordvpnd service, restarting, deleting my .config/nordvpn dir, no matter what it asks for my email and password, gives me the \|/m and then says, "Whoops! We're having trouble reaching our servers. Please try again later. If the issue persists, please contact our customer support." I've made sure my account is still good, and the app on my phone is working just fine.

rafaelgov95 commented on 2020-11-03 20:13 (UTC) (edited on 2020-11-03 20:14 (UTC) by rafaelgov95)

I'm make version 3.8.6 running.

manja2 commented on 2020-10-22 23:34 (UTC) (edited on 2020-10-22 23:38 (UTC) by manja2)

@esdaniel , I just followed those steps: Downloaded 3.7.4 from https://aur.archlinux.org/cgit/aur.git/commit/?h=nordvpn-bin&id=fec23502d0d729d69cfcce617ba32d7aa586052e , extracted, ran mkpkg, and installed. Then you must terminate the existing nordvpnd process. Then it will work as before.

esdaniel commented on 2020-10-12 13:45 (UTC)

TrimTab: try Tor browser and see if you get same. If you don't, then perhaps check preferred browser's language settings and delete all cookies beforehand.

« First ‹ Previous 1 .. 23 24 25 26 27 28 29 30 31 32 33 .. 54 Next › Last »