NordVPN automatic provider fails, custom official .ovpn works - expected behavior? #3420
Unanswered
giovanni-cm
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
NordVPN automatic configuration stopped working - Solved using official OpenVPN configuration
After several years of using Gluetun with NordVPN, my VPN suddenly stopped working.
Symptoms
WireGuard:
OpenVPN (automatic provider mode):
The container continuously restarted.
Environment
Investigation
The following were verified:
Packets were leaving correctly but no VPN tunnel was established.
Interesting discovery
The official OpenVPN configuration downloaded from the NordVPN dashboard was completely different from the automatically selected configuration.
Automatic Gluetun:
Official NordVPN file:
(or its corresponding IP)
The official file connected successfully using OpenVPN Connect on Windows.
Solution
Instead of using:
VPN_SERVICE_PROVIDER=nordvpnI switched to:
and mounted the official NordVPN configuration:
Credentials are still provided through:
using NordVPN Service Credentials.
Result
The container immediately became:
All services behind Gluetun started working again.
Question
Is there any known difference between:
The automatic configuration consistently failed in my environment, while the official OpenVPN configuration worked immediately without any modification.
All reactions