Waiting to connect, but never does

Technical Support for Routers
1

I've seen others post here about getting the message, "The client is starting, please wait…" but I'm still not getting this solved.

SurfShark is my VPN provider. I've entered my credentials for SurfShark. I've only uploaded two OpenVPN config files (for UDP) to my GL-MT3000 Beryl AX router: one for Dallas, the other for New York. I live in the US.

Each time I connect to one of them, I get that message about it starting, but it never does and I can't figure out why.

Any and all help is much appreciated. Thank you.

Mon Sep 16 14:35:32 2024 daemon.notice ovpnclient[24893]: TCP/UDP: Preserving recently used remote address: [AF_INET]146.70.186.171:1194
Mon Sep 16 14:35:32 2024 daemon.notice ovpnclient[24893]: Socket Buffers: R=[212992->212992] S=[212992->212992]
Mon Sep 16 14:35:32 2024 daemon.notice ovpnclient[24893]: UDP link local: (not bound)
Mon Sep 16 14:35:32 2024 daemon.notice ovpnclient[24893]: UDP link remote: [AF_INET]146.70.186.171:1194
Mon Sep 16 14:35:32 2024 daemon.notice ovpnclient[24893]: TLS: Initial packet from [AF_INET]146.70.186.171:1194, sid=08e91b10 ce08dae8
Mon Sep 16 14:35:32 2024 daemon.notice ovpnclient[24893]: VERIFY OK: depth=2, C=VG, O=Surfshark, CN=Surfshark Root CA
Mon Sep 16 14:35:32 2024 daemon.notice ovpnclient[24893]: VERIFY OK: depth=1, C=VG, O=Surfshark, CN=Surfshark Intermediate CA
Mon Sep 16 14:35:32 2024 daemon.notice ovpnclient[24893]: VERIFY KU OK
Mon Sep 16 14:35:32 2024 daemon.notice ovpnclient[24893]: Validating certificate extended key usage
Mon Sep 16 14:35:32 2024 daemon.notice ovpnclient[24893]: ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Mon Sep 16 14:35:32 2024 daemon.notice ovpnclient[24893]: VERIFY EKU OK
Mon Sep 16 14:35:32 2024 daemon.notice ovpnclient[24893]: VERIFY OK: depth=0, CN=us-nyc-v135.prod.surfshark.com
Mon Sep 16 14:35:32 2024 daemon.warn ovpnclient[24893]: WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1601', remote='link-mtu 1581'
Mon Sep 16 14:35:32 2024 daemon.warn ovpnclient[24893]: WARNING: 'tun-mtu' is used inconsistently, local='tun-mtu 1500', remote='tun-mtu 1532'
Mon Sep 16 14:35:32 2024 daemon.warn ovpnclient[24893]: WARNING: 'auth' is used inconsistently, local='auth SHA512', remote='auth [null-digest]'
Mon Sep 16 14:35:32 2024 daemon.notice ovpnclient[24893]: Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 4096 bit RSA, signature: RSA-SHA256
Mon Sep 16 14:35:32 2024 daemon.notice ovpnclient[24893]: [us-nyc-v135.prod.surfshark.com] Peer Connection Initiated with [AF_INET]146.70.186.171:1194
Mon Sep 16 14:35:33 2024 daemon.notice ovpnclient[24893]: SENT CONTROL [us-nyc-v135.prod.surfshark.com]: 'PUSH_REQUEST' (status=1)
Mon Sep 16 14:35:33 2024 daemon.notice ovpnclient[24893]: AUTH: Received control message: AUTH_FAILED
Mon Sep 16 14:35:33 2024 daemon.notice ovpnclient[24893]: SIGTERM[soft,auth-failure] received, process exiting

2

Mon Sep 16 14:35:33 2024 daemon.notice ovpnclient[24893]: AUTH: Received control message: AUTH_FAILED

Username or password are invalid.

See OpenVPN Client - GL.iNet Router Docs 4

Surfshark service credentials are different from your Surfshark account credentials, namely your email address and your password. You'll need Surfshark service credentials to connect to the VPN using the manual OpenVPN configuration method in the router.

3

My bad! I got it working now, thanks.

But shouldn't my IP be masked though? When I chose New York and went to a site to find my ip, it still showed my local area.

4

What is the VPN client proxy mode of the router?
Try it one more time:
https://whatismyipaddress.com/

5

It's set to the first one: Global Proxy.

I think it's working now although when I chose a config file for Houston, TX, my ip shows up in California.?? But when I chose one for the UK as a test, it showed me in the UK.

Unless I should check something else, I think I'm set. I appreciate your help.

6

IP locations are often wrong, thats normal.

7

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.