gluetun: Bug: NordVPN Credentials Wrong
Is this urgent?
Yes
Host OS
Ubuntu 20.04.4 LTS
CPU arch
x86_64
VPN service provider
NordVPN
What are you using to run the container
docker-compose
What is the version of Gluetun
Running version latest built on 2022-04-23T12:58:11.855Z (commit a1d70f7)
What’s the problem 🤔
Haven’t changed credentials, can still log into NordVPN app. Gluetun sporadically works with these creds.
Share your logs
2022-04-25T22:57:43Z INFO [openvpn] SIGUSR1[soft,auth-failure] received, process restarting
2022-04-25T22:57:53Z INFO [openvpn] TCP/UDP: Preserving recently used remote address: [AF_INET]213.232.87.204:1194
2022-04-25T22:57:53Z INFO [openvpn] UDP link local: (not bound)
2022-04-25T22:57:53Z INFO [openvpn] UDP link remote: [AF_INET]213.232.87.204:1194
2022-04-25T22:57:55Z WARN [openvpn] 'link-mtu' is used inconsistently, local='link-mtu 1582', remote='link-mtu 1634'
2022-04-25T22:57:55Z WARN [openvpn] 'auth' is used inconsistently, local='auth [null-digest]', remote='auth SHA512'
2022-04-25T22:57:55Z INFO [openvpn] [nl729.nordvpn.com] Peer Connection Initiated with [AF_INET]213.232.87.204:1194
2022-04-25T22:57:56Z ERROR [openvpn] AUTH: Received control message: AUTH_FAILED
Your credentials might be wrong 🤨
Share your configuration
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 7
- Comments: 41 (15 by maintainers)
Commits related to this issue
- hotfix(nordvpn): use `aes-256-cbc` before GCM — committed to qdm12/gluetun by qdm12 2 years ago
So this is fixed on
qmcgaw/gluetun:latest
right?I switched to v3.28.2 and it is working for me as well.
Awesome, thanks.
:964
again (digestsha256:2af979f02176dbc0d619840968a3892e422a3a962489e9e508b868433b2804ce
), does it work? I re-addedcomp-lzo no
but flipped the order of ciphers around fromaes-256-gcm aes-256-cbc
toaes-256-cbc aes-256-gcm
.-e OPENVPN_CIPHERS=aes-256-cbc
(to remove the gcm variant)?-e OPENVPN_FLAGS="--comp-lzo"
?And that should finally nail down what’s the required settings for Nordvpn. Thanks in advance
Wanted to be extra sure, just switched back again to V3.28.2 and its good, I cant say what the issue is but that version works with my setup!
@oenu
-e OPENVPN_CIPHERS=aes-256-cbc
(to remove the gcm variant)?-e OPENVPN_FLAGS="--comp-lzo"
?You can mix and matching these two to see what combo works?
964 still not working for me. Could it have something to do with a1d70f7? I’d say that’s about the time it stopped working for me. Thanks in advance for all the help regardless!
@qdm12 Just at work rn, have seen this, will report back
I was having the same issue starting yesterday. I did move to v3.28.2 and it seems to have fixed the issue for now.
Just switched to a server in the US on V3.28.2 and its working just fine, switched to
latest
and im getting the sameas before
Scratch that, just tried again with V3.28.2 (c04cd62) and its up, didnt change anything on my end