Package Details: nordvpn-bin 3.14.2-1

Git Clone URL: (read-only, click to copy)
Package Base: nordvpn-bin
Description: NordVPN CLI tool for Linux
Upstream URL:
Keywords: networking nordvpn openvpn security vpn
Licenses: custom
Conflicts: openvpn-nordvpn
Provides: nordvpn
Submitter: metiis
Maintainer: metiis (Martoko, bubuntux)
Last Packager: Martoko
Votes: 134
Popularity: 2.51
First Submitted: 2018-08-29 12:13 (UTC)
Last Updated: 2022-08-02 13:28 (UTC)

Pinned Comments

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:

Latest Comments

isryn commented on 2022-08-09 19:15 (UTC)

you can fix the "rotating:transport rotator: ptr timer is locked" output like this: 1. sudo systemctl stop nordvpnd.service 2. sudo mkdir /run/nordvpn/ 3. touch nordpvnd.sock 4. sudo systemctl start nordvpnd.service cheers

demiluxmed commented on 2022-08-09 16:33 (UTC)

Getting the same message as ygurin when I try to login

"rotating: transport rotator: ptr timer is locked"

ygurin commented on 2022-08-06 23:14 (UTC)

I seem to be getting this on login

nordvpn login

rotating: transport rotator: ptr timer is locked

Any idea what this could be?

nika commented on 2022-08-04 06:20 (UTC)

Any idea how to use meshnet according to

$ nordvpn set meshnet on                                                                                                                                                                                           
Command 'meshnet' doesn't exist.

arizonajoe commented on 2022-07-24 18:05 (UTC) (edited on 2022-08-02 21:05 (UTC) by arizonajoe)

Having issues with this last update. In order to connect to any specific server using

"nordvpn c Seattle" (or any general or specific server locale, for that matter)

Connecting to United States #8952 ( Whoops! We couldn't connect you to 'Seattle'. Please try again. If the problem persists, contact our customer support.

But when I explicitly specify the Nord-preferred DNS server addresses using

"nordvpn set dns"

resulting in a proven settings change to this:

$ nordvpn settings Technology: NORDLYNX Firewall: enabled Kill Switch: disabled Threat Protection Lite: disabled Notify: disabled Auto-connect: disabled IPv6: disabled DNS:,

the problem vanishes and a successful connection is almost immediate. Whether using Nordlynx or OpenVPN technology, or UDP or TCP protocol, I must explicitly set the DNS addresses or I get no connection. I looked over the PKGBUILD and install files but see nothing that could explain this. Also, I am logged in, the daemon is enabled and I am a member of the nordvpn group. I do allow Networkmanager to control the writing of resolv.conf. Thoughts? I've reached out to tech support. Situation persists after I flush IP tables. UPDATE, UNRESOLVED: Nord tech support simply recommends adding Cloudflare nameservers and to resolv.conf and making that file immutible: chattr +i /etc/resolv.conf The need for explicit DNS servers in nordvpn-bin was nevertheless unchanged.

UPDATE: The nordvpn-bin update seems to have resolved the above issue.

bunkbail commented on 2022-07-15 19:50 (UTC)

Just putting this out there in case anyone else wants to use the old, but reliable version of nordvpn. nordvpn-bin-3.7.4-1-x86_64.pkg.tar.zst

f1she3 commented on 2022-07-09 08:12 (UTC)

Hi ! Thanks for maintaining,

Here's a quick suggestion : when installing the package, directly suggest the automatic command to be added to the nordvpn group :

sudo gpasswd -a $(whoami) nordvpn

Have a nice day

theriddick commented on 2022-06-30 01:59 (UTC) (edited on 2022-06-30 04:39 (UTC) by theriddick)

Doesn't work for me.

[Error] TELIO: telio_disconnect_from_exit_nodes: Err(NotStarted)

[Error] adding drop: adding iptables rule 'INPUT -i enp42s0 -j DROP -m comment --comment nordvpn': exit status 1: Warning: Extension comment revision 0 not supported, missing kernel module?

Is this nordvpn app dependent on specific kernel modules? if so what ones?

UPDATE: SOLVED, Ended up being my modprobed.db file missing some stuff so I booted to default kernel and ran through it again.

bensums commented on 2022-06-29 09:24 (UTC)

On Ubuntu, the meshnet command is available, but it doesn't seem to be available with the version from this package. Both versions are 3.14.1

Snayler commented on 2022-06-10 08:22 (UTC) (edited on 2022-06-10 08:32 (UTC) by Snayler)

Keep getting out-of-date flags even though the version is the latest at nordvpn repos. Tried installing from nordvpn directly, same issue.

Seems like uninstalling and rebuilding nordvpn-bin again solves the issue.

Fox_2712 commented on 2022-06-06 16:51 (UTC)

I have the same problem. App just opens and closes.

chovy commented on 2022-06-05 13:17 (UTC)

app just opens and closes.

steventrouble commented on 2022-06-04 03:30 (UTC)

If you want to get the latest version, simply clone the git repo, update the version to the latest version (e.g. 3.14.0), and remove the SHA sum lines.

To clone: git clone To build: makepkg

android_aur commented on 2022-05-24 16:54 (UTC) (edited on 2022-05-24 16:57 (UTC) by android_aur)

With the newest NordVPN version I get this small error message when trying to connect:

$ nordvpn connect
rpc error: code = Unimplemented desc = method IsMeshnetAvailable not implemented
Connecting to XYZ #XYZ (
You are connected to XYZ #XXX (!

This part: rpc error: code = Unimplemented desc = method IsMeshnetAvailable not implemented

The VPN still seems to work but with older versions I never got this error message.

Photonik commented on 2022-05-24 15:09 (UTC)

Would it be possible to get this package updated? I am getting an out-of-date flag on login. Thank you for your hard work!

wyanricks commented on 2022-04-24 01:53 (UTC) (edited on 2022-04-24 01:54 (UTC) by wyanricks)

For anyone trying to use the new login mechanism and don't want to use the --legacy option, you can run 'nordvpn login' login though the web browser, and then copy the link provided. It should be a link starting with nordvpn:// and your token included.

Then run 'nordvpn login --callback "<nordvpn:// link>"'

Replace "<nordvpn:// link>" with whatever you copied, but keep the quotes around it.

Sensu commented on 2022-04-05 21:41 (UTC)

Please add xterm as a dependency to this. I was not able to sign with my nordvpn credentials until I installed xterm in my system.

iZiboi commented on 2022-03-20 19:03 (UTC)

@MidnightStarSign Yeah, i am facing the same issue

MidnightStarSign commented on 2022-03-20 16:53 (UTC)

I'm having issues where after the computer has been on for a while, the VPN hangs in terminal for 5+ minutes trying to connect using nordvpn connect.

It works otherwise :D

Usually, a reboot solves it until it does it again. Using systemctl restart nord* works sometimes, but not others.

manja2 commented on 2022-02-28 05:00 (UTC) (edited on 2022-02-28 05:02 (UTC) by manja2)

Just wanted to share my experience with this package. I've been using nordvpn-bin for the last 2 years, because I had signed up for the 2-year special discount with nordvpn. Throughout that time, this package was very unstable and was the source of many headaches such as:

  • Sometimes it would not connect, and the killswitch could not be turned off. So the only solution was to uninstall, and then restart.

  • Sometimes it would not connect on certain public networks such as library wifi.

  • Sometimes it would only connect to servers from costa rica, and I had to manually select the country using the cli commands.

  • Sometimes the autoconnect feature would not automatically connect, and I had to always remember to check if my vpn is connected, when I start the system.

  • Sometimes these issues would last several days, and I was forced to install an older version which didn't have those issues.

I think these are not issues related to the nordvpn servers, because I never had these issues with the android app, or the macOS app, or the ubuntu cli.

I recently tried Mullvad for 1 month and I didn't have any of the issues I had with nordvpn. I'm not trying to promote them, and I'm not affiliated with them, but I really think it's the best vpn service for arch linux.

sl1pkn07 commented on 2022-02-23 15:19 (UTC)

hi. is possible add


to the .desktop file? this makes for example put the app into the Network menu


malibu commented on 2022-02-16 03:04 (UTC)

Thank you that was it. I was totally overthinking it.

UNP6GDXDXA commented on 2022-02-13 10:38 (UTC)

@malibu Try running: sudo nordvpn set firewall on && sudo nordvpn set killswitch on

malibu commented on 2022-02-05 15:02 (UTC)

Hi, I installed nordvpn-bin once and was able to enable killswitch. I had some problems that turned out to be my fault, but in the course of finding this out I uninstalled nordvpn-bin and ufw, and I flushed iptables. Now I have reinstalled nordvpn-bin and ufw and enabled them but when I try to enable killswitch I get a message "Firewall must be enabled to use 'killswitch'".

Does anyone know what the binary is looking for so that I can get this to work again? Thanks.

luismario commented on 2022-01-25 18:17 (UTC) (edited on 2022-01-25 18:26 (UTC) by luismario)

@jade To list the servers you could download the NordVPN server list: 'wget && unzip'. You will get two directories 'ovpn_udp' and 'ovpn_tcp'.

To connect to a specific server you can use the short format of the city and the server number, e.g. 'nordvpn connect uk2329'.

If you want to find a server with your prefered protocol/technology you can use the 'Server recommended' tool by NordVPN(

a3dman commented on 2022-01-20 18:19 (UTC)

Any idea why this error happens on connect: [Error] turning on nordlynx: Out of file descriptors

jade commented on 2022-01-19 14:54 (UTC)

Hi, Is it possible for me to get a list of servers in a country and connect to a specific server? For example, there is only 1 city available in the UK but there are several servers (400+). I want to be able to connect to server #nnn. But how do I get a list of those server numbers? I know I can do that in Windows using the app but the app is not available in linux.


Satan commented on 2022-01-16 18:37 (UTC)

I recently ran into issues after updating, "Whoops! Cannot reach User Daemon." Checking with "systemctl status nordvpnd" showed that it crashed without giving any real reason. This happened to me because because I am running NetworkManager and was not using systemd-resolved. Fix is linked here:

Hope it helps.

joshfiveo commented on 2021-12-18 10:20 (UTC)

@rf2020 My speeds are the same, and my ping is really good as well. I have the wireguard-tools package installed, and am using Nordlynx. I'm on nordvpn-bin 3.12.2-1

rf2020 commented on 2021-12-18 09:05 (UTC)

A question for those who are using the latest update with nordlynx (wireguard): how are your upload/download speeds? I ask because of my experience with nordvpn on windows.

On linux with nordvpn-bin 3.12.1, my speeds with nordlynx are barely reduced, but when I was forced to adopt the new app to login on windows, my downloads went from 250 Mbps without to 50 Mbps with (and yes, that was with nordlynx)! There were similar reductions for upload speed. Thus I'm risk-averse now on linux.

Thanks for your info!

joshfiveo commented on 2021-12-17 23:51 (UTC) (edited on 2021-12-18 00:07 (UTC) by joshfiveo)

I found a fix, if anybody is struggling to login with new update.

I just had to use the legacy flag for login: "nordvpn login --legacy"

It doesn't support MFA, so disabe that, then login via CLI, and enable MFA again after.

Archanfel80HUN commented on 2021-12-17 23:42 (UTC)

Yes i had this issue too, but only with chrome. I did opened the url with firefox and after i login it opened a blank terminal for a few seconds and it worked.

joshfiveo commented on 2021-12-17 23:41 (UTC)

@Archanfel80HUN I already have group and service running. The problem I am running into is, that when I get the "Choose an application to open the nordvpn link"-prompt and select NordVPN (or alacritty, or nordvpnd, or xterm, or terminator) in the browser, nothing happens. So I can get the link and login in the browser, but can't open the nordvpn link in the cli to finalize login.

Is there a manual way to open the link in the cli?

Archanfel80HUN commented on 2021-12-17 23:36 (UTC)

@joshfiveo Wait! There is two more thing. 1) You have to enable and run the nordvpnd systemd service and make sure that your user is added to the nordvpn group. Otherwise cant save the configuration!

joshfiveo commented on 2021-12-17 23:34 (UTC)

@Archanfel80HUN No success, but thanks for the help. :)

Archanfel80HUN commented on 2021-12-17 23:28 (UTC)

@joshfiveo My default konsole app is 'terminator'

joshfiveo commented on 2021-12-17 23:27 (UTC)

@Archanfel80HUN Would you mind telling me which terminal emulator you are using? I uninstalled uBlock and disabled my pi-hole, but still no success. Maybe NordVPN doesn't play well with alacritty

Archanfel80HUN commented on 2021-12-17 23:20 (UTC)

@joshfiveo I contacted the support, they said this and it works. Firefox and also make sure that you're not using any adblocker for the moment.

joshfiveo commented on 2021-12-17 23:18 (UTC)

@Archanfel80HUN Firefox is not working for me.

I'm on i3 gaps if that makes a difference. I choose the default NordVPN option to open link with, but nothing happens.

Archanfel80HUN commented on 2021-12-17 23:08 (UTC)

Nordvpn login currently not working from chrome (or any chrome variant), use firefox for the auth url, login then the firefox browser will open a cli windows and login the cli app itself, save the nordvpn.conf file too.

jrichard326 commented on 2021-12-17 19:25 (UTC)


Excuse the late reply. Make certain that nordvpnd.socket is enabled on your system

joshfiveo commented on 2021-12-17 09:10 (UTC)

Hey, since an update, it is now not possible to login fully within the cli. It now redirects to the browser, but once logged in there, it want to open a link with the Nordvpn app, which doesn't work with the cli.

Anybody have a way to work around this.

I tried opening the link with nordvpn, nordvpnd and alacritty, but nothing.

Gamall commented on 2021-12-11 20:48 (UTC)


Have you tried connecting to other servers, changing to another protocol, deleting config folder and logging in again, reinstalling, etc ?

Techi-Joe commented on 2021-12-11 20:03 (UTC)

getting this error currently: nordvpn c transport is closing

iZiboi commented on 2021-12-06 15:55 (UTC)

I also confirm that, wireguard-tools fix the disconnect issues. It also fixed "nordvpn set autoconnect" in my case.

snowShiba commented on 2021-12-02 16:36 (UTC)

I'd like to also confirm that since installing wireguard-tools and rebooting I have not had any disconnecting issues. I am currently on 10 hours of uptime, where prior to installing wireguard-tools I would have to restart every ~2 hours to fix NordVPN.

Gamall commented on 2021-11-30 19:02 (UTC) (edited on 2021-11-30 19:03 (UTC) by Gamall)

As a further datapoint, installing wireguard-tools on kubuntu also fixed the ~2h10m (previously ~4h20) issue (connected 5h41 and going). I did nothing other than installing the package and rebooting. This issue is not specific to Arch, nor, it appears, is its solution.

equalis3r commented on 2021-11-23 22:37 (UTC) (edited on 2021-11-23 22:38 (UTC) by equalis3r)

@rabcor: Thanks a lot for your information. Using wireguard-tools fixes the issue with NordLynx for me. No disconnection and service drop after more than 4 hours of usage. Before, with version 3.12, nordvpn only worked for 2 hours before service dropped.

I add fallback DNS to resolved.conf. Not sure how it's gonna work out since I need nordvpn to break first :))

//I'm using systemd-networkd and systemd-resolved.

3ddi commented on 2021-11-23 09:19 (UTC) (edited on 2021-11-23 12:31 (UTC) by 3ddi)

