Need Help: Surfshark WireGuard Username and Password for MT6000 Configuration

I'm having trouble configuring the correct settings for Surfshark WireGuard on my MT6000. The Surfshark log-in is present, but I'm unsure where to obtain the required username and password. Despite multiple inquiries with Surfshark's support chat, I couldn't get any assistance. Does anyone here in the forum have any ideas or experience with this and could help me out? Thank you in advance!

I assume they are the same like with OpenVPN, see OpenVPN Client - GL.iNet Router Docs 4

Is it the same used to login in their website?

invalid login info [20001100]

No, try many times already

Yes. I use surfshark and I used my sign in to setup the VPN on the router that I use for their website.

1 Like

Contains your SurfShark password some weird characters or is extra long maybe?

I tried on 4.7-op24 and the VPN is working fine.
The credentials are exactly the same used to login in their website.

I have the same issue, with the latest FW on Brume 2.
I tried with two different surfshark accounts.

invalid login info [20001100]

"Contains your SurfShark password some weird characters or is extra long maybe?" ... well I hope all passwords do contain something more complicated than 12345

Mine has special characters and it's working (4.7.0-op24 - Flint 2)

Thanks for the Input.
Do you use 2FA on Surfshark too? Maybe that's an issue ...?

I tried with different browsers, same issue ... even after factory reset.

Hey @slike
I believe the issue is 2FA.
When I temporarily disabled 2FA on my surfshark-account, I was able to login via the gl-inet-Router's interface.

Not the nicest way to go, but at least now it's working as wanted.

2 Likes

So this is really it ... Surfshark can not be logged into from glinet's admin interface as long as 2fa is on. Tested it on an MT3000 with 4.7.0 as well

I was having the same error.

I tried disabling the 2FA on my account, logging into my account on my Beryl AX and it finally let me in.

I enabled my 2FA afterwards. Annoying process but it worked I suppose. 2/20/2025