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

The repository's hierarchy has been updated and a slightly divergence comes with it. It was from:

/debian/pool/main

To now as:

/debian/pool/main/n/nordvpn

Any previous commits you may like to try in the future will need a manual mediation to replace old links in favor of the new ones.

Note from 3.19.0:

This version introduces new libraries being used by NordVPN. I have created symbolic links and committed a patch for it not interposing with already existing libraries (like sqlite3). Although this is not a big deal, If you, however, upgraded nordvpn-bin before the fix and noticed some library-related issue from sqlite lately, I suggest reinstalling the affected package.

Note from 3.17.4v:

The previous bug exposing DNS servers is fixed.

Note from 3.17.3v:

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

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

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

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

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

Note from 3.16.2v:

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

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

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

Note from 3.16.0v:

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

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

@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
 nordvpnud.service
 nordvpnud.socket

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

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

@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

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?

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

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.

You will probably need to reconfigure the nordvpn. Look at the output of systemctl status nordvpnd after attempting to run the daemon.