We are encountering a “Too Many Redirects” error across various static assets, including images, CSS files, and JavaScript files. This issue is causing significant disruptions to our website’s functionality and appearance.
What steps have you taken to resolve the issue?
Troubleshooting Steps Taken:
We attempted to switch the SSL settings from Full to Full (Strict) on our CDN or server configuration, but this did not resolve the issue.
A similar issue occurred last week (on January 9th), and while it seemed to resolve temporarily, it has resurfaced and persisted for an entire week.
What are the steps to reproduce the issue?
Just browse trhoutgh the site. You will either see images that are not getting loaded, then you click on f12 to see the error.
I am having the same issue on a worker with static assets setup - reported it on Cloudflare Discord here:
The strange thing is that it happens only occasionally but can last for minutes. When a chunk of JS, the main CSS file or a font doesn’t load, that is obviously pretty bad (as in page breaks completely).
Most times there are no redirects - sometimes there are 1 - other times so many that Chrome stops loading the asset (ERR_TOO_MANY_REDIRECTS)
Scripts are caught in a redirect loop, causing javascript websites to fail - the issue seems to be intermittent
What steps have you taken to resolve the issue?
Turning off Cloudflare’s proxy resolves the issue (but then you don’t get the benefits)
I am testing if turning off Speed Brain might resolve the issue
What are the steps to reproduce the issue?
Proxy your DNS through Cloudflare.
This issue is affecting multiple Cloudflare domains and accounts - this issue is effecting sites to white no changes have been made in a long time.
If you make a CURL request to one of the resources that has the infinite loop, you can see that Cloudflare is 301 redirecting to the same url with a % attached at the end (see screenshot)
I don’t think it’s that. We’ve made no changes to that setting in years.
In addition, if you look at the redirect from the screenshot above, you’ll see that the original request is already https.
Hmm … good point. the nf header implies that it is reaching Netlify.
Perhaps it’s something between the two. But the fact that turning off Cloudflare’s proxy resolves the issue makes me suspect that the error is on Cloudflare somewhere.
Before moving to Cloudflare, was your domain working over HTTPS connection?
May I ask what SSL option have you got selected under the SSL/TLS tab at Cloudflare dashboard for your domain ( Flexible, Full, Full Strict … )?
To understand which SSL encryption mode you should select depending on the setup and your origin SSL certificate (if you have got any, or even invalid one?), please use below article for more information:
the problem doesn’t happen when you just load the page, it happens with requests to /api, it only causes problems if you login, and need to check console, network to find out
I switched to cloudflare a few months ago, the cache problem just appeared recently (I haven’t changed anything in config for months)
This is a legitimate cloudflare bug that was introduced roughly 2 weeks ago.
I’ve only found references to it on the internet here:
I am surprised that Cloudflare has not yet addressed this problem, as it has been actively disrupting my websites and appears to be worsening each day.