The page sends the browser to another address, which sends it back — around and around until the browser gives up after 20 hops. With HTTPS the classic loop is one side redirecting to https:// while another turns it back into http://, most often Cloudflare’s Flexible SSL mode in front of a server that forces HTTPS.
This page isn’t working example.com redirected you too many times. Try deleting your cookies. ERR_TOO_MANY_REDIRECTS
How 2 other clients word the same error
Firefox
The page isn’t redirecting properly This problem can sometimes be caused by disabling or refusing to accept cookies.
curl
curl: (47) Maximum (50) redirects followed
| Error | ERR_TOO_MANY_REDIRECTS |
| Usually fixed by | The website |
| Redirect limit | 20 in Chrome and Firefox; 50 in curl |
| Most common cause | Cloudflare Flexible SSL with an origin that forces HTTPS |
Follow a site’s redirects
Enter the address: we follow every redirect hop by hop and show where it starts going round in circles.
What it means
Each redirect answer carries a Location to go to next. When the chain comes back to an address it has already visited, it never ends; browsers stop after 20 redirects and show this page. Clearing cookies helps only when a cookie is part of the loop — usually the loop is in the site’s configuration.
Why it happens
- Cloudflare set to Flexible SSL — which talks to your server over plain HTTP — while the server redirects HTTP to HTTPS: every answer sends the visitor back to HTTPS, which Cloudflare fetches over HTTP again.
- Cloudflare on Full, Full (strict) or Always Use HTTPS while the server redirects HTTPS back to HTTP.
- Redirect rules in the CDN and on the server that contradict each other (www vs non-www, http vs https).
- WordPress behind a proxy or CDN that ends HTTPS: WordPress sees plain HTTP, and with an https:// site address it redirects the login and admin pages to HTTPS again and again.
How to fix it
- Follow the chain with the check above, or curl -IL, and look for the Location header flipping between http:// and https:// or between two hosts.
- On Cloudflare, use Full (strict) — or Full — instead of Flexible, with a certificate on your server (a free Cloudflare Origin CA certificate works), and do the HTTPS redirect in one place only.
- On WordPress behind a proxy, tell WordPress the visitor used HTTPS: in wp-config.php, set $_SERVER[‘HTTPS’] = ‘on’ when the proxy sends X-Forwarded-Proto: https (Cloudflare does).
- Remove duplicate redirects so that http://, https://, www and non-www each reach the canonical address in one hop.
If you are visiting the site
- Delete the site’s cookies and try again — Chrome suggests it, and it clears loops a cookie causes. If it persists, the loop is on the site.
See it for yourself
curl -IL http://example.com
-I shows only the headers and -L follows each redirect, so every hop’s status and Location is printed in turn; curl stops after 50 with exit code 47.
Questions
Why does Cloudflare Flexible SSL cause redirect loops?
Because Cloudflare connects to your server over plain HTTP in Flexible mode. If the server redirects HTTP to HTTPS, each request comes back as HTTP again. Cloudflare’s own advice is not to use Flexible: switch to Full or Full (strict).
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- ERR_TOO_MANY_REDIRECTS — developers.cloudflare.com
- Flexible — developers.cloudflare.com
- HTTPS — Advanced Administration Handbook — developer.wordpress.org
- curl — How To Use — curl.se
- Error page strings.grdp — raw.githubusercontent.com