It seems after installing wireguard-tools the VPN connection is recognized by NetworkManager Also as mentioned by @jrichard326 removing .config/nordvpn config folder and reinstalling solved the issue that although nordvpn connect was possible, the connection seemed broken (not able to connect/ping to any server).

However, I did not explicitly test whether the connection problems were solved by installing wireguard-tools or by removing the config folder.

EDIT: After going to suspend the nordvpn again was not able to send any requests/pings to any server. The solution was to delete .config/nordvpn/ and nordvpn connect

rabcor commented on 2021-11-22 22:29 (UTC)

For everyone who has been having issues with nordvpn disconnecting every X hours ( @Libly_Fait @equalis3r )

I had the same issue for a while now where every 4 hours and 20 minutes I would be disconnected and have to restart nordvpn to be able to connect again, after the latest update (3.12.1) it changed and started doing it every 2 hours and 10 minutes instead.

The issue was solved for me by installing the wireguard-tools package. At least it appears perfectly solved (I've had no issue with the connection for 12 hours)

I think maybe if more users confirm it solving their issue it should be added as an optional dependency for this package (for people who want to use nordlynx)

Also, for the DNS issue, you can resolve it by configuring your system to use systemd-resolved to manage your DNS. There's a guide for doing it here (although for manjaro):

Mundamugus commented on 2021-11-22 11:51 (UTC)

Thank you very much @GoldenDreamcast and @langtudeplao. Downgraded to nordvpn-bin 3.10.0_1-1 and everything works as it should. Just had to delete old config file and login again. Thanks again

equalis3r commented on 2021-11-22 09:56 (UTC)

@Mundamugus: You can use git log and then git checkout to the suitable commit. git checkout e01bd1fc828c Then cd to the dir and makepkg -si

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

@GoldenDreamcast | sorry I'm a real noob but I cloned the repo using
"git clone" 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

Archking commented on 2021-11-05 07:50 (UTC)

Hello I have been using this package to install but there has been a problem with it that has not been fixed, every time I go to install it in a fresh install I am prompted with::: Processing package changes... chattr: There is no such file or directory when trying to make a stat call to /var/lib/nordvpn/data/* Error: The command was not executed correctly" "This error has always existed I use arch as well as manjaro,garuda, all three systems have this problem, what is the cause of this error, how do I fix it?

copperteal02 commented on 2021-11-04 17:14 (UTC)

As of 04-Nov-2021, the latest version is

joehillen commented on 2021-11-02 20:51 (UTC)

This is not out of date. If you look here, the latest version is 3.11

Can someone remove the flag?

Paradox625 commented on 2021-10-26 19:49 (UTC)

This package has been flagged out of date for a month at the time of posting, but has no issues with building or running the package.

jarlaxle commented on 2021-10-21 06:58 (UTC) (edited on 2021-10-21 06:59 (UTC) by jarlaxle)

is anyone able to connect to a specific server?

nordvpn c de1045
Whoops! Something went wrong. Please try again. If the problem persists, contact our customer support.

This happens for me no matter what technology or protocol i am using

cgundogan commented on 2021-10-01 12:35 (UTC) (edited on 2021-10-01 12:41 (UTC) by cgundogan)

Is anyone else seeing this problem in the logs when starting nordvpnd?

json: cannot unmarshal string into Go struct field AutoConnectData.auto_connect_data.protocol of type config.Protocol


I removed the package and deleted everything in /var/lib/nordvpn, then reinstalled. After specifically saying nordvpn logout and nordvpn login, everything works fine again.

archtefo commented on 2021-09-30 14:04 (UTC)

@rok.lesjak, yes, I've used NetworkManager in the past, althoug since recent updates of KDE in Arch it stopped working for me ( so I'm stuck with the proprietary client. Thanks!

rok.lesjak commented on 2021-09-30 04:56 (UTC)

I'm connecting to NordVPN with NetworkManager, it works great.

archtefo commented on 2021-09-30 00:32 (UTC) (edited on 2021-09-30 14:09 (UTC) by archtefo)

Version 3.11.0_1-1 is not working for me. It is showing this error: "It seems there's an issue with the config file. If the issue persists, please contact our customer support." Even if I correct "warning: directory permissions differ on /var/lib/nordvpn/data/". Had to downgrade to 3.10.0-1 (working fine so far).

Edit: since today, version 3.10.0-1 is presenting issues: it gives me errors about my account data or expiration. After several attemps it is working for now.

Oceanarium commented on 2021-09-29 10:18 (UTC)

Hello I've been getting "Wired Ethernet: Connected to Wired connection 1 (limited connectivity)" for 6+ months whenever I connect to any server within the app. This happens no matter which technology I use, or which type of server (group). I thought there was a bug so I've been waiting for a fix. It has been happening to me on both Manjaro and vanilla Arch linux. How could this be fixed?

esdaniel commented on 2021-09-16 15:32 (UTC)

@Th30 choice is good, I'm happy here for now but will check out wgnord thread from time to time to see how it progresses. Thanks for the info.

Th30 commented on 2021-09-16 04:10 (UTC)

After many problems with this package, I opted for wgnord.

iZiboi commented on 2021-09-12 08:50 (UTC)

@mmt84 I have set protocol UDP still doesn't work

mmt84 commented on 2021-09-11 15:45 (UTC)


You should try changing the protocol you use. It may or may not solve your problem.

nordvpn set technology NordLynx/OpenVPN nordvpn set protocol UDP/TCP

P31314 commented on 2021-09-11 13:46 (UTC)

Heyho, I am at an airport and I get "We were not able to fetch your account data. Please check your internet connection and try again. If the issue persists, please contact our customer support." someone an idea where the problem could lay? even if it is just for tthe next time

tyler19820201 commented on 2021-09-09 13:53 (UTC)

Any chanche to get fixed the "account expired" issue? I am now using 3.7.4 as 3.10 does not work anymore. However it was working around 4 weeks ago...Strange

viking777 commented on 2021-09-08 12:04 (UTC)


I have had exactly the same problem with nordvpn-bin (your account has expired). Your solution worked for me too although I did have to install the dependency ipset before I could continue with the build.

Thank you for explaining your solution so fully, it makes it much easier to follow.

rok.lesjak commented on 2021-09-06 13:32 (UTC)

@Poilrouge It now works after following your instructions. Thank you!

Poilrouge commented on 2021-09-06 12:02 (UTC) (edited on 2021-09-06 12:03 (UTC) by Poilrouge)


So I've been adressing this same issue with the nordvpn help center. They made me uninstall the client and install the 3.7.4 version, which works. Been told to wait for the next version of the client to get back up to date (was at 3.10.0).

To downgrade to 3.7.4 from the AUR, I used:

sudo pacman -R nordvpn-bin
git clone
cd nordvpn-bin
git checkout fec23502d0d729d69cfcce617ba32d7aa586052e
makepkg -f
sudo pacman -U nordvpn-bin-3.7.4-1-x86_64.pkg.tar.zst
sudo systemctl restart nordvpnd.service

rok.lesjak commented on 2021-09-05 10:32 (UTC) (edited on 2021-09-05 10:38 (UTC) by rok.lesjak)

After running command: "sudo nordvpn connect" I get output: "Your account has expired. Renew your subscription now to continue enjoying the ultimate privacy and security with NordVPN."

My account and subscription is active. Why I'm getting this error?

I have already tried reinstalling and relogging.

nrobinson2000 commented on 2021-08-31 09:35 (UTC)

This is probably an upstream issue, but shouldn't nordvpn.service and nordvpn.socket be writable only by root?

From journalctl -f:

systemd[1]: Configuration file /usr/lib/systemd/system/nordvpnd.service is marked world-writable. Please remove world writability permission bits. Proceeding anyway.
systemd[1]: Configuration file /usr/lib/systemd/system/nordvpnd.socket is marked world-writable. Please remove world writability permission bits. Proceeding anyway.

arizonajoe commented on 2021-08-30 21:36 (UTC)

Apparently, a problem at NordVPN appears to have been responsible for the NordLynx protocol failure earlier today. Re-installing nordvpn-bin works fine now.

arizonajoe commented on 2021-08-30 16:23 (UTC) (edited on 2021-08-30 17:02 (UTC) by arizonajoe)

Despite having enabled the nordvpn daemon and adding my username to the 'nordvpn' group, and having been a three-year user of NordVpn, today, I can connect to no servers that I desire by server number or city, and in terminal, when waiting for my credentials to authenticate and sign into a specific server, (which took 2 minutes!) the command 'nordvpn status' yields my own town and's location feature reveals a map of my street address using their google maps applet. (Of course, I have disabled WebRTC and Geo-enablement in Firefox, and the nord app still betrays my location).

Here's a sample of what I get on terminal:

I selected L.A., I got Phoenix. Another time, selected Dallas, I got Phoenix. But I was not protected by the encrypted tunnel. My house was dead center on the map in Phoenix at
Just removed nordvpn-bin; installed nordpy, which works.

chapa commented on 2021-08-30 00:03 (UTC) (edited on 2021-08-30 01:05 (UTC) by chapa)

What is?? "It's not you, it's us. We're having trouble reaching our servers. If the issue persists, please contact our customer support." I don't connected. Help, please. Thanks.

PS " If your password is over 48 characters" My pass is less 12

The connection was established using nordpy.!!

i-mw commented on 2021-08-25 15:08 (UTC)

Can't download this package in a country that blocks nordvpn servers (like China).. I got this to work by editing PKGBUILD locally and replacing "" in every sentence in the sources to the alternative website provided officially by Nordvpn >> "".. You should do this here on Aur

zeusmark commented on 2021-08-21 21:42 (UTC)

One issue I ran into when I switched over to Linux from Windows was my password length. When logging in from the terminal you will get this error "It's not you, it's us. We're having trouble reaching our servers. If the issue persists, please contact our customer support." If your password is over 48 characters. After a few hours of frustrating conversations with tech support and trial and error I finally figured that out on my own though so hopefully it will save a few people some headaches.

satman commented on 2021-08-18 13:19 (UTC)


Worked for me as well (connected for 24 hours as of writing), thanks a lot!

typewar commented on 2021-08-15 15:29 (UTC)

For the last couple of months, I've experienced random disconnects (nordvpnd freezes, become unresponsive) while using NordLynx technology. Back and fourth with support didn't exactly help much.

It turns out I had to install wireguard.

I can confirm it has been running stable now for 12 hours straight.

Can this be added as a recommendation ?

gary9872 commented on 2021-08-02 15:25 (UTC)

This thread may be of some help if you are have connection issues.

thiccpad commented on 2021-08-02 05:44 (UTC)

@manja2 I have the exact same issue as you and it still doesn't work, I wonder what they broke on their end.

esdaniel commented on 2021-07-29 09:53 (UTC)

@doctorcolossus hi and yes, one of the things I forgot to mention yesterday is 'we' deleted some conf files too... anyhow it's currently working for me with the following:

Technology: NordLynx Firewall: enabled Kill Switch: disabled CyberSec: disabled Notify: enabled Auto-connect: enabled IPv6: enabled DNS: < Unbound DoH resolver :-)

doctorcolossus commented on 2021-07-28 23:13 (UTC)

@esdaniel: I also contacted Nord support and went through some of the same steps (deleting settings data, temporarily disabling ipv6, etc.). What finally worked was the guy asked me to downgrade to 3.8.4. Then on trying to connect it blocked my internet connection and hung for about a full minute, but eventually finally connected. Later I decided to upgrade back to 3.10 and... it also worked. Very strange. I am thinking it may be / have been (?) a temporary server-side issue.

Did you get yours working again?

manja2 commented on 2021-07-28 21:52 (UTC)

After normal use for a few months, today nordvpn-bin gave me issues: - nordvpn c prompts me to enter my login credentials. Upon entering, it says It's not you, it's us. We're having trouble reaching our servers. If the issue persists, please contact our customer support. - But killswitch was on before the issue, so now I also can't reach the internet without nordvpn. And if I do nordvpn set killswitch off, I get You are not logged in. - Restarting the daemon gave the same results. - The only solution so I can reach the internet NOW, was to uninstall nordvpn. - I later installed an old version which worked, 3.7.4.

esdaniel commented on 2021-07-28 10:43 (UTC)

Update for everyone: spent an hour with nordvpn support, they don't know what's broken after checking plenty > from disabling ipv6, using their DNS servers, deleting their settings data, switching from Lynx to OpenVPN, then switching from UDP to TCP. Nothing worked!! So don't waste time checking and re-configuring. Hopefully I can update us later today when I get some feedback from this morning's checks/attempts.

esdaniel commented on 2021-07-28 09:03 (UTC)

@doctorcolossus Yep, hit me this morning. I logged out and back in again, which was reassuring that was working, then got the same error message: "Your account has expired. Renew..." etc.. Like you, my account is in good standing. Going to DM NordVPN now on Twitter to see if they know more.

doctorcolossus commented on 2021-07-27 04:09 (UTC)

After about a year of working properly, today nordvpn connect started giving me this on both of my arch linux laptops:

$ nordvpn connect
Opening the web browser...
If nothing happens, please visit
Your account has expired. Renew your subscription now to continue enjoying the ultimate privacy and security with NordVPN.

My subscription will not expire for a long time. In Windows, the NordVPN client connects to the same account with no problem.

Anybody else suddenly getting this? Any ideas? Thanks.

Th30 commented on 2021-05-24 02:01 (UTC) (edited on 2021-05-24 02:05 (UTC) by Th30)

Hi, for those who have a disconnection problem and are forced to restart the daemon, you need to downgrade to version 3.9.2 or activate OpenVPN instead of Nordlynx. To do this you need to run the command nordvpn s technology OpenVPN and reconnect to a server.

@Martoko: as suggested by joehillen think about adding in the PKGBUILD the 644 permissions for the concerned files. Thank you.

joehillen commented on 2021-05-17 21:14 (UTC) (edited on 2021-05-17 21:15 (UTC) by joehillen)

I'm constantly seeing these log messages. Please fix this:

May 17 14:09:25 t480 systemd[1]: Configuration file /usr/lib/systemd/system/nordvpnd.service is marked world-writable. Please remove world writability permission bits. Proceeding anyway.
May 17 14:09:25 t480 systemd[1]: Configuration file /usr/lib/systemd/system/nordvpnd.socket is marked world-writable. Please remove world writability permission bits. Proceeding anyway.

s1lv3r commented on 2021-05-16 22:38 (UTC)

@rezanmz marked this package as outdated with the reason "Outdated", but according to the release notes the latest version is 3.9.4, the same as the PKGBUILD is providing.

Additionally, the NordVPN deb pool lists 3.9.4 as the latest version.

What should be done in situations like these?

Arawindor commented on 2021-04-27 14:27 (UTC) (edited on 2021-04-27 14:29 (UTC) by Arawindor)

Hi to all, the subnet whitelist doesn't work with my Arch Linux Thinkpad T570: I've whitelisted both LAN and VPN subnet, but I can't ping LAN.
I've reinstalled twice, switched from OpenVPN to NordLynx technology, restarted several time systemd's nordvpnd service, but I can't ping local network while I'm connected to NordVPN.
Any advice?
Here's my nordvpn settings:
Technology: NordLynx
Firewall: enabled
Kill Switch: disabled
CyberSec: disabled
Notify: enabled
Auto-connect: disabled
DNS: disabled
Whitelisted subnets:

esdaniel commented on 2021-04-21 07:04 (UTC)

@arizonajoe iptables confs could be a red herring. As you say.. everything else works and then it slowly deteriorates, you've got a decent connection too which could mean traffic shaping via your ISP is taking place or perhaps even at Nordvpn. Might be best to send Nordvpn a DM on Twitter to help them diagnose given you've checked everything 'your side'. FYI I asked for their help once before and they were responsive, supportive and effective in helping me diagnose my issues.

arizonajoe commented on 2021-04-20 16:21 (UTC) (edited on 2021-04-20 16:38 (UTC) by arizonajoe)

I have been having issues with nordvpn-bin for over a year. Within 10 - 15 minutes "on the clock," something happens to severely restrict though-put, whether I use NetworkManager in Plasma/KDE or Gnome. It matters not. Yes, I make sure that the service is started and enabled. Yes, this user is a member of the group. The connection always starts out to be excellent whether using NordLynx or OpenVPN, and whether Cybersec is on or off. And it makes no difference which server I connect to. Sometimes the connection deteriorates slowly, and at other times, it becomes "constricted" faster, and requires a reboot or iptables restart. I have not looked at the IP tables but assumed that nordvpn broke them. And the system tray icon in Plasma/KDE gets the requisite exclamation mark telling me my connectivity is limited.

This happens whether on WiFi or on Ethernet. I am using a fast fiber connection near 1000MB/sec. A restart of the iptables fixes the though-put temporarily, but the exclamation point warning of limited connectivity in the system tray connection icon remains.

sadiqu commented on 2021-04-19 17:35 (UTC)

@ledom05 When my connection randomly closes I usually do a pkill nordvpnd and then sudo systemctl restart iptables and everything goes running again.

5DcNu23aph commented on 2021-03-23 20:31 (UTC)

Still have an issue with "limited connectivity" in Plasma. About 5 minutes in after connecting NetworkManager would notify about "limited connectivity", e.g. no internet access. After that connectivity in some apps (Spotify for example) would be lost, but browser works normally.

Have tried various combinations of settings for the package, but no luck so far. Support agent didn't even try to help, since they have no official support for arch. Flushing iptables and changing permissions for resolv.conf didn't help either.

I have found no working solution for my problem so far.

sylgar commented on 2021-03-23 20:28 (UTC) (edited on 2021-03-23 20:35 (UTC) by sylgar)

@Martoko: have you checked the dependencies of the 3.9.0 Debian package? They have changed from previous versions, so the dependencies of your package may need adjustments too.

LuciRose431 commented on 2021-03-23 11:49 (UTC) (edited on 2021-03-23 11:51 (UTC) by LuciRose431)

There is mistake at line number 26

bsdtar -O -xf *.deb data.tar.xz | bsdtar -C "${pkgdir}" -xJf -

there should be data.tar.gz

ledom05 commented on 2021-03-12 13:57 (UTC)

@sylvite I tried it, but when restore it runs but never finish, I have to stop it with CTRL+Z, and it does nothing.

@esdaniel It can't connect (no error, it endless run but does nothing), but nordvpnd is running.

I also tried stoping nordvpnd and restart it without succes. I always have to reboot.

Sometimes it runs after suspend, sometimes not...

sylvite commented on 2021-03-03 22:38 (UTC)

A lot of times when I have no connection it's because nord left the iptables in a broken state. What I've done is sudo iptables-save to a file (once only) right after a clean reboot before interacting with nord, when I have connectivity. Then when nord gets in this state, do a sudo iptables-restore from that file before using nord. Has saved me from rebooting many times.

esdaniel commented on 2021-03-03 12:18 (UTC)

@ledom05 as nordvpn won't maintain 'stale' connections when you sleep your computer, when you resume your computer just try: nordvpn c to reconnect to nordvpn service. Hope that works for you. If you wish to have internet access and not connect with nordvpn, after resume then run nordvpn d

ledom05 commented on 2021-03-03 12:03 (UTC)

Nordvpn stop working and breaks wifi connection after suspend.

Each time I suspend iwth nordvpn connected, after wake up I have no internet connection. Stoping or restarting nordvpnd does not solve the problem. I have to restart my computer.

dancow commented on 2021-03-01 04:18 (UTC)

@gary9872 Same here on the Nordlynx support. That would be a great upgrade to this package! Otherwise working perfectly with OpenVPN.

nimeton commented on 2021-02-11 15:15 (UTC)

Killswitch is not working for me.

gary9872 commented on 2021-02-05 23:46 (UTC)

Thanks for the package.

OpenVPN seems to work fine. Nordlynx is a mixed bag. Nordvpn won't help much because it's on Arch system. If anyone knows how to make Nordlynx reliable, let me know..

D3d3nD_d00d commented on 2021-01-22 17:34 (UTC)

@hydra Thanks!

hydra commented on 2021-01-22 17:28 (UTC)

I accidentally deleted, my previous comment, so reposting... DIY patch, change the appropriate PKGBUILD lines to:






D3d3nD_d00d commented on 2021-01-22 16:15 (UTC)

@cradcore Yep. This package is almost always late on updates, which is particularly bad for a relatively popular networking security app. There doesn't seem to be a consistent maintainer for the package either, judging by the multiple users listed above. Sigh, it's stuff like this (and the increasing number of broken updates on other packages,) that sometimes has me thinking about going back to an apt-based distro. I love most things about ARCH, but the AUR is a real mixed bag. Oh well, I should probably shut up, as I have nothing useful to add.

cradcore commented on 2021-01-21 19:26 (UTC)

This has been flagged out of date for some time now...When will it be updated?

chovy commented on 2021-01-16 15:52 (UTC)

is there a way to get nordpass on aur too?

gameslayer commented on 2021-01-11 02:37 (UTC) (edited on 2021-01-11 02:43 (UTC) by gameslayer)

Manjaro Arm64

Failed to prepare transaction: could not find or read package

I downloaded the screenshot and did makepkg but it doesn't even create a installable package which might be the issue or part of it.

speedytux commented on 2021-01-08 15:11 (UTC)

Great! Thanks!

sylvite commented on 2021-01-05 13:34 (UTC) (edited on 2021-01-05 13:37 (UTC) by sylvite)

@speedytux, the one linked on the website is nearly 2 years old.

$ wget
$ bsdtar -tvf nordvpn-release_1.0.0_all.deb
-rw-r--r--  0 0      0           4 Apr 15  2019 debian-binary
-rw-r--r--  0 0      0         402 Apr 15  2019 control.tar.gz
-rw-r--r--  0 0      0        3140 Apr 15  2019 data.tar.xz
-rw-r--r--  0 0      0        1262 Apr 15  2019 _gpgbuilder
$ wget
$ bsdtar -tvf nordvpn_3.8.9_amd64.deb 
-rw-r--r--  0 0      0           4 Dec 28 08:07 debian-binary
-rw-r--r--  0 0      0        6776 Dec 28 08:07 control.tar.xz
-rw-r--r--  0 0      0    10440308 Dec 28 08:07 data.tar.xz
-rw-r--r--  0 0      0        1267 Dec 28 08:19 _gpgbuilder

speedytux commented on 2021-01-03 20:46 (UTC)

Is this deb package the same offered on the NordVPN website? That one has the 1.0.0 release version and this one 3.8.9. Would you clarify?

sylvite commented on 2020-12-29 15:59 (UTC) (edited on 2020-12-29 16:59 (UTC) by sylvite)

I've had the same issue as @Zeros with all 3.8.x releases for the past several months, including the recent ones with group-related issues. I've been reverting back to 3.7.4 for quite a while, after attempting to update after every new 3.8.x release. I'm still able to connect fine with 3.7.4 today.

I just today found this post. Disabling the killswitch before connecting, I've finally been able to connect with 3.8.9-- the first time I've been able to connect with any 3.8.x release. (Re-enable killswitch after connecting.)

doctorcolossus commented on 2020-12-29 04:07 (UTC)

@Zeros: Are you sure the service is running? If so, have you by chance configured an $HTTP_PROXY? I discovered that this can interfere with communications between the client and service, but I found workaround in case you need it.

Zeros commented on 2020-12-28 21:03 (UTC) (edited on 2020-12-28 21:05 (UTC) by Zeros)

I've added myself to the nordvpn group and rebooted, but no matter what, I'm unable to log into my account via "nordvpn login" or "sudo nordvpn login", keep getting "Whoops! We're having trouble reaching our servers. Please try again later. If the issue persists, please contact our customer support." after about 30 seconds. I can connect through openvpn, and on the Android app just fine. Version: 3.8.9-1

fabh2o commented on 2020-12-21 19:22 (UTC)

Any plans to add the armel (armv6l) version? The deb in the same path as the others.

benwaffle commented on 2020-12-21 03:14 (UTC)

Would be even better to use the $USER variable instead of whoami

editicalu commented on 2020-12-20 18:52 (UTC)

Pedantic note: would be nice to use whoami instead of the USERNAME placeholder.

tonkku107 commented on 2020-12-20 15:57 (UTC) (edited on 2020-12-20 15:59 (UTC) by tonkku107)

You don't need to restart for the group to be created, that happens when the package is installed. Restarting the services after the group has been added should be enough for users updating the package. You should probably add a post-upgrade note telling people to restart the services after every update.

xmonster commented on 2020-12-20 09:48 (UTC)

With 3.8.8-4 the same trouble after enable demon and added to the nordvpn group still not work

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:

zuzavo commented on 2020-12-20 01:22 (UTC) (edited on 2020-12-20 01:43 (UTC) by zuzavo)

Hi, same here. My solution: Completely remove nordvpn-bin and reinstall following the wiki instructions:

$ sudo groupadd -r nordvpn

$ makepkg -si (or whatever you use to install the AUR package)

$ sudo gpasswd -a <username> nordvpn

After install: sudo systemctl enable --now nordvpnd

And of course:

systemctl enable nordvpnd.service
systemctl start nordvpnd.service

And works fine. Good luck !!!

nimbusflow commented on 2020-12-20 00:42 (UTC) (edited on 2020-12-20 04:23 (UTC) by nimbusflow)

EDIT: It works now, I only needed to restart Arch apparently!

@xmonster same here, now on 3.8.8-2 and although I see that all of the services are running:

nordvpnd.service loaded active running NordVPN Daemon

nordvpnsd.service loaded active running NordVPN System Daemon

nordvpnd.socket loaded active running NordVPN Daemon Socket

nordvpnsd.socket loaded active running NordVPN System Daemon Socket

And I've added my username to the nordvpn group, I'm still getting this when I ran nordvpn: "Whoops! Cannot reach System Daemon".

xmonster commented on 2020-12-19 23:57 (UTC)

With the 3.8.8-2 version I'm also having trouble getting the nordvpn service to start, I'm back to version 3.7.3-1

alium commented on 2020-12-19 17:31 (UTC)

@dapolinario: thank you! @metiis (Martoko, bubuntux) please update your PKGBUILD and add nordvpn.sysusers as mentioned dapolinario

crke commented on 2020-12-18 19:58 (UTC)

@kamil: That worked fine, thank you (using Manjaro). As mentioned earlier, I had also to reboot.

zuzavo commented on 2020-12-18 19:27 (UTC) (edited on 2020-12-18 19:28 (UTC) by zuzavo)

For me creating the group with a simple #groupadd nordvpn and restart systemctl solved de issue.

dapolinario commented on 2020-12-18 15:23 (UTC) (edited on 2020-12-18 15:24 (UTC) by dapolinario)

Create the nordvpn.sysusers file with the information:

g nordvpn - -

Install via PKGBUILD:

install -Dm 644 nordvpn.sysusers "${pkgdir}/usr/lib/sysusers.d/nordvpn.conf"

Finally instruct the user to add themselves to the nordvpn group:

# gpasswd -a USERNAME nordvpn

Aethanjf commented on 2020-12-18 14:38 (UTC)

Following others instruction, the nordvpn service is running. However the user can not interact with the service only root can (this is with the user added to the nordvpn group and after restart).

Th30 commented on 2020-12-18 13:00 (UTC)

For my part, I found out where the problem was coming from. I had created a Firejail profile that worked so far. I had to remove nogroups and noroot to get the app nordvpn running.

nordclinotworkin commented on 2020-12-18 11:15 (UTC)

I'm having some problem. After few minutes of connection, an exclamation mark comes on the wifi (saying Limit connectivity) and then no website loads anymore; as if I'm disconnected.

I've tried the whitelist subnet method (mentioned on the NordVPN CLI Arch wiki), restarted the Network Manager and rebooted but nothing worked. I have to keep disconnecting and reconnecting the wifi in a loop to keep it working. Pinging to and gives fail messages. Only ping to gateway IP address works. Can anybody give some advice? I'm using Manjaro KDE.


eesau commented on 2020-12-18 09:27 (UTC)

@kamil: Works fine, thanks!

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.

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.

kamil 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) 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

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: 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: 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: 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: 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: 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 , 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.

TrimTab commented on 2020-10-11 22:01 (UTC)

On version 3.8.5, I'm getting redirected to the UK/GB versions of websites (such as YouTube) when I'm connected to a US server. Anyone else?

tyler19820201 commented on 2020-09-29 07:23 (UTC) (edited on 2020-09-29 17:17 (UTC) by tyler19820201)

I am just wondering on my debian system nordvpn already updated to the latest 3.8 however my "bleeding edge" arch still stucked on 3.7...Should be update the package by the AUR maintainer. Please. Installing manually by yay -S nordvpn-bin has solved my issue so the latest version has been installed. However i am just confused why was not available in my package-manager list?? I am using pamac.

esdaniel commented on 2020-09-17 09:04 (UTC)

arizonajoe: I don't think it's a KDE thing, works fine with my KDE. Could be a DNS issue. Perhaps run wireshark and observe the packet flows, you might notice some irregular or unanticipated behaviour that is associated with your problem. Finally, the pkgbuild pre-processing script might improve with chattr -Ri /var/lib/nordvpn/* to ensure all new files are successfully written. Try running that command then re-installing.

arizonajoe commented on 2020-09-16 23:31 (UTC)

Despite proper configuration of this fully-updated version of nordvpn-bin, particularly when using Nordlynx's Wireguard-based protocol, connection to a server using nordvpn c "server_of_your_choice" works well and does connect to the server and data will flow for a few minutes, but on "this" older 2013 vintage Dell 7737 laptop, using an Intel 7260 WiFi card and kernel-supplied driver, the connection slows gradually over several minutes and then completely stops. Within the Plasma GUI, the NetworkManager wifi icon in the panel ("system tray") shows the requisite "!" indicating limited connectivity. The particular Nord server choice does not seem to matter. The system must be rebooted to restore a functional network stack. I have not experienced this problem using the OpenVPN protocol.

When I access the very same Nord server a minute later on a different (Windows 10 Pro) machine, the server syncs quickly and functions with unfettered throughput. I suspect that the problem on "this" laptop may be a Plasma/NM issue. I have also not been able to replicate this deterioration in Gnome or classic Gnome, nor have I experienced it in console mode either as root or as a standard user.

WorldwoWires commented on 2020-09-13 11:14 (UTC)

I sorted out my issues with the latest release. Seems that just nordvpn connect no longer picks a server near you geographically. It previously did so automatically. No worries. Specify country and city all is good.

esdaniel commented on 2020-09-11 07:52 (UTC)

@tyler19820201: By referring to the news I was highlighting the fact that developers of AUR package managers needed to update their code, not yourself. So, you just need to get your latest/favourite package manager 'updated'. You then can manually build that package, most have been updated. I use Yay today:

tyler19820201 commented on 2020-09-10 19:45 (UTC)

@esdaniel: i was trying to update my ssh keys for AUR but unable to find the file includes the keys. however if i try to run ssh -keygen -R in terminal i will get no file or directory error...How should i update SSH keys then?? ssh -keygen -R

WorldwoWires commented on 2020-09-10 15:29 (UTC)

There is definitely some different with the 3.8.3-1 release. It does work but I can only connect to 1 server in Costa Rica. Additionally if I issue nordvpn logout and try to login again providing email address and password it fails to connect every time. Anyone else experiencing this?

3.7.4-1 does not exhibit this behavior.

esdaniel commented on 2020-09-10 10:32 (UTC)

@tyler19820201: If you can download, extract to folder and run makepkg, then run pacman -U <package> successfully you should update/change your pkg manager. BTW there were recent key changes for AUR:

tyler19820201 commented on 2020-09-09 18:48 (UTC)

On my package manager still only nordvpn-bin 3.7.4-1 available only no 3.8.3-1... On the terminal i am getting warning about update available but nothing in my package manager....Anyway until 3.7 still works fine i am okay with that.

esdaniel commented on 2020-09-09 16:44 (UTC)

Sorry, everyone. NordVPN team reminded me to use whitelist command ($ nordvpn whitelist add subnet <my_subnet/mask>) so issue resolved :-)

esdaniel commented on 2020-09-09 16:08 (UTC)

Just a heads-up to users... sometime in last couple of days something 'changed'. Before then, no issue pinging RFC1918 (local) addresses then today no joy when VPN 'connected'. Disconnect VPN and can ping, thus it's a firewall issue with how NordVPN interprets existing rules and overlays their own binding to the VPN host IP and dropping 'everything' else based on my tests today. Workaround is f'ing tedious till I script it... first, before connecting to VPN, do an iptables-save of the good conf. After connecting to NordVPN, check the NordVPN IP given that is in the updated firewall rules (take note of those new rules), then restore old fire rules and add the NordVPN rules thereafter thus ensuring LAN Allow is before local nic DROP statement etc. etc..

saddy commented on 2020-09-06 20:52 (UTC)

The package is out of date and no longer works for me. If you have time, please update this to the newest version (3.8.1 which fixed my issue

MiniKoala commented on 2020-09-04 11:52 (UTC)

@MXI i use nordvpn on 2 laptops but the most recent has the same problem, i managed to get it to work by deleting the config file, but it only works once!

MXI commented on 2020-08-23 13:23 (UTC)


Thank you for the work, been using it for quite a few months now, with no issue till yesterday.

I am however encountering the following issue since I updated last: whenever I try to use "nordvpn c", or "nordvpn [option]", I have the following message in red:"It seems there's an issue with the config file. If the issue persists, please contact our customer support."

Is anyone else encountering this or having any suggestion to address?

eesau commented on 2020-07-30 15:11 (UTC)

@Fifis Thanks, it works. And having that as an alias is kind of a temporary fix for this, but i guess i shouldn't have to do that.

Fifis commented on 2020-07-24 16:12 (UTC)

@eesau I am using NetworkManager, so sudo systemctl restart NetworkManager did the job. I have an official reply from the support: Most likely a DNS issue. After you connect to our servers, your local DNS is being overwritten with our DNS to ensure a secure connection to the server. After disconnecting, the DNS is removed so this might be the issue if restarting network manager helps.

eesau commented on 2020-07-19 15:05 (UTC)

Thanks for the app.

Small problem though, I have to reboot to get the connection back after using vpn. Killswitch is off.

Any solution, apart from manually correcting iptables every time?

SR-G commented on 2020-06-30 20:00 (UTC)

Seems that nordvpn-bin3.7.4 has resolved the issue i was encountering about connection being impossible ...

ruffy commented on 2020-06-23 11:11 (UTC)

@hydra: Yes, I have the same problem.

hydra commented on 2020-06-23 08:30 (UTC)

On 3.7.3 is anyone else having iptables rules messed up after disconnect? It seems iptables rules are not restored to pre-vpn connection state after disconnecting or stopping the daemon. I can only get traffic through after manually resetting iptables.

SR-G commented on 2020-06-20 20:52 (UTC) (edited on 2020-06-20 21:28 (UTC) by SR-G)

Also having the error "Whoops! Connection failed. Please try again." or "Whoops! We couldn't connect you to 'germany'. Please try again. " ... any idea how to solve this issue ?!

  • either through OpenVPN, either through Nordlynx ("nordvpn set technology openvpn" then "... nordlynx")
  • either from my own country ("nordvpn connect"), either from another one ("nordvpn connect Germany")
  • same problem after restarting nordvpnd.service through systemctl ("systemctl stop nordvpnd && systemctl start nordvpnd")
  • same problem after forcing a logout/login ("nordvpn logout" then "nordvpn login")
  • same problem after removing everything and reinstalling ("yay --remove nordvpn-bin && sudo rm -rf /var/lib/nordvpn/")

My account is valid (from their website) : "Private and secure internet access (VPN)Active 3 Year Subscription · Next payment at Jan 11th, 2021 "

But from time to time i get : "Opening the web browser... If nothing happens, please visit Your account has expired. Renew your subscription now to continue enjoying the ultimate privacy and security with NordVPN."

Of course most of the time i get "Whoops! We couldn't connect you to 'Germany'. Please try again. If the problem persists, contact our customer support."

Once contacted, support is not helpful at all ("Archlinux is not supported, we only support Ubuntu/Debian"). Interestingly, if i set up a local debian docker container (from scratch) and then install the supported nordvpn package ... i still have the exact same problems ...

jako commented on 2020-05-16 11:00 (UTC)

I have pb with Nordvpn since 4 days : Whoops! Cannot reach System Daemon.

freecandy420 commented on 2020-05-15 09:00 (UTC) (edited on 2020-05-15 09:01 (UTC) by freecandy420)

Anyone having problems when trying to disconnect, and killswitch is on? [NordLynx and CyberSec enabled in settings]

Edit: The package is up-to date, showing the latest version 3.7.2.

dapolinario commented on 2020-05-11 19:47 (UTC)

According to the official documentation, the wireguard-tools package is no longer needed for NordLynx to work. In the first NordLynx implementations, there was an explicit indication of the installation of the kernel modules and support tools for WireGuard. I've tested it and it works 100%!

Zeros commented on 2020-05-11 14:17 (UTC)

Newer version has been available for a few days now.

Karrq commented on 2020-05-05 02:56 (UTC)

ipset should be added as dependency, it's needed to disconnect (at least with nordlynx)

gavinbeatty commented on 2020-05-01 02:21 (UTC)

Would it be possible to add aarch64 support back? It's upstream at (I don't know why the name changed to arm64 instead of aarch64, but I'm running this on aarch64 right now).

commented on 2020-04-27 05:58 (UTC)

Anyone encountered this error when trying to sort servers? sudo nordvpn best -r eu

timeout: sending signal INT to command ‘python3’
Traceback (most recent call last):
  File "/etc/openvpn/client/nordvpn/", line 186, in <module>
    print(get_best(servers, args))
  File "/etc/openvpn/client/nordvpn/", line 105, in get_best
    pings = pingservers(, count=args.pingcount)
  File "/etc/openvpn/client/nordvpn/", line 77, in pingservers
    res = run(
  File "/usr/lib/python3.8/", line 491, in run
    stdout, stderr = process.communicate(input, timeout=timeout)
  File "/usr/lib/python3.8/", line 1014, in communicate
    stderr =

mya711 commented on 2020-04-23 20:10 (UTC)

Will you please update the package to the newest version? Thank you.

esdaniel commented on 2020-04-20 15:45 (UTC)

As we're sharing, you might find these ~/.bash_aliases helpful...


alias nordgood="yay -Si nordvpn-bin | grep --color=never Out-of-date | awk '{ print $3 "" "" $4 }'" alias nordstat="nordvpn status" alias nsc='nordvpn status | grep -i status'

bryanOmalley commented on 2020-04-19 14:41 (UTC)

What the hell is up with those CRs on the status output? I should have went here first, because it took me forever to find out why my scripts suddenly failed.

@Haystack Thank you very much, because I don't know how long I would have kept searching, if I hadn't read your comment.

If anyone is interested, this is how you filter that out with sed: nordvpn status | cat -v | sed 's/\^M-^M ^M//g'

commented on 2020-04-19 04:43 (UTC)

sudo nordvpn list No configuration files found or files too old. Updating now... Downloading nordvpn config files... [] End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and zipfile comment will be found on the last disk(s) of this archive. unzip: cannot find zipfile directory in one of or, and cannot find, period. /usr/bin/nordvpn: line 113: msg_exit: command not found Patching and installing files...

commented on 2020-04-18 01:36 (UTC)

you can use this packagebuild until maintainer fixes

Haystack commented on 2020-04-17 22:57 (UTC) (edited on 2020-04-17 22:59 (UTC) by Haystack)

New update to nordvpn prints a load of invisible garbage characters in its output:

❯ nordvpn status | cat -v                                            
^M-^M  ^M^M-^M  ^MStatus: Disconnected

Broke a couple of my scripts so maybe this will help someone else experiencing similar problems.

dapolinario commented on 2020-04-17 22:12 (UTC) (edited on 2020-04-17 22:13 (UTC) by dapolinario)

Checking the dependencies in the Nordvpn package for Debian, I noticed that some dependencies have changed. The new dependency vector is: depends = ('libxslt' 'iptables' 'procps' 'iproute2' 'ipset' 'ca-certificates')

I'm using NordLynx without any of the two packages below and from what I've researched, NordLynx is a proprietary implementation of Wireguard, it would need further testing, but I think the optional dependencies below could be removed: optdepends = ('wireguard-tools: nordlynx support' 'wireguard-arch: nordlynx support')

commented on 2020-04-17 19:13 (UTC)

I updated it to the new version... If anyone needs it

commented on 2020-04-17 19:12 (UTC)

Updated to the new version 3.7.1

pkgname=nordvpn-bin pkgver=3.7.1 pkgrel=1 pkgdesc="NordVPN CLI tool for Linux" arch=('x86_64' 'i686' 'armv7h') url="" license=('custom') depends=('net-tools' 'libxslt' 'iptables' 'procps' 'iproute2') optdepends=('wireguard-tools: nordlynx support' 'wireguard-arch: nordlynx support') provides=('nordvpn') conflicts=('openvpn-nordvpn') install=nordvpn-bin.install source_x86_64=("${pkgver///-}_amd64.deb") source_i686=("${pkgver///-}i386.deb") source_armv7h=("${pkgver///-}_armhf.deb") sha256sums_x86_64=('2385b1361be082ae18a9d018787cd5e54943e26b9285fca115093aa16897f766') sha256sums_i686=('baf90c370c42bb89fe3dee4c40d0f95adc2e3d393bccea541e9cf9d9a2dd0197') sha256sums_armv7h=('9f7cd08edbb1d50660838b1f035aa01b5943447ad2bebe0a45e604ab8df2912a')

package() { bsdtar -O -xf *.deb data.tar.xz | bsdtar -C "${pkgdir}" -xJf -

mv "${pkgdir}/usr/sbin/nordvpnd" "${pkgdir}/usr/bin"
rm -r "${pkgdir}/etc/init.d"
rm -r "${pkgdir}/usr/sbin"


doctorcolossus commented on 2020-04-14 21:54 (UTC)

@annguyen: See the pinned comment. Did you check that the systemd daemon is running?

If it is and you are still seeing that message, at least you are not alone - I experienced the same issue. I wasn't able to solve it myself, nor was anyone here in the community, and NordVPN refused to help on the grounds that they do not support Arch, so I requested a refund and am now happily using Mullvad.

You can view my original description of the problem here and my follow-ups to suggestions here, here, here, and here.

Zombie later followed up with an idea for me to try. I had already given up, so I didn't bother, but maybe it will work for you.

Otherwise you could try contacting NordVPN support, but I suppose they will also be unable or unwilling to help you, in which case I'm sure you could also request a refund.

annguyen commented on 2020-04-14 10:51 (UTC)

I can't login NordVPN.

when I type "nordvpn login", it shows "Whoops! Cannot reach System Daemon."

I'm missing something, isn't it?

esdaniel commented on 2020-04-10 12:32 (UTC)

rsa: try > systemctl restart nordvpnd


Satan commented on 2020-04-08 09:29 (UTC) (edited on 2020-04-08 09:47 (UTC) by Satan)

pretty much broken. Guessing it has to do with the new kernel.

Edit: NordVPN seems to be having difficulties with their OpenVPN servers atm. Suggest using Nordlynx for the time beeing.

rsa commented on 2020-04-08 03:42 (UTC) (edited on 2020-04-08 03:48 (UTC) by rsa)

I can't connect no matter what. Logging out then in again does not work, uninstalling then reinstalling does not work, the daemon is running and I get the same "Failed to connect to Server #XX" message for OpenVPN and it connects but it's impossible to connect to anything with NordLynx.

Zeros commented on 2020-03-30 16:04 (UTC)

Is there a way to specify using only a P2P server in a specific country? The man page says you can use "nordvpn connect P2P", but is there a way to say, "connect US/P2P"? There is no mention of the connect P2P option on the wiki either.

Martoko commented on 2020-03-28 20:12 (UTC)

Yo, co-maintainer here.

I've removed the archs arm, armv6h and aarch64, as they seem to have disappeared from upstream.

acwest commented on 2020-03-28 19:49 (UTC) (edited on 2020-03-28 19:50 (UTC) by acwest)

commit d513c68db6674bf3bc5f3c8ad0268bec6a15d274
Author: A. Craig West <>
Date:   Sat Mar 21 12:04:08 2020 -0400

    Bump to version 3.7.0-3

diff --git a/.SRCINFO b/.SRCINFO
index 3e3af7c..4c72a9d 100644
--- a/.SRCINFO
+++ b/.SRCINFO
@@ -1,15 +1,12 @@
 pkgbase = nordvpn-bin
    pkgdesc = NordVPN CLI tool for Linux
-   pkgver = 3.7.0_2
+   pkgver = 3.7.0_3
    pkgrel = 1
    url =
    install = nordvpn-bin.install
    arch = x86_64
    arch = i686
-   arch = arm
-   arch = armv6h
    arch = armv7h
-   arch = aarch64
    license = custom
    depends = net-tools
    depends = libxslt
@@ -20,18 +17,12 @@ pkgbase = nordvpn-bin
    optdepends = wireguard-arch: nordlynx support
    provides = nordvpn
    conflicts = openvpn-nordvpn
-   source_x86_64 =
-   sha256sums_x86_64 = 75f9b8fbddd7c52a0e6bc1c1062c97cec8a8b4a6ced940ef4031d8a159fd0d48
-   source_i686 =
-   sha256sums_i686 = 9b0716640add9471351fb15b130f14eae490d591104607ac3da83f3d4c5b5fc8
-   source_arm =
-   sha256sums_arm = 5667e2e64b16c64231e62e3be1a58c182fda8fe5687fb81ca05b3ed0ff24ac46
-   source_armv6h =
-   sha256sums_armv6h = 5667e2e64b16c64231e62e3be1a58c182fda8fe5687fb81ca05b3ed0ff24ac46
-   source_armv7h =
-   sha256sums_armv7h = 74b679d490c7b3487043ef12b9cd01bf327cec13d2b82c8bc789bc676263c16e
-   source_aarch64 =
-   sha256sums_aarch64 = 1f5add8af79aaef4efe7ff4823e24cba6c3c28263260f6bd5d55b63b73e36336
+   source_x86_64 =
+   sha256sums_x86_64 = 0ae46a8e33fe806c8c8e5670d9ee2606b1fd74ad6e092120f6c472f8d3797850
+   source_i686 =
+   sha256sums_i686 = a46c148248457a975d0e1d1d61606b17bd18345505ff4a9e21fea213b6e19997
+   source_armv7h =
+   sha256sums_armv7h = 8faa5a0c9b495728205b643b74ec695e1653eaeec709e40955f87bf5cc259a7b

 pkgname = nordvpn-bin

diff --git a/PKGBUILD b/PKGBUILD
index 4eb83c2..a7588bd 100644
@@ -3,10 +3,10 @@
 # Maintainer: Martoko <mbastholm at gmail dot com>

 pkgdesc="NordVPN CLI tool for Linux"
-arch=('x86_64' 'i686' 'arm' 'armv6h' 'armv7h' 'aarch64')
+arch=('x86_64' 'i686' 'armv7h')
 depends=('net-tools' 'libxslt' 'iptables' 'procps' 'iproute2')
@@ -16,16 +16,10 @@ conflicts=('openvpn-nordvpn')

 package() {
     bsdtar -O -xf *.deb data.tar.xz | bsdtar -C "${pkgdir}" -xJf -

Satan commented on 2020-03-28 19:41 (UTC)

Suddenly stopped working when using OpenVPN backend and now only works with NordLynx.

viggy96 commented on 2020-03-28 19:02 (UTC)

Please update this package to 3.7.0-3

emulti commented on 2020-03-26 14:46 (UTC)

Was getting the "Whoops! We couldn't connect you' error, even after logout/login.

A reboot is necessary to load the new kernel and modules after the running kernel has been updated using pacman. After reboot, Nordvpn-bin works again.

kfallah commented on 2020-03-24 19:06 (UTC) (edited on 2020-03-24 19:06 (UTC) by kfallah)

I am still getting the "Whoops! We couldn't connect you..." error when using both OpenVPN and NordLynx. I have tried logging out and restarting the service. I have the optional wireguard packages installed. I also get "A new version of NordVPN is available! Please update the application." Whenever using any command.

ncage commented on 2020-03-23 00:02 (UTC)

@andryandrew thanks for the solution.

Dawa commented on 2020-03-17 18:54 (UTC)

Confirmed logging out/logging in fixes the connection issue after updating to 3.7.0. Previously, if this was necessary the app would notify you to do so, which didn't happen this time.

andryandrew commented on 2020-03-15 17:17 (UTC)

I had connection problems when installing the latest version (3.7.0). Fixed them by logging out and in again

Haystack commented on 2020-03-14 20:37 (UTC) (edited on 2020-03-14 20:52 (UTC) by Haystack)

Having the same problem as aslan00 and others

Edit: not anymore

aslan00 commented on 2020-03-14 13:48 (UTC)

I have the same problem of nasdack, I have update the package and I'm unable to connect to any server. I have unistalled the package, reboot the system, changed connection settings switching from OpenVPN and Nordlinx, and UPD/TCP but nothing works, I always get the message :

Whoops! We couldn't connect you to "anyserver". Please try again. If the problem persists, contact our customer support.

NewbPlayer123 commented on 2020-03-11 03:13 (UTC) (edited on 2020-03-11 03:16 (UTC) by NewbPlayer123)

@ABOhiccups Auto-Connect doesn't work with NetworkManager on NordLynx. The nordvpnd.service needs an additional dependency: ''.

ABOhiccups commented on 2020-02-18 04:47 (UTC) (edited on 2020-02-18 18:40 (UTC) by ABOhiccups)

NordLynx won't auto-connect after login to XFCE Desktop. I have to connect manually.

Nordlynx won't work. But, OpenVPN does work.

arizonajoe commented on 2020-02-10 19:11 (UTC) (edited on 2020-02-10 19:13 (UTC) by arizonajoe)

NordLynx and Openvpn technologies appear to be working now again after the update to nordvpn-bin was added to the AUR repo. I did have to restart and re-enable the nordvpnd service. Thanks!

eh8 commented on 2020-02-03 19:33 (UTC)

Whoops! Connection failed. Please try again. If the problem persists, contact our customer support.

Restarting systemd service and fiddling with settings does not work.

ABOhiccups commented on 2020-02-03 05:30 (UTC)

NordLynx won't work! I get this error message when connecting to VPN.

Whoops! Connection failed. Please try again. If the problem persists, contact our customer support.

I have to change Technology back to OpenVPN and it works.

eesau commented on 2020-01-28 10:45 (UTC) (edited on 2020-01-28 10:56 (UTC) by eesau)

@archifer "I dubugged it by turning it off then reboot and launch nordvpn and set killswitch ON again and reboot"

For some reason, this didn't work for me. Have to disable nordvpnd and reboot.

archifer commented on 2020-01-27 19:25 (UTC) (edited on 2020-01-27 19:26 (UTC) by archifer)

now there's a new version of nordvpn indeed

archifer commented on 2020-01-26 22:41 (UTC) (edited on 2020-01-26 22:42 (UTC) by archifer)

@stavrakis I faced issues with iptables too but it only happens when activating killswitch for the first time, I dubugged it by turning it off then reboot and launch nordvpn and set killswitch ON again and reboot and from there no more issues..

archifer commented on 2020-01-26 22:30 (UTC)

you should un-flag it as out of date I dunno who flags it if it's not out of date

stavrakis commented on 2020-01-26 16:27 (UTC)

iptables rules keep getting set when killswitch is off, and they have to be removed before even nord can connect.

blind_gh0st commented on 2020-01-24 01:09 (UTC)

@ludaval - This package is not out of date. 3.6.0-3 is the most recent version in the nordvpn debian repo. I am also not seeing the error having just installed.

archieslove commented on 2020-01-20 23:44 (UTC) (edited on 2020-01-20 23:48 (UTC) by archieslove)

Is anybody facing random disconnections on an eduroam connection when auto connect is enabled in the settings ? Turning off auto connect completely eliminates the frequent disconnection. Anybody ?

*It behaves the same after the fresh install.

bhargu commented on 2020-01-18 06:13 (UTC) (edited on 2020-01-18 07:29 (UTC) by bhargu)

Edit: I found the reason for this issue while running strace on nordvpn client. I had a local proxy server configured on my Arch system using /etc/environment. The trace showed that the client was accessing this proxy server for even the 'login' command. I removed these variables from my environment file, restarted the OS and the client started working.

Hi, I tried the nordvpn-bin and I am getting the error message "Whoops! Cannot reach System Daemon.". I tried building different versions of the AUR package, but none of it works. I did a clean install, restarted, etc. Also, yes, I did start the systemd service. I tried the Linux CLI tool with Ubuntu and it worked without any issues.

Does anyone know what this is really about? I have my nordvpn service running and socket listening.

SurlyCycler commented on 2020-01-17 16:44 (UTC) (edited on 2020-01-17 22:02 (UTC) by SurlyCycler)

Hi metils. I have noticed some hickups with the last 2 updates. The previous update openvpn stopped working and wireguard did. However, with this update nordlynx (wireguard) has stopped working and openvpn does.

Note: that there was an update with the kernel linux and linux-lts and wireguard-arch and wireguard-lts. The problem could be there.

I am curious if you might know why? thanks

UPDATE: it works now. I just had to reinstall and remove the ./config/nordvpn file.

Ubermensch commented on 2020-01-14 12:07 (UTC) (edited on 2020-01-16 16:49 (UTC) by Ubermensch)

I still have problems with iptables and killswitch even with the latest version. To fix i disbled killswitch.

j.taala commented on 2020-01-14 11:55 (UTC) (edited on 2020-01-14 11:56 (UTC) by j.taala)

Hey metiis, let me know if you could use another co-maintainer. Updated PKGBUILD to 3.6.0_2 and updpkgsums. Updated on my local machine, tested, and new ver works well. Happy to help keep this AUR pkg up to date if you could use a hand.

Cheers, Jay.

Zombie commented on 2020-01-01 11:22 (UTC) (edited on 2020-01-01 11:23 (UTC) by Zombie)

@doctorcolossus my problem was that ther was no sysctl script for the binary.

So I downloaded the *.deb file extractet in a folder with

  1. ar xv nordvpn_3.5.0-2_amd64.deb

now there should be a file named data.tar.xz that you have to extract with

  1. tar -xvf data.tar.xz

the next step is got to the /etc/init.d folder of the extracted file and copy the file named nordvpn to your /etc/system.d/system folder

  1. cd /etc/init.d
  2. sudo cp nordvpn /etc/system.d/system/nordvpn.service
  3. systemctl enable nordvpn.service
  4. systemctl start nordvpn.service

Now should be able to login with nordvpn login.

drpossum commented on 2019-12-27 13:27 (UTC) (edited on 2019-12-27 13:28 (UTC) by drpossum)

Had the same problem as wassup but only on one machine. The difference is the killswitch setting. Enabling killswitch destroys existing iptables and sets the policies to DROP and only allows DNS traffic and traffic to their CDN. This squashes my other iptables settings (seriously, NordVPN?!) making killswitch not viable anymore.

Third option that worked for me other than manually setting the policy to ACCEPT or downgrading is disabling killswitch

emulti commented on 2019-12-26 18:29 (UTC) (edited on 2019-12-26 18:31 (UTC) by emulti)

I noticed that after loss/re-establish of network connection (or suspend/resume cycle) the DNS settings were NOT restored by nordvpnd, leading to a DNS leak to whatever DNS servers are configured/used in non-VPN state. I investigated, and found:

nordvpn set technology openvpn

If openresolv is being used on the machine, then DNS settings are NOT restored on auto-reconnect. It is necessary to do 'nordvpn disconnect' and 'nordvpn connect' again to restore them.

If systemd-resolved is enabled (see and configured to use the stub resolver (ln -s /run/systemd/resolve/stub-resolv.conf) then DNS settings are correctly restored. nordvpnd is aware of the network connection status and performs an automatic reconnect.

The reason for the above behaviour I guess is because the .deb file used is designed for/tested on Ubuntu, which uses systemd-resolved by default.

nordvpn set technology nordlynx

If the nordlynx/wiregard technology is used the DNS settings are NOT restored after suspend/resume or network disconnect/reconnect. In nordlynx mode, nordvpnd seems not aware of network status and does not perform a reconnect. This applies both on Arch and an Ubuntu VM I used for testing.

In short if using nordvpn-bin, best use openvpn and systemd-resolved, otherwise if you forget to manually disconnect/reconnect nordvpn (for example after a suspend/resume) all DNS queries will be leaked outside the tunnel.

wassup commented on 2019-12-26 16:53 (UTC) (edited on 2019-12-26 16:58 (UTC) by wassup)

The newest update (3.5.0-2) seems to mess up the iptables rules once the nordvpnd.service is enabled via systemctl. The default behaviour is changed to -P INPUT DROP and -P OUTPUT DROP, thus dropping all the IPv4 in and out traffic. Only IPv6 works as it should in this scenario.

There are two solutions to this problem:

1. Either automatically or manually execute the following:
# iptables -P INPUT ACCEPT
# iptables -P OUTPUT ACCEPT
2. Or, downgrade the nordvpn-bin package to version 3.4.0_1-1.

hydra commented on 2019-12-12 12:26 (UTC)

I have had similar issues like the @doctorcolossus, but after trying different settings, it seems NordLynx buggy. Sometimes it works, sometimes it does not. Using technology set to openvpn always works in my case.

I also installed networkmanager-openvpn as a backup for when I do not feel like messing with nordvpn-bin. So far, the NetworkManager openvpn plugin has not given me any issues, so I am convinced it is something with NordLynx.

doctorcolossus commented on 2019-12-11 18:47 (UTC) (edited on 2019-12-11 18:49 (UTC) by doctorcolossus)

@archnix: My issue is not the same as klodep's. My issue is that the userspace console application is not able to communicate with the system daemon.

I don't think it has anything to networking. My resolv.conf is set by dhcp. Running any nordvpn command (including the ones you suggested: "nordvpn c de" and "nordvpn d") resulted in the "Whoops! Cannot reach system daemon" message. So this error occurs before a connection is even attempted - I was not even able to enter my login credentials - the command I wanted to run was "nordvpn login" - but that resulted in the same error message as always, so the stage of even attempting to initiate a connection was never even reached.

I am also pretty confident that nothing is wrong with my network configuration, since 1) that is what I am using to write to you now; 2) I was able to connect to NordVPN via openvpn using the open-source application openpyn; 3) I have now switched to Mullvad and it is working fine over either WireGuard or openvpn; and 4) I previously used Cyberghost and had no connection problems with it either.

For all of the reasons above, I highly doubt the particular problem I was experiencing had anything to do with network issues.

Unfortunately I am no longer able to help troubleshoot this issue, as I have now cancelled my NordVPN subscription, requested a refund, and switched to Mullvad, whose client works seamlessly out of the box on Arch.

root-nix commented on 2019-12-11 11:20 (UTC) (edited on 2019-12-11 11:28 (UTC) by root-nix)

@Lyxmyx @doctorcolossus @klodep

Your issues with nordvpn-bin is a symptom of something fundamentally wrong with your network configuration or maybe a result of using sudo connect - creating a config in the wrong place or with wrong permissions in home folder.

❯ nordvpn c de
Connecting to Germany #442 (
You are connected to Germany #442 (!
❯ cat /etc/resolv.conf
# Generated by resolvconf
❯ nordvpn d
You are disconnected from NordVPN.
How would you rate your connection quality on a scale from 1 (poor) to 5 (excellent)? Type 'nordvpn rate [1-5]'.
❯ cat /etc/resolv.conf
# Generated by NetworkManager
search localnet.lan

jackhistoria commented on 2019-12-11 10:04 (UTC)

@Lyxmyx until nordvpn-bin is stable it might be a good solution for you to use - it double checks the resolve config and works very nice and the code is clean written. It also adds server load checks to linux and yeah, its in the aur. I use it as second layer over my nordvpn-bin even if the killswitch works nice in the script there still is a connection if it doesn't (direct on a 30 bucks open wrt 5G china router)

Hope that helps you

Lyxmyx commented on 2019-12-11 08:43 (UTC)

It no longer updates my resolv.conf after I disconnect from the VPN connection.

So then I'm left with an unusable internet connection because I can't access the DNS servers listed in my resolv.conf because you have to be connected to the VPN to access them.

And I can't bring the dhcpcd service to regenerate the resolv.conf unless I reboot.

It used to update the resolv.conf after I disconnected from the VPN.

doctorcolossus commented on 2019-12-06 11:41 (UTC) (edited on 2019-12-06 11:45 (UTC) by doctorcolossus)

I haven't updated the kernel since installing nordvpn. This is my first attempt to install nordvpn and it has not worked for me at all yet. I tried completely removing nordvpn as suggested at the Manjaro forum link you provided, by deleting /var/lib/nordvpn/. There were no immutable files there, in my case. I then restarted, reinstalled, reenabled the systemd service, and restarted again. The nordvpn command still gives me the error: "Whoops! Cannot reach System Daemon."

# nordvpn login
Whoops! Cannot reach System Daemon.
# uname -a
Linux xps3 5.4.1-arch1-1 #1 SMP PREEMPT Fri, 29 Nov 2019 13:37:24 +0000 x86_64 GNU/Linux
# systemctl status nordvpnd.service
● nordvpnd.service - NordVPN Daemon
     Loaded: loaded (/usr/lib/systemd/system/nordvpnd.service; enabled; vendor preset: disabled)
     Active: active (running) since Fri 2019-12-06 04:31:43 MST; 11min ago
TriggeredBy: ● nordvpnd.socket
   Main PID: 29011 (nordvpnd)
      Tasks: 13 (limit: 19034)
     Memory: 33.8M
     CGroup: /system.slice/nordvpnd.service
             └─29011 /usr/sbin/nordvpnd

Dec 06 04:31:43 xps3 systemd[1]: Started NordVPN Daemon.
# systemctl status nordvpnd.socket
● nordvpnd.socket - NordVPN Daemon Socket
     Loaded: loaded (/usr/lib/systemd/system/nordvpnd.socket; disabled; vendor preset: disabled)
     Active: active (running) since Fri 2019-12-06 04:31:43 MST; 11min ago
   Triggers: ● nordvpnd.service
     Listen: /run/nordvpnd.sock (Stream)
     CGroup: /system.slice/nordvpnd.socket

Dec 06 04:31:43 xps3 systemd[1]: Stopping NordVPN Daemon Socket.
Dec 06 04:31:43 xps3 systemd[1]: nordvpnd.socket: TCP_NODELAY failed: Operation not supported
Dec 06 04:31:43 xps3 systemd[1]: Listening on NordVPN Daemon Socket.

doctorcolossus commented on 2019-12-04 09:10 (UTC)

@archnix: It may work for you, but it does not work for me, in spite of restarting.

$ nordvpn login
Whoops! Cannot reach System Daemon.

root-nix commented on 2019-12-04 08:22 (UTC) (edited on 2019-12-04 08:25 (UTC) by root-nix)

@Klodep @doctorcolossus

Nordvpn works without issues. At least if your remember that network depends on kernel - so if you updated kernel - restart. If you update nordvpn - stop the daemon - update - start daemon.

Previous versions of Nordvpn did change rapidly between nordvpnd - nordvpnud and nordvpnsd services. The nordvpnsd service is a leftover.

If your resolver is cluttered - it is probably the installed gui. If you use nordvpn as it is supposed to - on CLI - there is no problems.

Nordvpn - using TCP or UDP is problematic if you are using UFW iptables based firewall - ditch it and use firewalld instead.

On Manjaro forum is guide to troubleshooting nordvpn including complete removal.

Klodep commented on 2019-12-03 02:29 (UTC)

I have resolved the problem. I just add this line in /etc/resolv.conf [code]nameserver[/code] and all is now working correctly whith my Wifi It is the server that nordvpn use to resolve DNS (I think) But, however, i don't know if i will re-install nodrvpn-bin.

For more information see this post on the Arch-forum


doctorcolossus commented on 2019-12-02 17:54 (UTC) (edited on 2019-12-02 17:59 (UTC) by doctorcolossus)

@archnix: Thanks, but I have already tried restarting many times. Every time I still get "Whoops! Cannot reach System Daemon." Any other ideas?

root-nix commented on 2019-12-02 09:58 (UTC) (edited on 2019-12-02 09:59 (UTC) by root-nix)

@Klodep If you have a nordvpnsd service - uninstall the app - remove the nordvpnsd service file manually if not removed. Rebuild the package.

@doctorcolossus Restart your system - usually this is due to updated system files. Sometimes it is enough to restart the daemon.

Klodep commented on 2019-12-02 02:32 (UTC)

I have the same problem since i have install nordvpn-bin I was not able to connect to NordVPN with my account and my password and i have realised also that my computer was not able to resolve anyone DNS on Firefox and also whith a ping command. The connection is ok but impossible to reach a web site The deamond nordvpnd.service was start and enable but nothing was working for the web. I have remove NordVPN on my computer and the problem was not resolve. I can't acces to the WEB. After to have removed nordvpn from my computer i have checked my service with this command : systemctl list-unit-files --type=service --all nordvpnd.service was disapeared but i saw this one : nordvpnsd.service disabled

I don't now which pakage to remove to delete this service.

doctorcolossus commented on 2019-12-02 00:55 (UTC) (edited on 2019-12-02 00:57 (UTC) by doctorcolossus)

I am experiencing the same problem that many here have reported:

$ nordvpn login
Whoops! Cannot reach System Daemon.

However, I did remember to enable and start nordvpnd, as the output of "systemctl status nordvpnd" shows:

● nordvpnd.service - NordVPN Daemon
   Loaded: loaded (/usr/lib/systemd/system/nordvpnd.service; enabled; vendor preset: disabled)
   Active: active (running) since Sun 2019-12-01 16:47:30 MST; 57s ago
 Main PID: 96036 (nordvpnd)
    Tasks: 14 (limit: 19034)
   Memory: 61.1M
   CGroup: /system.slice/nordvpnd.service
           └─96036 /usr/sbin/nordvpnd

Has anyone figured out how to resolve this? Thanks...

doczico commented on 2019-11-24 18:00 (UTC)

Hello, when i set nordlynx as technology i cannot ping nor resolve anything Can someone help me please ?

ping ping: Temporary failure in name resolution ping PING ( 56(84) bytes of data. ping: sendmsg: Operation not permitted

i'm on armv7l

Thanks a lot

robotdna commented on 2019-11-21 17:05 (UTC) (edited on 2019-11-21 17:08 (UTC) by robotdna)

@Kodep This has happened to me before. The files are immutable, and you can easily change this using:

sudo chattr -i file

So, something like this:

sudo chattr -i /var/lib/nordvpn/data/insights.dat 


sudo chattr -i /var/lib/nordvpn/data/servers.dat

The +i flag makes a file read-only in case you are curious.

Klodep commented on 2019-11-21 16:58 (UTC)

I have updated based-devil. I have installed YAY and used it to install nordvpn-bin. My problem wiht libalpm seem resolve. But i have some problems with two files when i try to install nordvpn with YAY. I have received theses messages:

nordvpn-bin : /var/lib/nordvpn/data/insights.dat already exist in the file system nordvpn-bin : /var/lib/nordvpn/data/servers.dat already exist in the file system. YAY don't have installed nordvpn To be able to delete them, I have tried to change all permissions on these files with these commands :

sudo chmod a=rwx /var/lib/nordvpn/data/servers.dat sudo chmod a=rwx /var/lib/nordvpn/data/insights.dat

But these operations are not autorised by the system.

jackhistoria commented on 2019-11-21 08:59 (UTC) (edited on 2019-11-21 09:03 (UTC) by jackhistoria)

@Klodep yaourt is outdated / depricated meaning no longer active developed. ( I use yay (yet another yaourt) and it works fine and also get the nordvpn-bin working fine. (

Just in your case if libalpm is missing, it should be in the "yayourt -S base-devel" or "yay libalpm" and than base-devel. (You should install base-devel on every arch system for basic stuff if you plan on compiling software from the [[AUR]] Have fun :) (

root-nix commented on 2019-11-21 08:05 (UTC)

@Klodep Update your system Clone the PKGBUILD and build using makepkg

Klodep commented on 2019-11-21 01:53 (UTC)

I receive this message when I try to download this package on Arch-Linux

sudo yaourt -S nordvpn-bin package-query: error while loading shared libraries: cannot open shared object file: No such file or directory package-query: error while loading shared libraries: cannot open shared object file: No such file or directory

ruffy commented on 2019-10-29 14:17 (UTC)

Why does connecting and disconnecting takes so long since the last two udates?

backflash commented on 2019-10-09 14:51 (UTC)

Nordvpn has a bash completion implemented. Maybe the maintainer of this package could add "bash-completion" package as an optional dependency and add a script to PKGBUILD to move it from ${pkgdir}/usr/share/bash-completion/completions/nordvpn to /usr/share/bash-completion/completions/nordvpn?

shaybox commented on 2019-10-07 22:34 (UTC)

Just a tip for the future, although this is a binary package, since there's no source version or source to make one, you wouldn't include that in the name

xerx3w commented on 2019-10-02 13:04 (UTC)

@tito480 maybe you're trying to enable obfuscation while on nordlynx? AFAIK wireguard (or nordlynx as they call it) has no obfuscation.

tito480 commented on 2019-09-30 02:32 (UTC)

@robotdna Still no luck, thanks anyway for the help.

robotdna commented on 2019-09-30 02:00 (UTC)

@tito480 I am able to enable and connect to obfuscate servers. Since this AUR package is just a wrapping for the provided NordVPN .deb client, my suggestion would first be to open the PKGBUILD and look at how the .deb from NordVPN is installed and try this set of commands manually, using the downloaded .deb from their website. If 'obfuscate' still does not work, then you can isolate the issue to their client itself and contact their support at

tito480 commented on 2019-09-30 01:42 (UTC)

@robotdna. Same error: Command 'obfuscate enable' doesn't exist.

I think there is no "obfuscate" command on this package.

robotdna commented on 2019-09-30 00:16 (UTC)

@tito480 Try: nordvpn set obfuscate enable

tito480 commented on 2019-09-29 23:34 (UTC)

I think Obfuscate is not working:

nordvpn set obfuscate 1 Command 'obfuscate 1' doesn't exist.

mikael2933 commented on 2019-09-20 10:49 (UTC)

@alogim The kill-switch only works after you are connected to a server. After you connect to a server it will apply the iptables, and only then if you lose internet, will it be blocked.

root-nix commented on 2019-09-17 07:35 (UTC)

@alogim The package is a repack of the official app. As nordvpn is a paid service - you should use their bugtracker/forum/issues platform to report it.

alogim commented on 2019-09-17 06:52 (UTC)

I noticed that even though KillSwitch is enabled, still I can browse the Internet without problems when NordVPN is not connected. My current settings: Technology: OpenVPN Protocol: TCP Kill Switch: enabled CyberSec: disabled Obfuscate: disabled Notify: enabled Auto-connect: enabled DNS: disabled

Is there any fix?

esdaniel commented on 2019-08-30 21:57 (UTC)

@Martoko / @erkexzcx, thank you for collaborating together to help improve this package. Well done!

erkexzcx commented on 2019-08-28 14:07 (UTC) (edited on 2019-08-28 14:17 (UTC) by erkexzcx)

@Martoko here is the list:

amd64 = x86_64
arm64 = aarch64
armel = arm & armv6h
armhf = armv7h
i386 = i686

Also feel free to use my written in Go app to generate PKGBUILD:

sudo pacman -S go
go get
wget -O app.go
go build app.go

Also, I would like to share my computing power to schedule automated script to update this AUR package. Let me know if needed.

EDIT: My bad, in the golang code I accidentally left nordvpn-cli rather than nordvpn-bin. Change before compiling.

Martoko commented on 2019-08-28 12:58 (UTC) (edited on 2019-08-28 12:58 (UTC) by Martoko)

I have updated the package.

The mapping between how Debian names arm architectures and how Arch Linux names arm architectures does not seem to be documented anywhere, so I made a few qualified guesses here:

armel -> armv6h
armhf -> armv7h
arm64 -> aarch64

If anyone can confirm or deny the above mappings, it would be most appreciated.

robotdna commented on 2019-08-28 01:55 (UTC) (edited on 2019-08-28 02:09 (UTC) by robotdna)

Is it possible to update this to 1.0.0? Thank you!

disastro commented on 2019-08-27 16:43 (UTC)

@erkexzcx For the moment, no options. If the package is actually unmaintained, adopting it. If the maintainer updates and somehow outright refuses to include armv6, MAYBE nordvpn-armv6 but I'm not a TU and have little to none knowledge about a case like this, so I would discuss it with a TU beforehand ESPECIALLY given your past. In most cases you'd probably just live with it and makepkg -A but I know it doesn't work for this exact package. Using a local PKGBUILD is always an option.

erkexzcx commented on 2019-08-27 16:38 (UTC)

@disastro - If I would like to contribute to the community and create Arch Linux package for NordVPN armv6 architecture, what options do I have? Just asking, no offense.

disastro commented on 2019-08-27 16:07 (UTC)

@Jessie Your note seems to grossly be based on baseless claims by erkexzcx. When the package was flagged on the 12th it wasn't out of date. 3.3.1 has only been out since the 19th and the package has only been correctly flagged since yesterday. All architechtures beyond x86_64 are extra, if a maintainer wants to add them they can do so at their own will and pace. That said it's fine to create a personal PKGBUILD, that's what I do with a lot of packages, but bashing the maintainer with or without reason isn't nice.

commented on 2019-08-27 14:38 (UTC)

I wrote a note and corresponding shell script to update it by hand. The script is based on this PKGBUILD file.

polyzen commented on 2019-08-26 19:48 (UTC)

Please rename this package to just nordvpn, unless there is source code available to be built.

erkexzcx commented on 2019-08-24 16:54 (UTC) (edited on 2019-08-27 05:50 (UTC) by erkexzcx)

nordvpn-bin AUR package maintainers have a python script, but they don't use it (no scheduled cronjobs etc...). I asked to make me a maintainer - they didn't. I asked to include missing architecture - they didn't.

Trusted users (known as moderators of AUR) has declined any help from me - I already created automated script to fix all issues of this package, but got rejected. Created alternative AUR packages with it, yet got removed by them. I flagged this package as out of date on 2019-08-12, but one of TUs has unflagged it, yet package has been outdated since then. And I also got AUR account suspension threats from them.

So basically when package is very popular among users and been outdated for like 2 weeks already - it's fine. When it misses few unofficial architectures - it's also fine.

commented on 2019-08-24 09:21 (UTC)

Hi, keeps nagging me to update the client. Any chance of updating this to "nordvpn_3.3.1-1_arm64.deb"? thanks for your work

stecampanella commented on 2019-08-20 07:29 (UTC)

@esdaniel Actually no, I didn't find a fix. The autostart functionality is very fragile and from time to time it stops working.

esdaniel commented on 2019-08-18 15:38 (UTC)

sfncmp1729: RE: autoconnect, me2 :-( Did you find a fix? I resorted to autostart script until 'we' can resolve this.

lotan_rm commented on 2019-08-14 19:29 (UTC)

Could you please add awk to the list of dependencies?

MarcoBuster commented on 2019-08-14 13:12 (UTC)

When I try to connect I see this message: "transport is closing". On my laptop it works fine, but on my Raspberry it doesn't. The daemon is up and running. Thx

erkexzcx commented on 2019-08-12 10:32 (UTC)

Add missing armel architecture. It's for RPI1 and RPI zero devices (devices with armv6 architecture).

It's also provided by NordVPN:

cobaltspace commented on 2019-08-09 23:48 (UTC)

Please replace wireguard-arch with WIREGUARD-MODULE, as this is provided by wireguard-arch, wireguard-lts, and wireguard-dkms

erkexzcx commented on 2019-08-09 16:15 (UTC)

Add missing armel architecture. It's for RPI1 and RPI zero devices (devices with armv6 architecture).

It's also provided by NordVPN:

stecampanella commented on 2019-08-07 20:55 (UTC) (edited on 2019-08-08 06:00 (UTC) by stecampanella)

Anyone else having problems with autoconnect? Any hint on how to solve this issue? Also, I suspect that the killswitch is not working as it should. For example, if I disconnect from nordvpn after a while my downloads resume.

JRO012 commented on 2019-08-03 12:04 (UTC)

@Martoko That link resolved my issue. If anyone else has the problem, I was needed to install linux headers and select my kernel.

sudo pacman -S linux-headers


Martoko commented on 2019-08-03 11:39 (UTC)

@JRO012 I do not have Manjaro installation right now, but a quick Google search revealed the following pages of interest Arch Linux wiki on WireGuard, Blog post detailing how to install WireGuard for Manjaro

@erkexzcx "we" are not refusing anything. Metiis is the one with the power to make you a maintainer, and AFAIK he is not even aware of your comments.

We welcome any suggestions on how to update the PKGBUILD. Examples include jackhistoria's suggestion of adding WireGuard as a dependency and your suggestion of creating a script to automatically update. Both suggestions have been implemented.

In the future, please refrain from general statements, such as "they don't even know how to maintain this", and instead highlight specific issues, such as "why isn't wireguard added as a dependency".

erkexzcx commented on 2019-08-03 11:12 (UTC)

@JRO012 they don't even know how to maintain this. It was described by NORDVPN about new requirwd dependencies of new release, but they refuse to help me update this PKGBUILD.

JRO012 commented on 2019-08-03 10:38 (UTC)

Very new to all this and I have an error. When I try to Nordvpn set technology NordLynx, I get "Missing NordLynx kernel module or configuration utility." I have wireguard-dkms and wireguard-tools installed. Any help is appreciated (also if this isn't the place to request help, let me know and I'll delete this post).

Dell XPS 13 9360 Operating System: Manjaro Linux Kernel: Linux 4.19.62-1-MANJARO Architecture: x86-64

Martoko commented on 2019-08-02 22:11 (UTC)

@erkexzcx what I meant to say was that I am a co-maintainer. I have written a script like you talked about and I have set it to run daily. If I have missed anything in my script feel free to make a pull request, otherwise the problem of the package being constantly out of date because of minor changes should be fixed now. Thank you for offering your help.

erkexzcx commented on 2019-08-02 21:12 (UTC)

@Martoko i am not doing anythink by now. First I would like to be a maintainer, otherwise spending time would be useless.

Martoko commented on 2019-08-02 20:35 (UTC)

@erkexzcx I can't make you a maintainer (AFAIK only metiis can), but here is a script that I've written Martoko/maintain-nordvpn-bin, feel free to make a pull request with improvements or suggestions.

esdaniel commented on 2019-08-02 16:50 (UTC)

Thanks for the tip, jackhistoria.

FYI anyone curious about the wireguard stuff on previous post, see here:

Follow these steps to switch to NordLynx: Install WireGuard. Open the terminal and enter ‘nordvpn set technology NordLynx’. Enter ‘nordvpn c’ to connect to VPN.

jackhistoria commented on 2019-08-02 13:03 (UTC)

@metiis: please add: wireguard-tools wireguard-arch since the nordlynx technology is now included in the app that needs that packages to work properly. ( NordLynx works like charm for me now after adding wireguard. (sudo pacman -S wireguard-tools wireguard-arch) Maybe disable cyberSec in the settings)

It is under heavy development regarding that and has new versions sometimes twice a day: (

stecampanella commented on 2019-08-01 20:50 (UTC)

Auto-connect not working on my system. nordvpn connect working though.

erkexzcx commented on 2019-08-01 16:08 (UTC)

Can you make me a maintainer please? It's ALREADY OUTDATED...

root-nix commented on 2019-08-01 12:25 (UTC)


I have been experimenting and I am not sure my assumptions is entirely correct.

I now believe it to be undesireable behavior of the official client.

All my notes are on the Manjaro forum

viking777 commented on 2019-08-01 10:43 (UTC)

@fhdk Thanks for the reply, I am sure you are correct in your assumptions re this program and ufw, but I don't think that excuses the fact that this happens without any warnings. If I see a program that deliberately disables my firewall, doesn't tell me, and then fails to re-enable it, then I instantly think 'malware'. Now I know this program is not malware, and certainly don't blame the maintainer for anything, he has just inherited this behaviour due to poor coding in from the nord original - it exhibits the same behaviour on debian based distros btw. I don't use Windows, but my wife does, and she also uses Nord and her software firewall doesn't get disconnected every time she connects, so it must be possible.

As to workrounds, I don't use autoconnect, so thankfully, I don't have to mess with the impenetrability of systemd. I use the simple but effective expedient of "nordvpn -c ** && sudo ufw enable" from the terminal, in case anyone else looking for a quick way around it.

jackhistoria commented on 2019-07-31 14:56 (UTC)

Is there a system im place to update the deb url since there is the version 3.3 out there and the repo outdated or how can i support you guys?

esdaniel commented on 2019-07-31 11:04 (UTC) (edited on 2019-07-31 11:05 (UTC) by esdaniel)

Hi @erkexzcx, ahead of a 'poltical' decision regarding the maintainers adding you as a maintainer perhaps fast-track approach to merit maintaining here too [not necessary given your activity elsewhere on AUR but... ;-)] would be to share a link to your proposed build scripts to be used, or start a new AUR package. Just my 2c.

erkexzcx commented on 2019-07-31 10:38 (UTC)

Can you make me a maintainer, please? I'd like to setup automated script to update this package.

erkexzcx commented on 2019-07-27 08:13 (UTC)

Hey. Add missing armel architecture. It's for RPI1 and RPI zero devices (devices with armv6 architecture).

It's also provided by NordVPN:

root-nix commented on 2019-07-25 08:22 (UTC)

@viking777 @typicallinuxuser

I am by no means a guru on connections and ufw but I do think that ufw is disabled because of the routing changes.

If the nordvpnd did not disable the ufw, the iptables generated by ufw would be blocking the traffic from the connected server as your nic changes address, dns and gateway.

If you are directly connected to a public a ip (most users connect through a firewalled routing device) then you are well served by a local firewall.

If you realle need firewall, you can create a systemd service to react on your network change to reenable ufw after nordvpnd has created the tunnel.

ZAKhan commented on 2019-07-25 06:20 (UTC)

does not work for me at all .. removed everything and reinstalled but still the same error

Whoops! Connection failed. Please try again. If the problem persists, contact our customer support.

viking777 commented on 2019-07-22 15:29 (UTC)

@typicallinuxuser I have noticed exactly the same ufw problem on Manjaro Linux - so it is not just you. Don't know what to do about it though except restart ufw every time I connect to a nordvpn server.

typicallinuxuser commented on 2019-07-21 18:06 (UTC)

I'm now noticing anytime I connect with nordvpn c my ufw becomes inactive and will not enable on startup. I can activate it manually and all is well, and will remain active if I nordvpn d but then becomes inactive again any time I connect with nordvpn c.

Using nordvpn-bin version 3.2.0-4

ZAKhan commented on 2019-07-21 03:27 (UTC)

@typicallinuxuser no such file or directory

chattr -i /var/lib/nordvpn/data/.config.ovpn

typicallinuxuser commented on 2019-07-20 11:37 (UTC) (edited on 2019-07-20 11:38 (UTC) by typicallinuxuser)

@ajgraves thank you. chattr -i /var/lib/nordvpn/data/.config.ovpn fixed my issue without having to reinstall the snapshot. Works as intended, version 3.2.0-4.

ZAKhan commented on 2019-07-20 04:08 (UTC) (edited on 2019-07-21 03:26 (UTC) by ZAKhan)

the version has changed now its 1.0 again ..

ZAKhan commented on 2019-07-20 04:05 (UTC)

after removing /var/lib/nordvpn , it still does not work

ajgraves commented on 2019-07-19 12:11 (UTC)

@typicallinuxuser the reason you can’t delete even as root is because there is a file in that directory with the immutable bit set. I can’t recall off the top of my head which but if you’ve already attempted to delete the folder it should be the only file left inside that folder. You can verify it is set by using the lsattr command. To remove the bit, as root run chattr -i followed by the name of the file. You’ll then be able to completely delete the directory.

typicallinuxuser commented on 2019-07-19 11:53 (UTC) (edited on 2019-07-19 11:54 (UTC) by typicallinuxuser)

I have also been getting the error message: Whoops! Connection failed. Please try again. If the problem persists, contact our customer support.

Running systemctl status nordvpnd there seems to be a restriction accessing the following path:

Jul 19 07:35:56 primary systemd[1]: Started NordVPN Daemon.

Jul 19 07:37:12 primary nordvpnd[530]: 2019/07/19 07:37:12 open /var/lib/nordvpn/data/.config.ovpn: operation not permitted

Each time I try to connect with nordvpn c another error is appended to systemctl status.

I tried to completely uninstall and remove all system files like ajgraves recommended for a different issue and I could not delete, even when logged in as su, /var/lib/nordvpn .

Version: 3.2.0-4

ZAKhan commented on 2019-07-19 09:43 (UTC)

started getting an error

"Whoops! Connection failed. Please try again. If the problem persists, contact our customer support."

reinstalled but still giving an error.

kuluse commented on 2019-07-14 18:08 (UTC)

I have the same problem and couldn't solve it, I use networkmanager and ufw as killswitch now. I wrote this on the archwiki :

ajgraves commented on 2019-07-09 18:47 (UTC) (edited on 2019-07-10 23:14 (UTC) by ajgraves)

@sfranchi I had issues too, and I literally had to remove any reference of nordvpn anywhere from my system. As root, type "find / -name nord*" and see what it spits out. There were many locations where nord had leftovers on my system. I removed every directory, old systemd definition, etc I could find anywhere. I then restarted, and re-installed. It appears to be working for me now.

sfranchi commented on 2019-07-09 14:48 (UTC)

I have the same issue as Archanfel80HUN , but removing the app + config dir and reinstalling did not solve the issue. S

Archanfel80HUN commented on 2019-07-09 09:49 (UTC) (edited on 2019-07-09 11:31 (UTC) by Archanfel80HUN)

After the upgrade i got this: parsing time "" as "2006-01-02 15:04:05": cannot parse "" as "2006"

Any help?

SOLVED: fully removed the app, deleted the config directory and the systemd service, reinstall and it works now.

archifer commented on 2019-07-06 20:20 (UTC) (edited on 2019-07-06 20:22 (UTC) by archifer)

@s339 I had this issue I solved it by completely removing the package then restart the system and install it fresh. After that:

$ sudo systemctl enable nordvpnd.service

$ sudo systemctl start nordvpnd.service

And it got back to normal.

s339 commented on 2019-06-13 10:24 (UTC) (edited on 2019-06-13 10:24 (UTC) by s339)

@przemub I seem to be having a similar problem to @cipley. Output of systemctl status nordvpndis:

$ systemctl status nordvpnd * nordvpnd.service - NordVPN Daemon Loaded: loaded (/usr/lib/systemd/system/nordvpnd.service; enabled; vendor preset: disabled) Active: activating (auto-restart) (Result: exit-code) since Thu 2019-06-13 12:19:41 CEST; 1s ago Process: 8458 ExecStart=/usr/sbin/nordvpnd (code=exited, status=203/EXEC) Main PID: 8458 (code=exited, status=203/EXEC)

Output of systemd-cgls | grep nord is:

$ systemd-cgls | grep nord | | |-nordvpnud.service | | |-763 /usr/sbin/nordvpnud | -8067 grep --color=auto nord |-nordvpnsd.service |-641 /usr/sbin/nordvpnsd`

The error I get from the recent update is:

$ nordvpn c Whoops! Cannot reach System Daemon.

Any clues? I'm at a loss as to what's going on here. Removing and reinstalling doesn't help.

przemub commented on 2019-06-12 16:22 (UTC)


Restart the system. (If you have installed a new kernel version simultaneously, it might have caused the problem.)

If it's not that, paste the result of command systemctl status nordvpnd.

root-nix commented on 2019-06-06 08:53 (UTC) (edited on 2019-06-06 09:05 (UTC) by root-nix)

Removed - another change with 3.1

mudrii commented on 2019-06-05 07:27 (UTC) (edited on 2019-06-05 07:45 (UTC) by mudrii)

After latest updated to version nordvpn-bin 3.1.0_4-1 and after fixing startup issue with Daemon now I can't make nordvpn to connect and getting below error. Is anybody else have the same issue?

We're having trouble configuring your DNS settings. If the issue persists, please contact our customer support

For now, I managed to connect using openvpn.

EDIT: Seems issue is with systemd-resolved service that manages /etc/resolv.cong and needs to be stopped 1st before connecting to nordvpn

ABOhiccups commented on 2019-06-05 02:32 (UTC) (edited on 2019-06-05 02:36 (UTC) by ABOhiccups)

After a new update. I get this error message.

Whoops! Cannot reach System Daemon.

Edit: You have to open Terminal and enter this command.

sudo systemctl enable nordvpnd.service

cipley commented on 2019-05-23 19:03 (UTC)

I can't seem to connect to nordvpn.

The last successful command was login. Then, anything else yields this:

Whoops! Something went wrong. Please try again. If the problem persists, contact our customer support.

colearrington commented on 2019-05-21 16:03 (UTC) (edited on 2019-05-21 16:03 (UTC) by colearrington)

@Ubermensch - I ran into the same issue (on GalliumOS in my case), and ultimately just uninstalled and reinstalled via apt. Some of the non-reinstallation options have worked in the past but this time around seemed to require the reinstall

Ubermensch commented on 2019-05-15 08:59 (UTC)

I report frequently "Whoops! Cannot reach User Daemon." error message when i use nordvpn command. Removing ~/.config/nordvpn/ don't fix it

aleksz commented on 2019-05-13 01:45 (UTC)

I get the issue "systemclt" is the alias of "sudo systemctl" in Antergos linux.

NygelLyndley commented on 2019-05-11 11:57 (UTC) (edited on 2019-05-12 19:10 (UTC) by NygelLyndley)

Anyone else having issue whitelisting ports for access on the local lan?

nordvpn whitelist add port 1234

transport is closing or Whoops! Cannot reach User Daemon.

Both nordvpnsd and nordvpnud are showing as running.

EDIT: fixed by removing ~/.config/nordvpn/ and reconfiguring.

rendekarf commented on 2019-05-04 20:39 (UTC) (edited on 2019-05-04 20:40 (UTC) by rendekarf)

Hey everyone! For some reason outgoing traffic halts when I connect to a server:

  • I login with my credentials: Welcome to NordVPN! You can now connect to VPN by using 'nordvpn connect'.
  • nordvpn c ireland dublin: Connecting to Ireland #21 ( You are connected to Ireland #21 (!
  • ping returns nothing, my connection goes down.

I checked the service logs (through journalctl), looks ok. Only a couple of lines that say "kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized" but after a quick search on google it seems to be unrelated.

Any ideas?


Manjaro 18.0.4

Kernel 4.14.93-rt53-MANJARO

NordVPN Version 3.0.0-4

ynlieding commented on 2019-05-04 08:43 (UTC) (edited on 2019-05-04 13:04 (UTC) by ynlieding)

I can't uninstall nord-vpn package

# pacman -Rcns nordvpn-bin 
checking dependencies...
:: inxi optionally requires net-tools: inxi -i ip lan-deprecated

Packages (2) net-tools-1.60.20180212git-1  nordvpn-bin-3.0.0_4-1

Total Removed Size:  38.48 MiB

:: Do you want to remove these packages? [Y/n] 
:: Processing package changes...
error: cannot remove file '/var/lib/nordvpn/data/insights.dat': Operation not permitted
(2/2) removing net-tools                                             [######################################] 100%
:: Running post-transaction hooks...
(1/2) Reloading system manager configuration...
(2/2) Arming ConditionNeedsUpdate...

Upd. chattr -i /var/lib/nordvpn/data/insights.dat; chattr -i /var/lib/nordvpn/data/servers.dat did the trick

washo commented on 2019-05-02 19:37 (UTC) (edited on 2019-05-02 19:37 (UTC) by washo)

Apparently the killswitch does not work at all in my case. It does not cut the internet connection when disconnected. I'm using Antergos linux. Any idea?

stavrakis commented on 2019-04-27 19:41 (UTC)

How can we choose between countries normal/P2P/Double/TOR? When I try to connect to Netherlands it picks the onion server by itself. Also, the man page says something about groups. What is that? I cannot find any reference to groups, apart from the 3 examples in the man page.

Changaco commented on 2019-04-24 12:51 (UTC) (edited on 2019-04-29 07:20 (UTC) by Changaco)

Warning: the systemd unit files included in this package give NordVPN full access to your entire system. Adding sandboxing options in the [Service] section of each systemd service file can reduce the security risks.

For example the following options can be added in nordvpnsd.service:

ReadWritePaths=/var/lib/nordvpn /var/log/nordvpn

See man systemd.exec for details.

washo commented on 2019-04-23 21:17 (UTC)

I love you so much guys. I did what @RidderJoris mentions and then entered all the commands without "sudo". It worked perfectly. Happy days!

hahnt9009 commented on 2019-04-23 00:45 (UTC)

WOW! @RidderJoris, you are absolutely right, I didn't even think to check there. It's strange indeed that Antergos aliases systemctl >_> but you are absolutely right, that did the trick thanks so much!

RidderJoris commented on 2019-04-22 19:52 (UTC) (edited on 2019-04-23 08:47 (UTC) by RidderJoris)

@hahnt9009 I found the issue. In Antergos linux "systemclt" is the alias of "sudo systemctl" which makes no sense to me. Therefore if you comment the line "alias systemctl='sudo systemctl'" in ".bashrc.aliases" it will work fine ;)

washo commented on 2019-04-22 19:43 (UTC)

I had the same issue that @RidderJoris and @hahnt9009 are reporting.

"Failed to connect to bus: No such file or directory" when using systemctl --user enable --now nordvpnud.

When using nordvpn status I receive Whoops! Cannot reach User Daemon.

I'm also using Antergos linux.

SZJX commented on 2019-04-22 15:08 (UTC) (edited on 2019-04-22 15:09 (UTC) by SZJX)

First I had to sudo rm /var/lib/nordvpn/data before the update could get through.

Then, after running

sudo systemctl enable --now nordvpnsd
systemctl --user enable --now nordvpnud

I ran nordvpn connect (without sudo), and it worked.

hahnt9009 commented on 2019-04-22 13:38 (UTC)

@Ridder Joris Interesting; I as well, am on Antergos. I recently had my wife (also an Antergos user) attempt to update. She is now experiencing the issue. So it appears it may be Antergos related? I'll look into openpyn-nordvpn as well thanks. Will keep attempting to research this more and keep up with any updates on nordvpn-bin, feel a bit lost without it!

RidderJoris commented on 2019-04-22 09:56 (UTC) (edited on 2019-04-22 10:06 (UTC) by RidderJoris)

@Martoko I am running Antergos Linux. Your commands printed the following:

 (base) [joris@B250M ~]$ sudo systemctl status nordvpnsd.service
 ● nordvpnsd.service - NordVPN System Daemon
    Loaded: loaded (/usr/lib/systemd/system/nordvpnsd.service; enabled; vendor p>
    Active: active (running) since Mon 2019-04-22 11:53:43 CEST; 2min 6s ago
  Main PID: 1794 (nordvpnsd)
     Tasks: 13 (limit: 4915)
    Memory: 61.2M
    CGroup: /system.slice/nordvpnsd.service
            └─1794 /usr/sbin/nordvpnsd

 Apr 22 11:53:43 B250M systemd[1]: Started NordVPN System Daemon.

 (base) [joris@B250M ~]$ systemctl --user status nordvpnud.service
 Failed to connect to bus: No such file or directory
 (base) [joris@B250M ~]$ ls /usr/lib/systemd/user/ | grep nordvpn

RidderJoris commented on 2019-04-22 09:46 (UTC) (edited on 2019-04-22 09:48 (UTC) by RidderJoris)

@hahnt9009 I have the same issue. I am running Antergos Linux btw. I am now using openpyn-nordvpn instead waiting for an update on this issue.

hahnt9009 commented on 2019-04-21 15:03 (UTC)

@Martoko, Thanks for the reply. The outputs are as follows

nordvpnsd.service - NordVPN System Daemon Loaded: loaded (/usr/lib/systemd/system/nordvpnsd.service; enabled; vendor preset: disabled) Active: active (running) since Sun 2019-04-21 07:26:02 PDT; 30min ago Main PID: 695 (nordvpnsd) Tasks: 22 (limit: 4915) Memory: 40.2M CGroup: /system.slice/nordvpnsd.service └─695 /usr/sbin/nordvpnsd

Apr 21 07:26:02 antergos-desktop systemd[1]: Started NordVPN System Daemon.

Failed to connect to bus: No such file or directory

nordvpnud.service nordvpnud.socket

in respective order to commands as you listed them.

Martoko commented on 2019-04-21 11:23 (UTC) (edited on 2019-04-21 11:24 (UTC) by Martoko)

@hahnt9009 I am not sure what the problem is by just looking at the error message.
What do you get when you run each of these commands?

sudo systemctl status nordvpnsd.service
systemctl --user status nordvpnud.service
ls /usr/lib/systemd/user/ | grep nordvpn

hahnt9009 commented on 2019-04-20 16:49 (UTC) (edited on 2019-04-20 19:01 (UTC) by hahnt9009)

After version 3.0.0 update, I attempted to run the req'd services sudo systemctl enable --now nordvpnsd systemctl --user enable --now nordvpnud

the system daemon worked fine, however the user daemon returned error "Failed to connect to bus: No such file or directory". It appears the nordvpnud service did not get installed. Anyone else have this issue?

archieslove commented on 2019-04-19 22:35 (UTC) (edited on 2019-04-19 23:13 (UTC) by archieslove)

Is the port whitelist working for any of you guys after the resent update ? It just shows me 'Transport is closing'

Edit - Contacted the support and it seems they're working on a fix already. Wew

Martoko commented on 2019-04-19 08:48 (UTC) (edited on 2019-04-23 01:44 (UTC) by Martoko)

After version 3.0.0 there are now two systemd services you need to start:

sudo systemctl enable --now nordvpnsd
systemctl --user enable --now nordvpnud

If you are using Antergos then please be aware that systemctl is by default aliased to sudo systemctl in .bashrc.aliases. You might want to comment out the line alias systemctl='sudo systemctl' to disable the alias.

dapolinario commented on 2019-04-19 06:38 (UTC)

You will probably need to reconfigure the nordvpn. Look at the output of systemctl status nordvpnd after attempting to run the daemon.

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 ''. 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 ?

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

ncage commented on 2019-02-08 23:09 (UTC)

Does anyone know if here is anyway to give nordvpn login either command line arguments or a dotfile where you can specify credentials?. I would just like to type 'nordvpn login' and not be asked for creds.

Thornycrackers commented on 2019-02-03 23:36 (UTC)

@swiftscythe I had that exact error too. I originally had the error from not having the systemd daemon enabled so I ran:

sudo systemctl enable --now nordvpnd

After that I started getting the error message you were describing so I restarted my computer and then everything worked after that.

swiftscythe commented on 2019-01-19 15:15 (UTC)

I'm getting this error when trying to connect:

Exiting due to fatal error: ERROR: Cannot open TUN/TAP dev /dev/net/tun: No such file or directory (errno=2)

Any ideas? It used to work properly last week.

szybia commented on 2019-01-12 09:52 (UTC)

If you have started the service but still getting this error then just reboot your machine. Worked for me.

rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial unix /run/nordvpn.sock: connect: no such file or directory"

Martoko commented on 2019-01-12 07:54 (UTC)

For some reason the error message got uglier, but the gist of it is the same. Have you remembered to start the service?

As metiis said: Please run sudo systemctl enable --now nordvpnd to start it and run it at boot, or sudo systemctl start nordvpnd to only start it once.

ABOhiccups commented on 2019-01-12 05:50 (UTC)

Error while using nordvpn commands.

rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial unix /run/nordvpn.sock: connect: no such file or directory"

Martoko commented on 2019-01-09 23:23 (UTC)

The two files ovpn_template.xlst and ovpn_xor_template.xlst were not previously shipped with the nordvpn-bin package, but created by the application at runtime.

This means pacman does not know to remove them before upgrading.

A quick fix would be to just remove the files before upgrading:

sudo rm /var/lib/nordvpn/{ovpn_template,ovpn_xor_template}.xslt

drose2211 commented on 2019-01-09 20:04 (UTC)

I am receiving this error when updating

error: failed to commit transaction (conflicting files)
nordvpn-bin: /var/lib/nordvpn/ovpn_template.xslt exists in filesystem
Errors occurred, no packages were upgraded.

Martoko commented on 2018-12-23 19:40 (UTC) (edited on 2018-12-23 19:41 (UTC) by Martoko)

Here is a new patch based on bubuntux's version. Also I wouldn't mind being a co-maintainer.


  • remove openvpn dependency as nordvpn ships with their own openvpn binary src
  • add libxlst, iptables and procps as dependencies as they are listed in the deb package as dependencies src
  • update source to 2.1.0_5
  • move systemd files to the proper arch location src
  • add comment with maintainer src

bubuntux commented on 2018-12-03 23:59 (UTC)

Patch to latest version 2.1.0-3

dapolinario commented on 2018-11-28 19:13 (UTC)

The openvpn package is no longer required as a dependency. Now the deb package uses its own openvpn binary (/var/lib/nordvpn/openvpn)

These are the dependencies (according to the control file, inside the deb): Depends: systemd, procps, net-tools, iptables, xsltproc

kgizdov commented on 2018-11-20 11:53 (UTC)

sums check is failing for me

metiis commented on 2018-11-20 11:27 (UTC)

@simokron Then I'll add it later, currently not anywhere near a PC.

vcekron commented on 2018-11-20 11:24 (UTC)

@metiis Yes, works perfectly with net-tools installed.

metiis commented on 2018-11-20 11:20 (UTC)

@simokron Does it work with net-tools installed?

vcekron commented on 2018-11-20 11:11 (UTC) (edited on 2018-11-20 11:20 (UTC) by vcekron)

Thank you @metiis, it is so obvious now that you point it out.

Also, looks like it now depends on the net-tools package?

Without it I get;

[~]$ sudo nordvpn connect se

Connecting to Sweden #203 (

Exiting due to fatal error: Linux ifconfig failed: could not execute external program

metiis commented on 2018-11-20 11:01 (UTC)

If you're seeing the message "Daemon is unreachable, is systemd running?", that means that the nordvpn daemon is not started. Please run "sudo systemctl enable --now nordvpnd" to start it and run it at boot, or "sudo systemctl start nordvpnd" to only start it once.

lenard commented on 2018-11-20 10:46 (UTC)

In version 2.0.0-2 the source nordvpn_2.0.0_amd64.deb fails to validate with sha256sums.

Ubermensch commented on 2018-11-20 10:45 (UTC)

Also for me as simokron same problem :(

vcekron commented on 2018-11-20 08:20 (UTC) (edited on 2018-11-20 08:21 (UTC) by vcekron)

[~]$ sudo nordvpn login

Daemon is unreachable. Is systemd running?

Anyone else seeing this after version 2.0?

simona commented on 2018-11-19 23:01 (UTC)

nordvpn-bin: /usr/sbin exists in filesystem (owned by filesystem)

metiis commented on 2018-11-19 21:16 (UTC)

Sorry for the late update, I had no internet access for the last few weeks. If someone wants to become a co-maintainer, tell me please.

tecnewb commented on 2018-11-11 18:25 (UTC)

same problem here with the config file, deleted it multiple times

SZJX commented on 2018-11-06 11:50 (UTC) (edited on 2018-11-06 11:51 (UTC) by SZJX)

I'm not having any problems with the commands

sudo nordvpn login

sudo nordvpn connect

sudo nordvpn disconnect

What are you supposed to do? Try to debug it a bit more, e.g. deleting the config files and making sure you're using sudo? Contact the customer support? This is a commercial software so why not go and ask the company directly. The packager is not the developer of the software anyways.

lenard commented on 2018-11-06 10:29 (UTC) (edited on 2018-11-06 10:30 (UTC) by lenard)

Current version 1.2.0-3 is broken for me.

When trying to execute any nordvpn command, I get an error message that says: We could not decode the config file("/etc/nordvpn/.nordvpn-config"). Please check that the file exists and we have correct permissions to access it.

This is a serious issue, what are we supposed to do?

Ubermensch commented on 2018-10-29 11:02 (UTC) (edited on 2018-10-29 11:12 (UTC) by Ubermensch)

With the version 1.3.6 there's a problem with permission of ("/home/ubermensch/.config/nordvpn/config")

[code] nordvpn login It seems there's an issue with the config file ("/home/ubermensch/.config/nordvpn/config") permissions. If the issue persists, please contact our customer support. [/code]

Ubermensch commented on 2018-10-29 10:22 (UTC) (edited on 2018-10-29 10:27 (UTC) by Ubermensch)

PKGBUILD for the 1.3.6 version here:

david1975 commented on 2018-10-27 19:57 (UTC)

Hello, I've the same question, I can't connect... Thanks.

korra commented on 2018-10-17 17:44 (UTC) (edited on 2018-10-17 17:45 (UTC) by korra)

Yes, I'm having checksum issues too.

Heziode commented on 2018-10-17 15:17 (UTC) (edited on 2018-10-17 15:17 (UTC) by Heziode)

I have a bad checksum when it check it.

the file is: nordvpn_1.2.0_amd64.deb

expected: 82b11e8dd6e0810282be1322d291cef17a92658cf0438ef702f349370e1e3afa

actual : 386c4e36d42d2d5508d134e5640df9e5aaf7a8fd85fad66b4951296a2f393ff9

Selvadi commented on 2018-10-04 00:05 (UTC) (edited on 2018-10-04 00:09 (UTC) by Selvadi)

Thanks to Ubermensch, with login and connection under sudo it works. I forgot the k.i.s.s. philosophy for a moment. :)

Ubermensch commented on 2018-10-02 09:07 (UTC)

Use "sudo" to fix the problem :)

Selvadi commented on 2018-10-01 23:59 (UTC) (edited on 2018-10-02 00:03 (UTC) by Selvadi)

Hi, i've the same issue of lknix, after nordvpn connet command.

lknix commented on 2018-09-28 19:30 (UTC) (edited on 2018-09-28 19:40 (UTC) by lknix)

@metiis how did you solve this after installing and logging in:

$ nordvpn connect
NordVPN needs access to these files to ensure Your privacy:
Immutability and append-only flags need to be removed from the files above. You can achieve that by running `sudo chattr -ia /path/to/file` for each of them.
Would you like NordVPN to do it for you?[Y/N]

I already have those attributes disabled for both files. It seems nordvpn wants write access to /etc/sysctl.conf and /etc/resolv.conf. Changing file permissions to +rw did the trick. But then I hit:

$ nordvpn connect
It seems there's an issue with the config file ("/etc/nordvpn/nordvpn-config") permissions. If the issue persists, please contact our customer support.
$ ls /etc/nordvpn/nordvpn-config
ls: cannot access '/etc/nordvpn/nordvpn-config': No such file or directory

$ yay -Ql nordvpn-bin | grep config

How did you resolve this?