Hello all
We currently have just 2 sites on here, one is live and one is for staging. Both have been live for ages (a couple of years) with no problems at all. Suddenly though, the errors of ‘net::ERR_TOO_MANY_REDIRECTS’ are being thrown on both. The issue is that not all the users (approx 1500) are seeing the same results. Some get a blank white screen, some get half of the assets, some don’t have any problems at all. This hasn’t been as a result of a deployment, it’s just appeared out of the blue.
The DNS entries all seem to be ok (and have been for some time) but if I use the netlify subdomain (https://printplate-v2.netlify.app) then all seems fine. If I use the primary domain, it throws the errors. It hints towards DNS issues (especially as both sites are linked to the same parent domain name) but if nothing has changed then I’m a little confused. Has anyone else had this?
Many thanks.
@DevelopmentDept I’ve had to google to try and determine your ‘primary domain’, but if it’s the one I’m looking at, then the request is actually being served by cloudflare.
The DNS records for that domain also indicate the same.
Do you have cloudflare sitting in front of Netlify?
If so, you could look into that too.
You may already be aware, but see:
https://answers.netlify.com/t/support-guide-what-problems-could-occur-when-using-cloudflare-in-front-of-netlify/138
https://answers.netlify.com/t/support-guide-why-not-proxy-to-netlify/8869
Thank you Nathan. That’s annoying as something has been updated on Cloudflare on our end. I can see the ‘proxied’ switch for the DNS entries have been switched on when they have always been off (and therefore all ok). I’ve just changed them and will now wait for it to do it’s thing. Hopefully, that’s it…and then I have to find out why the switch was switched on!
Many thanks again, I’ll update this later if that’s solved it.
After propagation, it’s now resolved. Still not yet found out why the proxied switch was changed but that might be something to do with the domain name owner and not Cloudflare!
Thanks again for the response.
1 Like