Google DNS and Toms

[John Wittenberg]

When I've set Google's DNS address, primary 8.8.8.8 and alternate 8.8.4.4, I cannot load Tomshardware.com including the forums. An "Error 403 - Ohoh Something is wrong ..." shows, and says that "It looks like something is broken in our systems..."

Removing Google's DNS server fixes this issue, but the Tomshardware.com website has been having this problem for the past couple of days (maybe 3 or 4).

I'll look into seeing if I can contact Google, but this seems to be a matter for the Webadmins.

 

[COLGeek]

I am currently using the very same DNS servers and am not experiencing this problem. Odd. Will pass along to admins. Thanks.

 

[John Wittenberg]

Well, something changed! For the first time in several days I can access Toms on my desktop.

Thank you for passing that info along, as I highly suspect that that was how it got fixed.

 

[COLGeek]

I have been using those settings for years. As far as I know, nothing has changed on this end. If I find something from the admins, I'll let you know.

Glad you are operational now. Have fun!

 

[John Wittenberg]

It might have also been a regional issue (I'm in Idaho) that Google fixed. I did post to their DNS forums at the same time.

 

[John Wittenberg]

Spoke too soon, as it is back to the 403 error.

 

[COLGeek]

Are you using any ad blocker type applications? Also, what browser(s) are you using?

 

[John Wittenberg]

Chrome, Edge, and IE 11 on my desktop. Chrome has an ad blocker. All have the same issue ONLY when I set my router to use Google's DNS servers.

My phone is using Chrome. Works fine on LTE, but the same issue when connected to my wifi with Google's DNS.

I also tried updating to the latest Tomato version for my R7000 wireless router to no avail.

 

[COLGeek]

We should know something from the admins soon. Likely not before tomorrow.

Do you have issues with any other websites?

 

[John Wittenberg]

No other websites that I visit are having issues.

Also, now it is back. So it appears to be intermittent now - and the worst kind of problem to try and troubleshoot. Hopefully it is just Google trying some things out.

 

[Titillating]

Sorry you've been running into this issue! 403 errors have been on the rise in the past week or so. We're still trying to get to the root of it. When you get the chance, can you please send me a PM with the IP address you are using when you run into a 403 error so that we can check our logs?

 

[John Wittenberg]

Will do. I'll check again tonight as well as get my public IP.

 

[John Wittenberg]

Just a quick followup. I got home and couldn't access Tomshardware from my desktop (chrome or edge), but could on my phone (chrome) - they are both on the same network, one wired and one wireless.

Not sure if my releasing and renewing my internal IP fixed it or not, but after I did that my desktop could access Toms again. Probably just a coincidence.

 

[John Wittenberg]

Just checked again and it is now down for desktop and phone now (same network). Confirmed that releasing and renewing local IP as a fix was just a coincidence as it had no effect this time.

 

[Titillating]

I was informed by the devs that they believe they have fixed this issue, as of 4 hours ago. Browse a bit, see if it happens again. If so, shoot me a PM.