MLB.com "Varnish Cache Server" error with VPN enabled

1

Getting the following error trying to access MLB.com with Brave with Surfshark VPN enabled. I can access MLB.com with Brave if Surfshark VPN is paused.

I have no problem accessing MLB.com via Chrome, Edge or the DuckDuckGo browser with Surfshark enabled, just when using Brave.

Error 403 Access Denied

Access Denied

Error 54113

Details: cache-bos4683-BOS 1742389114 631506698

Varnish cache server

2

@Steve.Luciani not seeing this issue on my end when connected to SurfShark VPN. Can you tell me:

  • What OS and Brave version you’re using when you see this issue occur?
  • What region you’re connecting to in SurfShark when this occurs (or does it occur regardless of the selected region)?
  • Are you unable to land on the site at all? Or does this error get thrown if you try and visit an article/watch a video/etc while on the site?
3

Thanks for the quick reply.

Windows 10 Pro, 19045.5608

I’m using 1.77.83 Chromium: 134.0.6998.95 (Official Build) beta (64-bit)

New York. Doesn’t matter which city I’m connected to, tho.

Unable to land on the site at all, unless I pause Surfshark. No connection issues when connected to New York and using Chrome or Edge, tho.

In case it matters, can’t open a Brave Tor window either, even with VPN disabled.

4

Just checked on my end on Windows 10 and macOS in Brave Beta, still no issues here. Is this a personal machine or a work issued machine? Also, is it on your personal network or is this in a public space and/or work network?

Additionally, do you have any extensions installed in Brave at this time?

5

Personal machine on my home network. Here are my extensions:

image
image334Ă—551 17.9 KB

I just turned them all off and I’m still seeing the error.

Wondering why other chromium-based browsers running along side Brave on this machine are not having this problem.

6

Can you please try the following?

  1. Create a fresh browser profile (Menu --> More tools --> Add profile)
  2. Close your original profile window (so you only have the new profile window open)
  3. Turn on SurfShark VPN and try visiting mlb.com

Do you get the same results in the new profile?

7

Hi. Created a profile “test”. Quit Brave, restarted and chose “test”. Went to mlb.com and got the same 403 error, unfortunately.

9

I uninstalled the beta and re-installed 1.76.81 and I can now access MLB.com with Surfshark enabled.

1 Like
10

I guess something contained in the Chromium bump resolved the issue. Glad to hear it’s working again.

11

Could be VPN related also, some site will not work well with VPN’s enabled.

12

Same issue surfaced later that day, even with 1.76.81. Out of desperation, I switched to a different IPv6 server. It seems to have solved the problem. No issues yesterday or today. I didn’t even know I was using IPv6 to access MLB.com!

If that’s the fix, I wonder why was Brave relying on IPv6 for MLB.com when Chrome and Edge weren’t?

1 Like
13

Not sure wording “Brave relys on IPv6”, its all about the DNS, and how its configured. Secure DNS may affect it also.