TroubleByteSearch
SOURCE VERIFIEDSource review Sep 7, 2026No hands-on test claimed2 sources

ERR_TOO_MANY_REDIRECTS on Cloudflare

Cloudflare says redirect loops commonly come from a conflict between SSL/TLS encryption mode, edge certificate options or redirect rules and the redirects already configured at the origin.

AuthorshipWritten and source-reviewed by Mihailo Ivanjac
Record created Sep 7, 2026Last source review Sep 7, 2026Source review only
SymptomA browser reports ERR_TOO_MANY_REDIRECTS or “The page isn’t redirecting properly” for a Cloudflare-proxied site.
Problem familyNetworking · Cloudflare
Highest step riskCaution
Editorial statePublic launch · indexed
Affected scope
Cloudflare SSL/TLSAlways Use HTTPSHSTSRedirect RulesOrigin redirects
Start here

Align Cloudflare encryption mode with origin redirects

Map the actual redirect chain first. Then make Cloudflare SSL/TLS mode and edge redirects consistent with the origin. Avoid having one layer force HTTPS while another sends the request back to HTTP.

  1. Check the current Cloudflare SSL/TLS encryption mode.
  2. If Flexible is used while the origin forces HTTP to HTTPS, move to Full or higher only after the origin has a valid HTTPS configuration.
  3. If Full/Full (strict) is used, remove any origin rule that sends HTTPS back to HTTP.
  4. Retest the chain from a clean browser session or curl.

Why this branch first: Cloudflare documents encryption-mode conflicts as a direct cause of redirect loops.

TroubleByte diagnostic diagram for tracing an ERR_TOO_MANY_REDIRECTS loop between Cloudflare and the origin.
Cloudflare redirect-loop pathTroubleByte · Original TroubleByte editorial diagram
TroubleByte Tool

Decode the browser redirect error

Use the browser/error decoder to distinguish ERR_TOO_MANY_REDIRECTS from an HTTP status code, then follow this page to isolate the loop.

Decode redirect error →
Visual diagnosis

TroubleByte diagnostic path

01
Trace

Capture every Location hop.

02
TLS mode

Align edge-to-origin encryption.

03
Rules

Remove conflicting edge/origin redirects.

04
Verify

Confirm one stable canonical URL.

Original TroubleByte diagnostic map. It summarizes the cited troubleshooting order; it is not a vendor screenshot.

Diagnosis

What this usually means

A redirect loop is a cycle, not a failed destination. With Cloudflare, common cycles arise when edge encryption/HTTPS behavior conflicts with origin redirects, or when two redirect rules send requests back and forth. The fix is to remove the contradiction, not add another redirect.

What the evidence establishes

What we verified from the source material

Cloudflare’s redirect-loop documentation identifies SSL/TLS encryption mode conflicts, Always Use HTTPS/HSTS behavior and conflicting redirect rules as common ERR_TOO_MANY_REDIRECTS causes and recommends removing the contradictory redirect behavior.

Before you change anything

Prerequisites and checks

Prepare first

  • Capture the redirect chain before clearing settings.
  • Know the origin’s intended canonical scheme and hostname.
  • Check whether more than one layer controls HTTP-to-HTTPS or hostname redirects.

Checks that prevent the wrong fix

  • Capture the redirect chain with browser DevTools or curl before changing settings.
  • Record the Cloudflare SSL/TLS encryption mode.
  • List active Always Use HTTPS, HSTS, Redirect Rules/Page Rules and origin redirects.
Scope

Applies to

✓ Cloudflare SSL/TLS✓ Always Use HTTPS✓ HSTS✓ Redirect Rules✓ Origin redirects
Troubleshooting path

Solutions, in order

01
SAFE · START HERE

Align Cloudflare encryption mode with origin redirects

  1. Check the current Cloudflare SSL/TLS encryption mode.
  2. If Flexible is used while the origin forces HTTP to HTTPS, move to Full or higher only after the origin has a valid HTTPS configuration.
  3. If Full/Full (strict) is used, remove any origin rule that sends HTTPS back to HTTP.
  4. Retest the chain from a clean browser session or curl.

Why this can work: Cloudflare documents encryption-mode conflicts as a direct cause of redirect loops.

02
CAUTION

Remove conflicting edge/origin redirect rules

  1. Review Always Use HTTPS, HSTS and Cloudflare Redirect Rules/Page Rules.
  2. Review the origin web server/application redirects for the same host/path.
  3. Remove or disable the rule that sends the request back to a previously visited URL/scheme.
  4. Keep one intentional canonical redirect and verify the final URL.

Why this can work: Cloudflare documents edge-certificate settings and conflicting redirect rules as additional loop causes.

Verification

How to know the fix actually worked

  1. The request reaches one stable canonical HTTPS URL without repeating a previous location.
  2. Refreshing or opening a private session no longer triggers the redirect-loop error.

Do not count a temporary disappearance of the symptom as a confirmed fix if the problem normally returns after a restart, reconnect or several minutes of use.

Stop conditions

When not to keep changing things

  • Do not add another redirect rule until the existing loop is mapped; additional rules can make the cycle harder to diagnose.

Escalation: If the redirect chain crosses multiple applications or proxies, reduce it to one canonical HTTPS redirect owner and retest each layer separately before re-enabling complex rules.

Evidence

Sources used for this record

Primary · checked Sep 7, 2026Cloudflare — ERR_TOO_MANY_REDIRECTSFirst-party documentation used to verify the troubleshooting scope and steps.Corroborating · checked Sep 7, 2026Cloudflare — Always Use HTTPSFirst-party documentation used to verify the troubleshooting scope and steps.
Who reviewed this

Mihailo Ivanjac

This record was written and source-reviewed by Mihailo Ivanjac. Source review means the cited documentation was checked against the troubleshooting order on this page; it does not imply a hands-on reproduction unless the page explicitly says so.

Author profile and editorial scope →
Community troubleshooting

Discuss this exact problem

Share what happened on your system, ask a focused follow-up question, or add evidence that may help someone with the same symptom. Community posts are separate from TroubleByte editorial verification.

Before posting Do not include passwords, API keys, recovery codes, private IP addresses or other secrets. TroubleByte automatically attaches only coarse OS, browser and device-class context. Your full Browser & System Info report is not uploaded automatically.
Start a discussion
Posts are public. Guest identity is pseudonymous and browser-specific.

Loading community discussions…
Keep diagnosing

Related Networking problems

CloudflareCloudflare Error 523: Origin is unreachableCloudflare 523 is a routing/reachability problem: Cloudflare cannot contact the configured origin because the origin IP is wrong or the network path has no usable route. It is distinct from 521 refusal and 522 timeout, so the fastest checks are DNS origin address and routing evidence rather than application code.CloudflareCloudflare Error 524: A timeout occurredCloudflare 524 means the TCP connection to the origin succeeded, but the origin did not return an HTTP response within the proxy read timeout (125 seconds by default) or did not complete a write in time. That makes slow application work, long database queries and resource saturation more relevant than firewall reachability.CloudflareCloudflare Error 521: Web server is downCloudflare defines Error 521 as the origin web server refusing connections from Cloudflare. Common causes include an offline origin application or security rules blocking Cloudflare IP ranges.
Change log

Revision history

Show 1 recorded revision

2026-09-07 — Created for the v0.8 content-scale pass from current first-party documentation; held noindex for editorial review.