Back up redirect configuration and record the Cloudflare encryption mode, application URL and any www canonicalisation. Use a fresh browser or a request tool that shows each redirect hop.

1. Request the failing URL and record the sequence of HTTP status codes and Location values. Identify whether the loop alternates HTTP/HTTPS or different hostnames.
2. If Flexible mode is used while the origin forces HTTPS, prepare a valid origin certificate and move to Full (strict). Flexible’s HTTP origin connection can trigger the same redirect repeatedly.
3. Check the application’s canonical URL, trusted-proxy configuration and server redirects for contradictory rules.
4. Review Cloudflare Redirect Rules and Always Use HTTPS alongside origin rules. Remove only the conflicting behaviour and keep one coherent destination.
5. Retest nested paths, login and forms, then clear a cached redirect where necessary after confirming the configuration is correct.

The request should reach the intended HTTPS page through a short redirect chain. Test both hostname variants and confirm query strings remain intact where required.

If the loop persists, inspect a Worker or plugin that also redirects requests. Do not disable all HTTPS permanently to mask a configuration conflict. Restore the previous known configuration if an experimental change broadens the outage.

A permanent redirect may be cached locally or at another layer. Confirm the live response with a fresh client before concluding that the corrected server rule is still wrong.

• Moving a Cloudflare site to Full strict TLS safely
• Creating a Cloudflare Single Redirect for an old URL
• Diagnosing overlapping Cloudflare rules
• Finding mixed content when HTTPS works through Cloudflare

• Cloudflare: Too Many Redirects