“The client is starting, please wait…” FOREVER!

I have been trying to start a VNP cilent using NordVNP on the GL.iNet GL-AX1800 router but the damned thing never connects but at yellow “The client is starting, please wait…”
It did connect in the past but now it never does. Not sure what changed.
I have pasted the log so those who understand it can see what is going on:

“Fri Jul 21 10:27:53 2023 daemon.notice ovpnclient[4184]: Incoming Control Channel Authentication: Using 512 bit message hash ‘SHA512’ for HMAC authentication\nFri Jul 21 10:27:53 2023 daemon.notice ovpnclient[4184]: TCP/UDP: Preserving recently used remote address: [AF_INET]181.214.70.162:1194\nFri Jul 21 10:27:53 2023 daemon.notice ovpnclient[4184]: Socket Buffers: R=[163840->163840] S=[163840->163840]\nFri Jul 21 10:27:53 2023 daemon.notice ovpnclient[4184]: UDP link local: (not bound)\nFri Jul 21 10:27:53 2023 daemon.notice ovpnclient[4184]: UDP link remote: [AF_INET]181.214.70.162:1194\nFri Jul 21 10:27:53 2023 daemon.notice ovpnclient[4184]: TLS: Initial packet from [AF_INET]181.214.70.162:1194, sid=89452ca4 e6719699\nFri Jul 21 10:27:53 2023 daemon.notice ovpnclient[4184]: VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA\nFri Jul 21 10:27:53 2023 daemon.notice ovpnclient[4184]: VERIFY OK: depth=1, O=NordVPN, CN=NordVPN CA8\nFri Jul 21 10:27:53 2023 daemon.notice ovpnclient[4184]: VERIFY KU OK\nFri Jul 21 10:27:53 2023 daemon.notice ovpnclient[4184]: Validating certificate extended key usage\nFri Jul 21 10:27:53 2023 daemon.notice ovpnclient[4184]: ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication\nFri Jul 21 10:27:53 2023 daemon.notice ovpnclient[4184]: VERIFY EKU OK\nFri Jul 21 10:27:53 2023 daemon.notice ovpnclient[4184]: VERIFY X509NAME OK: CN=us9760.nordvpncom\nFri Jul 21 10:27:53 2023 daemon.notice ovpnclient[4184]: VERIFY OK: depth=0, CN=us9760.nordvpncom\nFri Jul 21 10:27:53 2023 daemon.notice ovpnclient[4184]: Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 4096 bit RSA, signature: RSA-SHA512\nFri Jul 21 10:27:53 2023 daemon.notice ovpnclient[4184]: [us9760.nordvpncom] Peer Connection Initiated with [AF_INET]181.214.70.162:1194\nFri Jul 21 10:27:55 2023 daemon.notice ovpnclient[4184]: SENT CONTROL [us9760.nordvpncom]: ‘PUSH_REQUEST’ (status=1)\nFri Jul 21 10:28:00 2023 daemon.notice ovpnclient[4184]: SENT CONTROL [us9760.nordvpncom]: ‘PUSH_REQUEST’ (status=1)\nFri Jul 21 10:28:00 2023 daemon.notice ovpnclient[4184]: AUTH: Received control message: AUTH_FAILED\nFri Jul 21 10:28:00 2023 daemon.notice ovpnclient[4184]: SIGTERM[soft,auth-failure] received, process exiting\n”

I removed the “.” from the links so that I could paste it. Anyway, I have no idea what all that means but I am hoping that you smart people can help me out.
Cheers!

That concerns me.

(Does Nord still not have straight WireGuard profiles easily available to their client base yet? Your Flint is capable of 500 Mbps vs 112 using OpenVPN.)

Possibly related:

1 Like

This was exactly the issue: “Nord has VPN specific username and password, which is different from your Nord login username and password.”

Confusing but at least that got it working. You’re amazing! Thank you for sharing what you found!

1 Like