ERR_TOO_MANY_REDIRECTS on Cloudflare: find which side is bouncing

TL;DR

The fix is to move to Full or Full (strict), not to add redirect rules. Check with curl -sI (no -L): each response shows one hop.

Steps

1. With Flexible mode, Cloudflare talks HTTP to the origin. If the origin redirects HTTP to HTTPS, the sequence is: visitor -> HTTPS -> Cloudflare -> HTTP -> origin -> redirect to HTTPS -> Cloudflare -> HTTP -> origin... forever. The fix is to move to Full or Full (strict), not to add redirect rules.
2. One rule sends apex -> www, the origin (or another rule) sends www -> apex. Audit all redirect sources together: Single Redirects, Page Rules, Bulk Redirects, origin config, and the Always Use HTTPS setting.
3. - curl -sI the URL: read the hop chain, identify each redirect's author.

• If Flexible SSL is in play, fix the SSL mode first.
• After fixing, clear edge cache: redirects get cached, and a cached bad redirect outlives the config fix.

When to use

You are seeing this: ERR\TOO\MANY\REDIRECTS means two sides keep redirecting to each other. Use this skill when you run into "ERRTOOMANYREDIRECTS on Cloudflare: find which side is bouncing".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• http://`
• https://`

Verified against the live SSL/TLS modes doc (Flexible redirect-loop mechanism) and URL forwarding docs (Single Redirects first-match, Page Rules precedence). Refs: https://developers.cloudflare.com/ssl/origin-configuration/ssl-modes/ and https://developers.cloudflare.com/rules/url-forwarding/