Meshnet icon indicating copy to clipboard operation
Meshnet copied to clipboard

VPN connection has failed

Open Echron opened this issue 9 months ago • 2 comments

When running this in Docker on my (Synology) NAS, I get the message " The VPN connection has failed. Please check your internet connection and try connecting to the VPN again. If the issue persists, contact our customer support.". When I run this on my local machine, it works fine.

I've tested with the latest stable version v3.18.4, and the dev version (NordVPN 3.20.0). I've tried a lot of different things, changing of cap_add, network_mode:host, privileged mode, disable firewall completely on my Nas, "nordvpn set DNS 1.1.1.1" to force Nordvpn to use a global vpn etc. Nothing seems to work. When I do "nordvpn connect" directly in the container, I'm getting the same error.

I know this is related to Nordvpn and not thick project, but I'd like to know if you have an idea to make the logging more verbose. There is no log file in /var/log/nordvpn. Looking into the Nordvpn code, there are a few reasons this error might show up (https://github.com/search?q=repo%3ANordSecurity%2Fnordvpn-linux%20ConnectCantConnect%20%20%20%20%20&type=code) but I can't see any way to make the output more verbose.

Echron avatar Apr 26 '25 16:04 Echron

Hi Echron,

Since you mentioned Synology, it might be a case of missing iptables modules on the host system. NordVPN is a bit picky about it and we seem to be circling around the issue on multiple operating systems now. It doesn't log anything most of the time and just fails to connect since it apparently can't get access to the required iptables modules from the host system.

On our Discord, someone mentioned the following guide was followed that fixed it for Synology. I would recommend to stick to the stable version for now since we are trying to fix some other stuff in dev that isn't really working yet.

https://github-com.translate.goog/sjtuross/syno-iptables?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=fr&_x_tr_pto=wapp

MattsBos avatar Apr 27 '25 15:04 MattsBos

I just had this issue with v3.18.4 and had to revert to v3.17.0. I already have the syno-iptables stuff setup. Seems like something isn't working quite right in the newer versions with Synology possibly.

woolyninja avatar Jul 03 '25 06:07 woolyninja