Package Details: nordlayer 3.0.0-0

Git Clone URL: (read-only, click to copy)
Package Base: nordlayer
Description: Proprietary VPN client for linux
Upstream URL:
Keywords: nordlayer nordvpnteams vpn
Licenses: custom
Conflicts: nordvpnteams-bin
Replaces: nordvpnteams-bin
Submitter: mearaj
Maintainer: sidicer
Last Packager: sidicer
Votes: 6
Popularity: 0.002243
First Submitted: 2022-02-09 21:42 (UTC)
Last Updated: 2023-10-09 10:03 (UTC)

Latest Comments

1 2 Next › Last »

phoenix17 commented on 2024-01-29 20:15 (UTC) (edited on 2024-02-07 14:31 (UTC) by phoenix17)

The strace output shows that the nordlayer-resolvconf process is attempting to execute a setuid(0) system call and is failing with EPERM (Operation not permitted). This indicates that the process is trying to gain root privileges, but it's being denied.

I fixed with:

sudo setcap 'CAP_NET_ADMIN=+eip' /usr/libexec/nordlayer/nordlayer-charon
sudo setcap 'CAP_NET_ADMIN=+eip' /usr/libexec/nordlayer/nordlayer-ip
sudo setcap 'CAP_NET_ADMIN=+eip' /usr/libexec/nordlayer/nordlayer-openvpn
sudo setcap 'CAP_NET_ADMIN+eip CAP_DAC_OVERRIDE+eip CAP_SETUID+eip' /usr/libexec/nordlayer/nordlayer-resolvconf
sudo setcap 'CAP_NET_ADMIN=+eip' /usr/libexec/nordlayer/nordlayer-setcap
sudo setcap 'CAP_NET_ADMIN=+eip' /usr/bin/nordlayer

Remember to also run:

sudo usermod -a -G nordlayer $(whoami)

And then reboot.

PS: I have updated my fork to 3.1.0, and it can be found here:

Pull request is open here:

direc85 commented on 2023-12-13 09:07 (UTC) (edited on 2023-12-13 09:08 (UTC) by direc85)

I wasn't able to connect using 3.0.0 at all - downgrading to 2.6.5 helped, and I was able to connect instantly.

Edit: I recommend to uninstall 3.0.0 and make sure the config files are deletedl, and then install 2.6.5.

direc85 commented on 2023-10-31 13:51 (UTC)

I'm not really sure what causes it but if you run into troubles of connecting to your server, try restarting nordlayer.service before connecting. I disabled autostarting the service, start it in my custom connect script, and stop it in my disconnect script, same idea. I also had multiple (50+ actually) nlx network devices listed with ip addr. They were removed by restarting the service, and after that I was able to connect again.

sidicer commented on 2023-10-28 22:36 (UTC)

As I will not be actively using nordlayer after November 3rd - I am looking for someone who would like to take ownership of this package.

Get in touch with me through and I will provide all the details in forking, how to update the package and how to take ownership in AUR.

sidicer commented on 2023-08-22 07:27 (UTC)

@netwalker yeah this happens when using non-standard drivers that cannot report an OpenState. (all drivers can report administrative state UP/DOWN but some can't and turns out it's actually optional). non-standard (=not so common network cards)

also happens when trying tethering because it won't go through a physical interface

netwalker commented on 2023-08-21 10:53 (UTC)

Hi. After upgrading to version 2.6.5, I'm getting 'no active link' when trying to connect to any gateway. Already tried removing nordlayer.db an restarting the service, but no success. Am I missing something? Thanks for maintaining the package. :)

sidicer commented on 2023-06-22 12:10 (UTC) (edited on 2023-06-22 12:10 (UTC) by sidicer)

Hotfix (Version 2.6.5) released by Nordlayer

The new version should not break nordlayer.db

# Run this if you are unable to use nordlayer after upgrade to 2.6.5
rm /var/lib/nordlayer/nordlayer.db
systemctl restart nordlayer
nordlayer login

sidicer commented on 2023-06-20 12:53 (UTC) (edited on 2023-06-20 12:57 (UTC) by sidicer)

# Run this if you are unable to use nordlayer after upgrade to 2.6.4
rm /var/lib/nordlayer/nordlayer.db
systemctl restart nordlayer
nordlayer login

mearaj commented on 2023-01-05 13:51 (UTC)

Hi @sidicer,
Thank you so much for taking this responsibility.
If anytime, I can be of help, then please do let me know.
Thanks a lot :)

sidicer commented on 2023-01-05 13:48 (UTC)

Will be maintaining this package from now on. Thank you, mearaj, for the work!