Arch Linux User Repository

"Please, do not flag this package as out-of-date until there's the official release on Github page."

"Maybe the announcement is delayed, but wait for some other possible forward release, which is patching the previous one before the actual publishing."

Note from 3.17.4v:

The previous bug exposing DNS servers is fixed.

Note from 3.17.3v:

Caution! This version needs heed while using it and should be avoided. I strongly advice downgrading to 3.17.2 and wait for a new version or patching. Some big problems are:

• There's DNS leak present. Your original ISP servers can be exposed, as reported already on #343 issue.

• Unable to connect on nordvpn servers. Your journal might show the follow output: networker setting dns: setting dns with resolvectl: setting dns with resolvectl: Failed to set DNS configuration: Could not activate remote peer: activation request failed: unknown unit.: exit status 1

  After restarting resolve with systemctl restart systemd-resolved.service you may get it working again, enough for connecting normally, as reported, but not exclusively an ARM platform issue, on #342.

Also huge thanks for the community warnings in prior comments before I could've noticed all.

Note from 3.16.2v:

As the published note from the version above has mentioned on Github's page:

• Logging in with a username and password is no longer available in the terminal.

Please, consider using a token to logging in from now on.

Note from 3.16.0v:

The 'countries.dat' may differ between versions. Be aware to remove the file before upgrading the package.

If you're seeing the message "Daemon is unreachable, is systemd running?", then one of two things is probably happening.

The nordvpn daemon might not be started
Start it using:
sudo systemctl enable --now nordvpnd

You might not have been added to the nordvpn group
Add yourself:
sudo gpasswd -a USERNAME nordvpn
And then restart in order for the group to be created:
reboot

@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

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

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

https://pastebin.com/k9sQfa0i

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.

@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.

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.

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"

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.

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"