Too many redirects (ERR_TOO_MANY_REDIRECTS) on your website
On this page
A redirect loop happens when two rules send the visitor back and forth — usually one that wants https:// and one that wants http://, or one that adds www and one that removes it.
Symptoms
- "This page isn't working — example.com redirected you too many times",
ERR_TOO_MANY_REDIRECTS. - Firefox: "The page isn't redirecting properly".
- The WordPress login page keeps reloading.
Causes
Most likely first:
- Cloudflare's SSL mode is Flexible. Cloudflare asks this server over
http://, this server sends it tohttps://, and Cloudflare asks overhttp://again. - The application's own address does not match — for example WordPress set to
http://or withoutwww, while the server or a rule sends visitors elsewhere. - A rule in
.htaccessor in Redirects conflicts with another one, or redirects a page to itself. - Old cookies or a cached redirect in the browser.
http:// visitors to https:// (except the certificate checks). You do not need your own http-to-https rule; a second one only adds a chance for loops.Fix
See the redirect
Open Site Check (section Advanced), choose the website and click Check. Answer on this server (for https://) and Plain http:// show the first answer of each, with an arrow to where it redirects (HTTP 301 … → https://…). If https:// redirects to http:// (or to the same address), the loop starts on this server; if https:// answers HTTP 200 here, the loop is outside it (Cloudflare or the browser).
1. Cloudflare Flexible
Set Cloudflare's SSL mode to Full (strict). From the panel: Cloudflare (section Domains) → Manage → SSL: Full (strict). The website needs its certificate here first; see Cloudflare 525 and 526.
2. The application's address
For WordPress, the two addresses under Settings → General must be exactly the address you want, for example https://www.example.com (with or without www, but the same as the rest of your rules). If you cannot open the dashboard, set them in wp-config.php with File Manager (section Files):
define('WP_HOME', 'https://example.com');
define('WP_SITEURL', 'https://example.com');
Other applications have a similar "site URL" setting in their configuration file.
3. Conflicting rules
- Open Redirects (section Domains). Remove a redirect whose From and To are the same page, or that sends
/of a website to the same website with Keep the rest of the path. - In File Manager, open the website's
.htaccess. Remove your own "force https" rules (the server does this) and make sure only one rule decides aboutwww. Changes apply within a minute. - Plugins that force https or www (WordPress) can loop with each other; turn them off one by one by renaming their folder.
4. Browser cache and cookies
Delete the cookies of the site or try a private window. Browsers remember permanent (301) redirects.
Still not working?
If your host has turned on the AI assistant, click Ask the AI assistant what is wrong on Site Check — it sees the redirect chain. Otherwise send the Site Check result to your host through Support.
Thank you — this helps us improve the article.
Still stuck?
Ask the AI about your exact situation — it answers from this knowledge base — or contact us.
Related articles
- Cloudflare error 525 or 526 on your website
Fix Cloudflare "Error 526: Invalid SSL certificate" and "Error 525: SSL handshake failed": get the certificate issued here, then use Full (strict).
- SSL certificate not valid (NET::ERR_CERT_COMMON_NAME_INVALID)
Fix "Your connection is not private" and NET::ERR_CERT_COMMON_NAME_INVALID: see why the free certificate was not issued for your site and request it.
- 404 Not Found after moving a website to this server
Pages answer "404 Not Found" after you moved or uploaded a website. Check the website folder, .htaccess rules, file name case and the stored address.