Introduction
Running a self-facilitated WordPress.org site has got tons of advantages, yet now and again some effectively solvable mistakes can trouble the beginners. White screen of death, Internal server error, and some other normal WordPress errors can be truly worrying for new clients. As of late, a specific error has been troubling the users a lot and that error is ‘Too Many Redirects‘ error in WordPress. It is a typical issue that WordPress clients may run into from time to time.
In the event that you are seeing an "ERR_TOO_MANY_REDIRECTS" on your internet browser, you are not the only one. Numerous Windows clients have detailed that. This blunder happens with a message “This webpage has a redirect loop” and squares them from stacking the site. This issue generally happens when you are diverted from the first URL to another one however lamentably falls into a vast divert circle. The program identifies this circumstance, and it breaks the circle and demonstrates the error message. The reason behind the question as to why you are stuck in this circle can be the issue of the server or of the end client.
Today we shall see various approaches in which you can solve this commonly occurring error. The blog covers the following topics to help you in fixing this error.
What kind of error is this: ERR_TOO_MANY_REDIRECTS?
As it pursues from the name ERR_TOO_MANY_REDIRECTS, the main essence of the blunder lies in the way that your site enters a vast redirect cycle. Generally, the site quits working (URL 1 points to URL 2, and URL 2 points to URL 1, or space diverts you too often), and, in contrast to different mistakes, this issue itself isn’t fathomed, so you need to take a few activities to settle it.
There are a few variations of this blunder, contingent upon the program that you are working with.
Google Chrome
In Google Chrome, this blunder is shown as ERR_TOO_MANY_REDIRECTS or “This webpage has a redirect loop problem”.
Error text that you get: This page isn’t working. domain.com has redirected you too many times.
Mozilla Firefox
In Mozilla Firefox, the error is shown as “The page is not redirecting properly”.
Error content: Firefox has identified that the server is diverting the demand for this location in such a way that will never complete.
Microsoft Edge
In Edge, the blunder is shown as “Hmm… can’t reach this page”. Which, obviously, does not clarify the embodiment of the issue
Mozilla Firefox
If you’re using Mozilla Firefox, the error message will be seen as:
“The page isn’t redirecting properly.”
An error occurred during a connection to www.domain.com
- This problem can sometimes be caused by disabling or refusing to accept cookies.*
Safari
Safari will say: “Safari Can’t Open the Page”
“Too many redirects occurred trying to open “www.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.”
Bottom Line: As you can see, each browser makes it pretty clear that it’s a redirection issue.
Now, we’ve conveniently placed a * next to two lines, one in the Chrome window and one in the Mozilla window to grab your attention to the first and easiest possible solution to the issue of cookies.
Why do you get: Error Too Many Redirects in WordPress?
This blunder, for the most part, happens due to a misconfigured redirection issue. As you realize that WordPress has SEO amicable URL Structure which utilizes the divert work. A few other prevalent WordPress modules likewise utilize the divert usefulness. For instance, WordPress SEO module enables you to expel classification base from classification URLs by diverting clients to a URL without a class base. WordPress SSL and reserve modules additionally use redirects.
Because of a misconfiguration in any of these redirection devices, your site may wind up diverting clients to a URL that is really diverting them back to the alluding URL. All things considered, the client’s program is caught between two pages and consequently, you see the blunder.
List of ways to Fix this Error
Here is a list of ways that you can try to fix this error.
Clearing Cookies for the Website
Google and Mozilla prescribe endeavoring to clear website cookies, which is shown as proposals on the page with a blunder. Treats can once in a while contain incorrect information, which leads to the presence of ERR_TOO_MANY_REDIRECTS. You can attempt to pursue this suggestion, regardless of whether you notice such a misstep on a site that does not belong.
Cookie files hold the status of “logged in” on destinations and store different settings, thus we suggest that you just erase the treats for the site that prompted the blunder. This does not influence your different sessions and different locales that you regularly visit.
Follow these steps to clear the cookie in Chrome.
- In Google Chrome, tap on the catch with three specks in the upper right corner of the screen.
- Go to Settings.
- Scroll down and tap on Advanced.
- Choose Content settings.
- Click on Cookies
- Select See all cookies and site information
We are searching for the area for which the ERR_TOO_MANY_REDIRECTS mistake was shown. Erase cookies that are as of now put away on your PC for this area. We endeavor to visit the site once more.
Clean the Server, Proxy and Browser Cache
Redirection cycles are the appropriate responses that you can reserve, so we prescribe you attempt to clear the store on your WordPress site, in outsider intermediary administrations, and in your program.
A). Clean the server cache
Numerous WordPress web hosts offer their apparatuses to clear the reserve on your WordPress webpage. This is generally done from the control board of your hosting since the blunder most likely won’t enable you to get to the WordPress console.
B). Clean the proxy cache
On the off chance that you utilize a proxy server, for example, Cloudflare or Sucuri, you can attempt to clear their cache reserve.
C). Cloudflare
To clear the Cloudflare cache reserve, go to the administrative support, select Caching and snap Purge Everything.
D). Sucuri
To clear the Sucuri cache store, enter the administration support, select Performance and click on Clear Cache.
E). Clearing the browser cache
On the off chance that you need to see and check whether the issue is identified with the program reserve, you can basically open your program in incognito mode. You can test another program to check whether the mistake net::err_too_many_redirects has vanished or not.
Checking HTTPS Settings
Another explanation behind the ERR TOO MANY REDIRECTS blunder is HTTPS settings. We frequently observed that the blunder happens after the client moved his site to HTTPS and either did not finish the procedure or had set up something inaccurately.
i). Do not migrate to HTTPS without an SSL certificate.
We confront this issue all the time. On the off chance that you don’t introduce the SSL endorsement on the server, and in the meantime compel your site to stack on HTTPS, you will promptly enter an interminable circle of redirects. To settle this, simply introduce the SSL testament. We prescribe that you check that the SSL establishment is right. SSL/TLS declarations expect you to introduce the essential authentication, as well as the root and middle of the road endorsements (chains). Every one of them must be accurately introduced. Go to the SSL confirmation apparatus, enter your domain, and afterward run the sweep. To filter an SSL/TLS arrangement on your site, it might take some time (about a moment).
ii). Do not use the plug-ins for SSL, update the links prescribed in the code.
There are free modules that enable programmed redirection to HTTPS. Be that as it may, we don’t suggest this technique, since outsider modules lead to extra issues and similarity issues. This is just a transitory arrangement. You should physically refresh all HTTP interfaces in the code. To do this, you should play out a pursuit and supplant in WordPress.
iii). Check the redirects from HTTP to HTTPS on the server
It is conceivable that the redirect guidelines to HTTPS are mistakenly arranged on the server.
Redirect from HTTP to HTTPS for Nginx
In the event that your web server is running on Nginx, you can undoubtedly divert all traffic from HTTP to HTTPS utilizing the accompanying code that you have to add to the Nginx setup document. The prescribed strategy for diverting WordPress to Nginx is:
server { listen 80; server_name domain.com www.domain.com; return 301 https://yourdomain.com$request_uri; }Redirect from HTTP to HTTPS for Apache
In the event that your web server is running on Apache, you can divert your traffic from HTTP to HTTPS utilizing the accompanying code that you have to add to the .htaccess document. The prescribed strategy for diverting WordPress to Apache is:
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
iv). Check for the error “Too Many HTTPS Redirects”.
You may have such a large number of HTTPS redirects. You can check this with an exceptional instrument called Redirect mapper.
We check third-party services
net::err_too_many_redirects blunder is frequently connected with a turn around intermediary administrations, such as Cloudflare. This is more often than not because of the consideration of the Flexible SSL choice, in the event that you as of now have an SSL endorsement introduced on your server with WordPress. Why? At the point when Flexible SSL is chosen, all solicitations to your facilitating server are transmitted through HTTP. Undoubtedly, your facilitating server as of now has a divert with HTTP to HTTPS, and thus a cycle of redirects happens. To settle this, you have to change the Cloudflare Crypto settings from Flexible to Full or Full (strict).
Likewise, you can utilize their Always Use HTTPS rules for pages to redirect all clients to HTTPS without making a loop. Something else you have to pursue when working with Cloudflare is to pursue the redirection rules for URLs utilized for redirection. Be watchful with making a divert for spaces that show themselves as the goal. This can prompt an interminable redirect.
Check the Settings of your WordPress Website
You ought to likewise check the settings of your WordPress site. There are two fields that must be accurately characterized. Another famous oversight is that you utilize a mistaken prefix that does not coordinate your site (with www or without www).
- WordPress Address (URL): The address which is used to get to your blog.
- Site Address (URL): The address which is used to get to the principal WordPress documents.
The two URLs must match if, obviously, you didn’t transfer WordPress to a separate directory.
Probably, you won’t approach the WordPress support. You can overwrite these settings through the wp-config.php record. The wp-config.php record is typically situated in the base of your WordPress site. It very well may be gotten to by means of FTP, SSH or WP-CLI. To overwrite WP_HOME and WP_SITEURL, just enter the accompanying code at the highest point of wp-config.php by determining your domain:
define('WP_HOME','https://yourdomain.com');
define('WP_SITEURL','https://yourdomain.com');
Here is an example of how your wp-config.php will look after all the changes. The screenshot has been taken from the website – https://nestify.io/blog/fixing-err_too_many_redirects-wordpress-website/
Check the Redirects on the Server
Notwithstanding HTTP redirects to HTTPS on your server, you have to watch that there are no other ignorant redirects on the server. For instance, one bad 301 diverter may result in the site quitting. Generally, they are situated in the arrangement files of your server.
.htaccess File for Apache
On the off chance that you work with the hosting on which Apache is running, you should check the .htaccess document for erroneous guidelines. Pursue the means underneath to make a record starting with no third-party help.
Login to the site by means of FTP or SSH, at that point rename, .htaccess, to .htaccess_old. Accordingly, you will dependably have a reinforcement copy of the file
To re-make this document, you simply need to re-save your permanent connections in WordPress. Be that as it may, on the off chance that you experience ERR_TOO_MANY_REDIRECTS, you in all likelihood don’t approach your WordPress console. For this situation, you can make another .htaccess record and enter the accompanying substance into it. At that point transfer the record to the server. The standard settings for the document are:
# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule. /index.php [L]
# END WordPress
In the WordPress code, you can discover different models, specifically, the standard .htaccess for multisite.
Nginx Configuration
On the off chance that your facilitating utilizes Nginx, designing the setup document will be more entangled, since the config can be distinctively relying upon the facilitating supplier utilized. We prescribe for this situation to write in the help of facilitating and request that they check the design file for the things that can cause the cycle of redirects.
Check your Plugins
In the event that none of the means above tackled the redirection issue, probably this is identified with a portion of your plug-ins. There are numerous plug-ins that are putting forth some sort of redirection usefulness which may come in a struggle with some other redirection controls as of now set up by your web server setup.
A basic method to check if this issue is caused by a module is to briefly rename the “plug-ins” registry to something unique, for instance, “plugins_disabled”.
When you rename the plug-ins catalog, attempt to reload your WordPress site to check if the ERR TOO MANY REDIRECTS error is still there.
On the off chance that the blunder is still there, the issue is elsewhere and isn’t identified with any of your plug-ins. For this situation, you can rename your plug-ins catalog from “plugins_disabled” back to “plug-ins” so as to empower the majority of your plug-ins once more.
In the event that the error is gone after renaming the plug-in catalog, we are sure that it was caused by one of your plug-ins. So as to find which explicit module was in charge of this, we can empower all modules by renaming “plugins_disabled” back to “modules” and after that rename each of the modules inside this index one by one. Ensure you check your site after each module you incapacitate so as to recognize the one that is in charge of the redirection blunder.
Change Site URL Without Access to Admin Area
On the off chance that you don’t approach WordPress Admin region, you can, in any case, refresh these settings by characterizing them in the wp-config.php record. Basically, interface with your site utilizing an FTP customer. When you are associated with your site, you will discover a wp-config.php record in your site’s root registry. You have to download and alter this record utilizing a content manager like Notepad. Basically, add these two lines to the record and keep in mind to supplant example.com with your own domain:
define('WP_HOME','http://example.com');
define('WP_SITEURL','http://example.com');
Spare the document and transfer it back to your web server. Presently attempt to get to your WordPress site. On the off chance that you cannot access your site, attempt to include your domain with www prefix.
Correct your System’s Date and Time
In many cases, you see the ERR_TOO_MANY_REDIRECTS error due to the off-base or obsolete date and time settings on your framework. To address your frameworks date and time follow the steps given here-
- Press Win + R keys on your console to conjure Run box. Type “control” and press Enter.
- In the Control Panel, select Date and Time.
- Select the Internet Time tab, and after that tap on Change settings.
In Internet Time Settings, tick on Synchronize with an Internet time server and select a time server. At that point tap on Update now, and hit OK.
Conclusion
While sometimes the ERR TOO MANY REDIRECTS can be irritating, the above mentioned simple solutions would help you resolve the issue and get your website up and running again!
This error is most commonly caused by multiple misconfigurations or incompatibilities including URLs, caches, plugins, and so on. Troubleshooting the issue step by step will help you resolve the error and get an idea of what’s going on behind the scenes of your website, and what permits it to be functional.
Remember, that we recommend you try the solutions one by one, as we begin with the easiest and proceed with the slightly more challenging ways of solving the ERR_TOO_MANY_REDIRECTS issue. Opening the cache and cookies, for instance, is a go-to first solution for most browser error codes, including error messages like “Your Connection is Not Private and DNS_PROBE_FINISHED_NXDOMAIN.”
If you have tried every solution and the problem persists, don’t shy away from contacting your web host and asking for help. They can troubleshoot the redirection loop as well, and keep an eye on the cause of ERR_TOO_MANY_REDIRECTS. If you have a new approach to your WordPress admin dashboard. Along with that, you can also leave a support ticket in the WordPress repository permitting them to know and understand about your problem.
Feel FREE to share your Experience in resolving ERR_error in the below-mentioned comment section!
Interested in our Web Design & Development Services?
- Achieve Your Brand Vision
- Customer Engagement
- Customize UI
Leave a Reply