Can't connect to NordVPN

tevskapoan · 2024-02-07T14:10:54.673Z

I’m trying to configure nordvpn client. Every time I try to start it, it gets stuck in infinite loading. Here’s my log:

Wed Feb  7 13:36:32 2024 daemon.warn ovpnclient[13418]: WARNING: --ping should normally be used with --ping-restart or --ping-exit
Wed Feb  7 13:36:32 2024 daemon.warn ovpnclient[13418]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Wed Feb  7 13:36:32 2024 daemon.notice ovpnclient[13418]: NOTE: --fast-io is disabled since we are not using UDP
Wed Feb  7 13:36:32 2024 daemon.notice ovpnclient[13418]: Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Wed Feb  7 13:36:32 2024 daemon.notice ovpnclient[13418]: Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Wed Feb  7 13:36:32 2024 daemon.notice ovpnclient[13418]: TCP/UDP: Preserving recently used remote address: [AF_INET]141.98.103.123:443
Wed Feb  7 13:36:32 2024 daemon.notice ovpnclient[13418]: Socket Buffers: R=[131072->131072] S=[16384->16384]
Wed Feb  7 13:36:32 2024 daemon.notice ovpnclient[13418]: Attempting to establish TCP connection with [AF_INET]141.98.103.123:443 [nonblock]
Wed Feb  7 13:36:33 2024 daemon.notice ovpnclient[13418]: TCP connection established with [AF_INET]141.98.103.123:443
Wed Feb  7 13:36:33 2024 daemon.notice ovpnclient[13418]: TCP_CLIENT link local: (not bound)
Wed Feb  7 13:36:33 2024 daemon.notice ovpnclient[13418]: TCP_CLIENT link remote: [AF_INET]141.98.103.123:443
Wed Feb  7 13:36:33 2024 daemon.notice ovpnclient[13418]: TLS: Initial packet from [AF_INET]141.98.103.123:443, sid=47603a3b 9a4f1d86
Wed Feb  7 13:36:34 2024 daemon.notice ovpnclient[13418]: VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA
Wed Feb  7 13:36:34 2024 daemon.notice ovpnclient[13418]: VERIFY OK: depth=1, O=NordVPN, CN=NordVPN CA9
Wed Feb  7 13:36:34 2024 daemon.notice ovpnclient[13418]: VERIFY KU OK
Wed Feb  7 13:36:34 2024 daemon.notice ovpnclient[13418]: Validating certificate extended key usage
Wed Feb  7 13:36:34 2024 daemon.notice ovpnclient[13418]: ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Wed Feb  7 13:36:34 2024 daemon.notice ovpnclient[13418]: VERIFY EKU OK
Wed Feb  7 13:36:34 2024 daemon.notice ovpnclient[13418]: VERIFY X509NAME OK: CN=rs48.nordvpn.com
Wed Feb  7 13:36:34 2024 daemon.notice ovpnclient[13418]: VERIFY OK: depth=0, CN=rs48.nordvpn.com

Can someone please help me resolve this?

admon · 2024-02-07T14:11:56.925Z

Even if I don’t see a login error itself: Did you use the right credentials from the NordVPN dashboard?
They are different from the one you use for downloading the OVPN config.

tevskapoan · 2024-02-07T18:00:05.264Z

Thanks a lot for the quick reply @adomon. I was too quick to post the question. After just a little digging through I found out that the problem is I’ve used my NordVPN user credentials (email/password login for nordvpn.com), instead of using service credentials. More information is available here: https://support.nordvpn.com/hc/en-us/articles/19685514639633-Changes-to-the-login-process-on-third-party-apps-and-routers. Also, there is a lot of information about this around GL-Inet forum

alzhao · 2024-02-08T09:10:36.388Z

Seems you are using old firmware.

The new firmware will prohibit you to input email/password.

tevskapoan · 2024-02-08T10:55:34.991Z

How can I determine if my firmware is old or not? Where can I find the latest released firmware version number?

admon · 2024-02-08T11:18:43.963Z

Here you go: https://dl.gl-inet.com/