How to Fix Error Too Many Redirects Issue in WordPress
Having a self-hosted WordPress.org site is good, but sometimes some easily fixable errors can prove to be annoying to newbies. Errors like the White screen of death and Internal server error can be really stressing for new users. It is a common issue that WordPress users may come across. In this article, we will show you how to fix unwanted redirects issue in WordPress.
On Firefox, this error will be displayed like this:
“The page isn’t redirecting properly. Firefox has detected that the server is redirecting the request for this address in a way that will never complete.”
What causes Error Too Many Redirects in WordPress?
This usually occurs due to a misconfigured redirection issue. We know that WordPress has SEO friendly URL Structure which uses the redirect function. Several other popular WordPress plugins also use the redirect function. For example, WordPress SEO plugin allows you to remove category base from category URLs by redirecting users to a URL without category base. WordPress SSL and cache plugins also use redirects.
If any of these redirection tools get misconfigured, your site may end up redirecting users to a URL that is actually redirecting them back to the referring URL. In that case the user’s browser is trapped between two pages and hence you see the error.
How to Solve Too Many Redirects Error in WordPress?
The most common misconfiguration that occurs repeatedly is when a user has incorrect URL in WordPress Address URL or Site Address URL settings.
Suppose that your site’s url is
http://www.example.com and you go to Settings » General and set it to
http://example.com. Most web hosts allow you to choose whether you would like to add a www prefix to your domain name or have it without www. In case you had selected to add www to your URL, then adding http://example.com in your WordPress settings will cause the error. Or if you opted to use your domain without www prefix, then adding it with www prefix in WordPress settings will cause this error.
When a user will come to
http://example.com, they will be redirected by your server’s configuration to http://www.example.com where they will be redirected back to
http://example.com by WordPress because that’s what you have set up in the settings.
If your site was working fine, and you did not make any changes to those settings. Then you need to contact your web host, because it is most probably a configuration issue at their end.
However, if you do not have a reliable WordPress hosting provider, and they deny having any issues and/or refuse to help you, then you should consider switching web hosts or fix it yourself.
To fix this, you need to change your WordPress Address and Site Address. Go to Settings » General, change your WordPress and Site Address. If you have your address with www prefix, then change it to non-www URL, and if you have it with non-www URL then add the www prefix.
Important: Make sure that you don’t leave a trailing slash at the end of your URL like
Change Site URL Without Access to Admin Area
In case you don’t have access to WordPress Admin area, you can still update these settings by defining them in the wp-config.php file. Simply connect to your website using an FTP client. Once you are connected to your site, you will find the wp-config.php file in your site’s root directory. You need to download and edit this file using a text editor like Notepad. Just add these two lines to the file and don’t forget to replace example.com with your own domain.
Save the file and upload it back to your web server. Now try to access your WordPress site. If you still can not access your site, then try to add your domain with www prefix.
Fixing Other Redirect Issues
If the not solve your problem, then it is likely that there is a plugin issue with your site. As we mentioned earlier that several WordPress plugins use redirection techniques to do a variety of things. We will try to help you troubleshoot.
First you need to figure out is which plugin is causing the issue. Did you activate a new plugin recently right before this error happened? Did you update plugins right before this error happened? If the answer to any of the above questions is YES, then it narrows the problem down to that plugin. You can simply deactivate that plugin by deleting that plugin’s folder from wp-content/plugins/
If you do not know which plugin is causing the issue, then you would need to do some trial and error. The best way to do this is to deactivate all plugins. After deactivation of all plugins on your site, you need to use FTP to download the .htaccess file as a backup. You can find this file in your site’s root directory. Once you have downloaded the file, delete it from your server. Now try to access your site.
This process will allow your server to regenerate a new .htaccess file, and since there are no plugins activated, it will most likely fix the issue. If the error is gone now, then you know for certain that it was a plugin causing this error.
The next step is to find out which plugin was causing the error. To do this, you need to download and install fresh copies of all your plugins. Activate plugins one at a time and after activating each plugin try to browse several pages on your site using a different browser as a non-logged in user. Hopefully you will find the plugin that caused the issue.
Latest posts by sarah ali (see all)
- How to Get Started with A/B Testing for WordPress - June 23, 2017
- Top 5 CDN Providers for WordPress: 2017 - June 22, 2017
- How to Create an Admin User in WordPress Database via MySQL. - June 20, 2017