We come across a lot of different errors here at Kinsta, and ERR_TOO_MANY_REDIRECTS (also known as a redirect loop) is one we see on a regular basis.
Typically this occurs after a recent change on your website, a misconfiguration of redirects on your server, or wrong settings with third-party services. But don’t worry, this error is fairly easy to fix.
Check out the recommendations below on how to fix this error and get your site back up and running.
What is the ERR_TOO_MANY_REDIRECTS Error?
The ERR_TOO_MANY_REDIRECTS error is pretty much what it sounds like: something is causing too many redirects, sending your website into an infinite redirection loop.
Essentially the site is stuck (such as URL 1 points to URL 2 and URL 2 points back to URL 1, or the domain has redirected you too many times) and unlike some other errors, these rarely resolve themselves and will probably need you to take action to fix it.
You might have also come across the error “request exceeded the limit of 10 internal redirects due to probable configuration error“.
|Error Type||Browser error/code error|
|Error Variations||This page isn’t working. domain.com redirected you too many times.
The page isn’t redirecting properly
This page isn’t working right now
Safari Can’t Open the Page
|Error Causes||Misconfigured WordPress settings/plugins
Issues with browser’s cache/cookies.
Issues with third-party services
Bad HTTPS settings
Bad server settings
The ERR_TOO_MANY_REDIRECTS error
The ERR_TOO_MANY_REDIRECTS error occurs as a result of a misconfiguration of redirects on your server, or incorrect settings with third-party services. This error is essentially what it implies: a loop of too many redirects is causing your website to be stuck in an endless cycle.
ERR_TOO_MANY_REDIRECTS: What Does It Look Like?
There are a couple of different variations of this error depending upon the browser you’re running.
In Google Chrome this error will show as ERR_TOO_MANY_REDIRECTS (as seen below) or This webpage has a redirect loop problem.
This page isn’t working. domain.com redirected you too many times.
(Check out how to fix Chrome’s ERR_CACHE_MISS error).
In Mozilla Firefox it will show as The page isn’t redirecting properly (as seen below).
An error occured during a connection to domain.com. This problem can sometimes be caused by disabling or refusing to accept cookies.
In Microsoft Edge, it will simply show as This page isn’t working right now (as seen below).
Domain.com redirected you too many times.
In Safari, it will show as Safari Can’t Open the Page (as seen below).
Too many redirects occurred trying to open “domain.com.” This might occur if you open a page that is redirected to open another page which is then redirected to open the original page.
What Causes the ERR_TOO_MANY_REDIRECTS Error?
This error happens when the browser can’t establish a connection between the initial page and the destination page in a redirect. The main causes can be:
- Misconfigured WordPress settings
- Misconfigured WordPress plugin.
- Misconfigured server settings.
- Incorrect HTTPS settings.
- Issues with the browser’s cache/cookies.
- Issues with third-party services (e.g. CDNs).
- Improper website or domain migration.
How To Fix the ERR_TOO_MANY_REDIRECTS Error?
Here are some recommendations and things to check to fix the error (sorted in order by most common reasons we see):
- Delete Cookies on That Specific Site
- Clear Server, Proxy, and Browser Cache
- Determine Nature of the Redirect Loop
- Check Your HTTPS Settings
- Check Third-Party Services
- Check Your WordPress Site Settings
- Temporarily Disable WordPress Plugins
- Check Redirects on Your Server
1. Delete Cookies on That Specific Site
Google and Mozilla both in fact recommend right below the error to “try clearing your cookies.” Cookies can sometimes contain faulty data in which could cause the ERR_TOO_MANY_REDIRECTS error. This is one recommendation you can try even if you’re encountering the error on a site you don’t own.
Due to the fact that cookies retain your “logged in” status on sites and other settings, we recommend simply deleting the cookie(s) on the site that is having the problem. This way you won’t impact any of your other sessions or websites that you frequently visit.
Follow the steps below to delete a cookie on a specific website in Google Chrome.
In Google Chrome click on the three small dots in the upper right-hand corner. Then click on “Settings.”
Scroll down and click on “Advanced.”
Then click on “Content settings.”
Click on “Cookies.”
Then click on “See all cookies and site data.”
Search for the site (domain) where you are encountering the ERR_TOO_MANY_REDIRECTS error. You can then delete the cookie(s) currently stored on your computer for that domain. Then try visiting the site again.
2. Clear Server, Proxy, and Browser Cache
Due to the fact that redirect loops are responses that can be cached, it’s always recommended to try clearing the cache on your WordPress site, the server, third-party proxy services, and even your browser if necessary.
Clear WordPress Site Cache
Depending upon the type of redirect loop, you might still be able to gain access to your WordPress admin dashboard. In this case, you can easily clear the cache within the settings of your caching plugin. Here are a couple of quick links on how to clear WordPress cache with popular plugins:
If you’re a Kinsta client, you can easily clear your cache from the WordPress admin toolbar.
Clear Server Cache
If you can’t access WordPress admin, many WordPress hosts have their own control panel tools for clearing the cache on your WordPress site.
Within the dashboard, click on WordPress Sites in the left sidebar navigation.
Click on your site name in the sites list and click on the Tools tab.
Click the Clear cache button to clear all cache.
Clear Proxy Cache
If you’re using a third-party reverse-proxy service such as Cloudflare or Sucuri, it can also be beneficial to clear the cache on their side.
To purge Cloudflare cache, login to their dashboard, click into “Caching” and click on “Purge Everything.”
To purge Sucuri cache, login to their dashboard, go to “Performance” and click on “Clear Cache.”
Clear Browser Cache
If you want to check and see if it might be your browser cache, without clearing your cache, you can always open up your browser in incognito mode. Or test another browser and see if you still see the ERR_TOO_MANY_REDIRECTS error.
If you determine it is being caused by your browser cache, you can then clear it. Below are instructions on how to do it in various browsers:
- How to Force Refresh a Single Page for All Browsers
- How to Clear Browser Cache for Google Chrome
- How to Clear Browser Cache for Mozilla Firefox
- How to Clear Browser Cache for Safari
- How to Clear Browser Cache for Internet Explorer
- How to Clear Browser Cache for Microsoft Edge
- How to Clear Browser Cache for Opera
3. Determine Nature of Redirect Loop
If clearing the cache didn’t work, then you’ll want to see if you can determine the nature of the redirect loop. Our free online Redirect Checker tool can help provide some further analysis into what might be going on. This could also be done via cURL.
For example, on the site below, it has a 301 redirect loop back to itself, which is causing a large chain of faulty redirects. You can follow all the redirects and determine whether or not it’s looping back to itself, or perhaps is an HTTP to HTTPS loop in which we’ll discuss how to solve that further below.
The Redirect Path Chrome extension can also be very useful and provides insights into all of the redirects happening on your site (specific URL or page.
4. Check Your HTTPS Settings
Another thing to check is your HTTPS settings. A lot of times we’ve seen ERR_TOO_MANY_REDIRECTS occur when someone has just migrated their WordPress site to HTTPS and either didn’t finish or set up something incorrectly.
Don’t Force HTTPS Without an SSL Certificate
This is by far the most common reason we see on a regular basis. If you force your WordPress site to load over HTTPS without first installing an SSL certificate, you’ll instantly throw your site into a redirection loop. To fix this, simply install an SSL certificate on your WordPress site.
It’s also recommended to run an SSL check. SSL/TLS certificates require not only your main certificate but also what they call intermediate certificates (chain) to also be installed. These need to be set up properly.
We recommend using the free SSL check tool from Qualys SSL Labs. It is very reliable and we use it for all Kinsta clients when verifying certificates. Simply head over to their SSL check tool, input your domain into the Hostname field and click on “Submit.” You can also select the option to hide public results if you prefer. It could take a minute or two to scan your site’s SSL/TLS configuration on your web server.
Don’t Use an SSL Plugin, Update your Hard-coded Links
There are some free SSL WordPress plugins, such as the Really Simple SSL plugin that will help you automatically redirect to HTTPS. However, we don’t recommend this method as a permanent solution because third-party plugins can always introduce another layer of problems and compatibility issues. It’s a good temporary solution, but you should really update your hard-coded HTTP links.
We have a great tutorial with 4 easy ways to do a search and replace in WordPress. If you’re a Kinsta client, you can always reach out to our support team to do this for you as well.
Check HTTP to HTTPS Redirects on Server
It could very well be that perhaps the HTTPS redirect rules on your server were misconfigured.
Redirect HTTP to HTTPS in Nginx
If your web server is running Nginx, you can easily redirect all of your HTTP traffic to HTTPS by adding the following code to your Nginx config file. This is the recommended method for redirecting WordPress running on Nginx.