Guide
How to fix ERR_TOO_MANY_REDIRECTS
ERR_TOO_MANY_REDIRECTS means your browser was sent round in a circle and gave up, because two settings keep redirecting to each other. The usual culprits are conflicting HTTPS or www rules, mismatched WordPress URLs, a plugin fighting an .htaccess rule, or a CDN set to the wrong SSL mode. Clear cookies first, then find which two rules disagree.
The loop
What a redirect loop is
A redirect tells the browser to go somewhere else. That is useful, for example to send http visitors to https. A loop happens when the destination sends the browser back to where it started. The browser follows the instructions about twenty times, then stops and shows an error. In Chrome it reads This page isnt working, example.co.uk redirected you too many times, with the code ERR_TOO_MANY_REDIRECTS. Other browsers say The page isnt redirecting properly.
Loops almost always come from two rules that disagree. One says go to the https version, while the other, perhaps unaware that the visitor is already on https, says go to http. Or one forces www while another strips it. Each rule makes sense alone, and together they trap visitors.
The good news is that a loop is a logic fault, not a damaged site. Find the two competing instructions, remove one, and it ends at once.
Anatomy
A typical redirect loop
- Visitor requests httpThe site wants a secure page
- Rule ARedirects to https
- Rule BSees something it dislikes and redirects to http
- Back at the startThe cycle repeats
- Browser gives upERR_TOO_MANY_REDIRECTS
Free SSL included, so HTTPS is easy
Every plan has a free SSL certificate and live chat open 24/7 if redirects get tangled.
Step by step
Fixing the loop in order
Clear cookies and cache for the site
A stale cookie can cause a loop even after the real cause is fixed. Clear the site data, or test in a private window.
Test the exact addresses
Try http and https, with and without www. Note which ones loop. This tells you which rule is involved.
Check WordPress addresses
In Settings then General, the WordPress Address and Site Address should match the version you want, such as https://www.example.co.uk. If you cannot log in, set them in wp-config.php instead.
Review .htaccess
Look for several rules that redirect to https or to www. Keep one of each and remove the rest. Rename the file to test.
Deactivate plugins
Redirect, SSL and security plugins often add their own forcing. Rename the plugins folder, test, then reactivate one by one.
Check CDN or proxy SSL mode
If a CDN sits in front of your site, an SSL mode that talks to your server over plain http while your server forces https creates a loop. Use a full mode that connects securely.
Retest from outside
Test on mobile data in a private window to avoid cached results.
Causes
Frequent causes of redirect loops
| Cause | Clue | Fix |
|---|---|---|
| Conflicting https and www rules | Loops only on one form of the address | Keep a single canonical rule |
| WordPress URLs differ from the server rule | Loop appears after switching to https | Set both addresses to the same https form |
| Redirect plugin plus .htaccess rule | Began after installing a plugin | Use one tool only |
| CDN set to flexible SSL | Server forces https but CDN connects with http | Use full SSL mode |
| Bad cookie or login redirect | Only logged-in pages loop | Clear cookies, check login URLs |
| Redirect rule pointing at itself | A single address loops straight away | Correct the destination |
| Cache storing a bad redirect | Fixed but still looping for some | Purge all caches |
WordPress
The WordPress URL settings that cause loops
WordPress stores two addresses, the WordPress Address and the Site Address, and uses them to build redirects. If they say http while your server forces https, WordPress redirects to http and the server redirects back to https, forever. Likewise, if one includes www and the other does not, WordPress and the server may disagree about the canonical form.
If the loop stops you reaching the dashboard, you can fix it from the file manager. Add two lines to wp-config.php, define( WP_HOME, your https address ); and define( WP_SITEURL, your https address );, using the same address in both. These override the database values. Once you are back in, set the options properly and remove the lines.
You can also check these values in the database table called options, in the rows named siteurl and home, using phpMyAdmin. Take a backup before changing any value. Our guide on moving a website from HTTP to HTTPS shows the whole sequence in the right order.
One source of truth
Where to force https and www
Choose one place
- The control panel redirect tool, or
- One block in .htaccess, or
- One trusted plugin, or
- The CDN page rule, if you use one
- Document which one you picked
Avoid doing all at once
- A plugin and an .htaccess rule together
- Two plugins that both force https
- CDN and server both forcing in different ways
- Old rules from past setups left in place
- Pasting snippets without reading existing ones
Facts
Redirect numbers worth knowing
Proxies
Loops caused by a CDN or proxy
A CDN or proxy sits between visitors and your server. If it connects to your server using plain http, but your server is set to redirect all http requests to https, then every request the CDN makes gets redirected, and the CDN sends it again. The result looks like a loop to the visitor.
The fix is to set the SSL mode on the CDN to one that connects to your server securely and validates its certificate. Your server already has a free SSL certificate, so this works. Avoid any option labelled flexible if your origin forces https.
Purge the CDN cache after changing the mode, because it may store the redirect. If you are not sure how the CDN is configured, ask us, and tell us which service you use and the exact address that loops.
Checklist
Redirect loop checklist
- Clear cookies and test in a private window
- List which address forms loop
- Match WordPress Address and Site Address
- Count the rules that force https
- Count the rules that force www
- Rename .htaccess to test
- Deactivate redirect and SSL plugins
- Check CDN SSL mode and purge cache
Prevention
Keeping redirects tidy
Keep a redirect list
Write down what redirects where and why.
Change one rule at once
Test straight after each addition.
Use one canonical form
Pick https with or without www and stick to it.
Review after migrations
Old rules often survive a move and clash with new ones.
Purge caches
After any redirect change, clear site and CDN caches.
Ask if stuck
Send live chat the address that loops and what you changed.
Wrapping up
Why a clean setup matters beyond the error
A tidy set of redirects does more than prevent errors. It makes pages load faster, because visitors take one hop and not four, and it helps search engines see a single version of each page. If you are also fixing missing pages, our guide on 404 errors and redirects covers how to build a clean list.
Once the loop is gone, test every form of the address one last time: http and https, with and without www. Each should end at the same single page in one step.
FAQ
Common questions
Is ERR_TOO_MANY_REDIRECTS a server error?
It is a configuration fault. The server is working, but two rules send the browser in a circle.
Why does clearing cookies sometimes fix it?
A cookie can trigger a redirect, especially for logins. Clearing it breaks that particular loop for your browser.
Can a plugin cause it?
Yes. Redirect, SSL and security plugins can conflict with .htaccess rules. Deactivate them to test.
I cannot log in to WordPress to fix it. What now?
Set WP_HOME and WP_SITEURL in wp-config.php to the correct address, or disable plugins by renaming the folder.
Will it hurt my SEO?
While the loop lasts, pages cannot be loaded or crawled. Fix it quickly to avoid losing visibility.
Keep reading
Related pages
Hosting with free SSL and help when you need it
Free SSL on every plan and live chat open 24/7.