The ERR TOO MANY REDIRECTS Error and How to Fix It?
Tags: sslcertificate, cheapcodesiging, codesigningcertificate
Published: 2022-06-19 14:53:31

We see a number of different errors, and one of the most common is err_too_many_redirects (also known as a redirect loop). The too many redirects error  usually happens after a recent change to your website, a server redirection misconfiguration, or incorrect settings with third-party services. But don’t worry, this is a simple problem to correct.

Check out the tips below on how to fix this mistake and get your site up and running again.

What does ERR TOO MANY REDIRECTS stand for?
 

The cause of ERR TOO MANY REDIRECTS is exactly what it sounds like: something is producing too many redirects, resulting in an unending redirection loop on your website.

 

In essence, the site is stuck (for example, if URL 1 points to URL 2 and URL 2 points back to URL 1, or if the domain has redirected you too many times), and unlike some other issues, these rarely resolve themselves and will almost certainly require you to take action to rectify them.

 

You may have also seen the message “request exceeded the limit of 10 internal redirects owing to a possible setup problem.”

Depending on the browser you’re using, there are a few distinct variations of this issue.

1.     Chrome by Google
 

This error will appear as ERR TOO MANY REDIRECTS (as seen below) or This webpage has a redirect loop problem in Google Chrome or Google images too many redirects

 

This page is not accessible. You were forwarded too many times by domain.com.
Google Chrome’s ERR TOO MANY REDIRECTS error
 

2.     Firefox by Mozilla
 

It will appear in Mozilla Firefox as The page isn’t redirecting properly (as seen below).

A connection to domain.com failed due to an issue. Disabling or refusing to accept cookies might sometimes create this issue.

It will just say This page isn’t working right now in Microsoft Edge (as seen below).

 

You were forwarded too many times by Domain.com.
Microsoft Edge: ERR TOO MANY REDIRECTS
3.     Safari
 

Safari will display the message Safari Can’t Open the Page (as seen below).

When trying to open “domain.com,” there were too many redirects. This could happen if you open a website that is routed to another page, which is then diverted to the original page.

Safari’s ERR TOO MANY REDIRECTS error

 

Here are some suggestions and things to look for to fix the problem (in order of the most common causes we see):

 

Delete cookies from that website.
Clear the caches on your WordPress site, server, proxy, and browser.
Determine the redirect loop’s nature.
Check your HTTPS configuration.
Look into third-party services.
Check the settings on your WordPress site.
Disable WordPress plugins temporarily.
Check your server’s redirects.
Delete Cookies from That Website
 

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. Even if you’re getting the problem on a site you don’t own, you can try this suggestion.

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.
 

Step 1

In Google Chrome click on the three small dots in the upper right-hand corner. Then click on “

The ERR TOO MANY REDIRECTS Error and How to Fix It?

 

We see a number of different errors, and one of the most common is err_too_many_redirects (also known as a redirect loop). The too many redirects error  usually happens after a recent change to your website, a server redirection misconfiguration, or incorrect settings with third-party services. But don’t worry, this is a simple problem to correct.

Check out the tips below on how to fix this mistake and get your site up and running again.

What does ERR TOO MANY REDIRECTS stand for?
 

The cause of ERR TOO MANY REDIRECTS is exactly what it sounds like: something is producing too many redirects, resulting in an unending redirection loop on your website.

 

In essence, the site is stuck (for example, if URL 1 points to URL 2 and URL 2 points back to URL 1, or if the domain has redirected you too many times), and unlike some other issues, these rarely resolve themselves and will almost certainly require you to take action to rectify them.

 

You may have also seen the message “request exceeded the limit of 10 internal redirects owing to a possible setup problem.”

Depending on the browser you’re using, there are a few distinct variations of this issue.

1.     Chrome by Google
 

This error will appear as ERR TOO MANY REDIRECTS (as seen below) or This webpage has a redirect loop problem in Google Chrome or Google images too many redirects

 

This page is not accessible. You were forwarded too many times by domain.com.
Google Chrome’s ERR TOO MANY REDIRECTS error
2.     Firefox by Mozilla
 

It will appear in Mozilla Firefox as The page isn’t redirecting properly (as seen below).

A connection to domain.com failed due to an issue. Disabling or refusing to accept cookies might sometimes create this issue.

It will just say This page isn’t working right now in Microsoft Edge (as seen below).

 

You were forwarded too many times by Domain.com.
Microsoft Edge: ERR TOO MANY REDIRECTS
3.     Safari
 

Safari will display the message Safari Can’t Open the Page (as seen below).

When trying to open “domain.com,” there were too many redirects. This could happen if you open a website that is routed to another page, which is then diverted to the original page.

Safari’s ERR TOO MANY REDIRECTS error

 

Here are some suggestions and things to look for to fix the problem (in order of the most common causes we see):

 

Delete cookies from that website.
Clear the caches on your WordPress site, server, proxy, and browser.
Determine the redirect loop’s nature.
Check your HTTPS configuration.
Look into third-party services.
Check the settings on your WordPress site.
Disable WordPress plugins temporarily.
Check your server’s redirects.
Delete Cookies from That Website
 

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. Even if you’re getting the problem on a site you don’t own, you can try this suggestion.

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.
Step 1

In Google Chrome click on the three small dots in the upper right-hand corner. Then click on “Settings.”

Step 2

Scroll down and click on “Advanced.”

Step 3

Then click on “Content settings.”

Step 4

Click on “Cookies.”

Step 5

Then click on “See all cookies and site data.”

Step 6

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.

 

Delete cookie in Chrome
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.

If you can’t access WordPress admin, many WordPress hosts have their own control panel tools for clearing the cache on your WordPress site.

Clear WordPress cache
Clear WordPress cache
Clear Proxy Cache