There are always two sides to a coin. This is definitely true with WordPress, as it has its fair share of positive and negative things. The flexibility and ease-of-use is amazing, but it comes with quite a few potential issues and errors that you might have to deal with. Such errors include Internal server error, White screen of death, and too many redirects. These errors can cause stress and frustration for beginners who aren’t still familiar with the ins and outs of WordPress. Running into errors is inevitable, but most of these errors are easy to resolve, especially the too many redirects one.
Table of Contents
What causes too many redirects error in WordPress?
On Firefox, the error shows up 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.”
Usually, this error is caused by a not properly configured redirection issue.
Aside from WordPress itself, the redirect function is also used by some WordPress plugins which include WordPress SEO plugin, WordPress SSL plugins, and caching plugins.
When there is a misconfiguration in one of these redirection tools, users who are trying to access your site might end up being redirected back to the referring URL. When this happens, the browser of the user basically freaks out, and that’s when the following error happens.
How to Solve The Too Many Redirects Error in WordPress?
The most usual misconfiguration experienced by almost everyone is an incorrect URL in WordPress Address URL or Site Address URL settings. (in Settings > General)
For example, you own a website with https://blabla.com as the URL. If add www. to your URL in WP, then the error will pop up.
If a user will access https://blabla.com, the user will be redirected to http://www.blabla.com and will be redirected again to https://blabla.com by WordPress. Why will this happen? Technically, this is because that is what you have set up in the settings. If you haven’t changed anything in these settings, then it’s time to look somewhere else (eg. contact your web host and ask for help).
If you know you changed something in that Admin section of your back-end (again, in Settings > General), which probably means you can’t even access the back-end anymore, AND your web host isn’t being helpful. You need to 1. change your setting back in a different way, and 2. change your web hosting provider.
Change Site URL Without Access to Admin Area
There are cases wherein users don’t have access to the admin area of WordPress. In such case, these settings can still be updated by simply defining them in the wp-config.php file. To make this possible, all you have to do is connect to your website using an FTP client where you will find the wp-config.php file in your site’s root directory. What you are going to do next is to download and edit the file. After which, add the following code to the file:
But of course, don’t forget to change mangomattermedia.com with your own URL. Finally, save the file and upload it again to your web server (or if the host uses cPanel, you can do it all through the file manager).
Fixing Other Redirect Issues
If the abovementioned solutions did not work, most probably, your site has a plugin issue.
If this happens, the first thing that has to do is to find out which among the plugins is causing the problem. Think of when the error first happened and remember what you might have changed. You might have added a new plugin or you might have updated an existing one. You can just delete the plugin folder which is causing the error in the wp-content/plugins/, and ti should be fixed.
What if you don’t know which plugin is causing the error? Then the trial and error method is recommended. To simplify the process, start renaming plugins to something else, like add _old to the folder, that should de-activate them. You can rename the plugins one by one to find out which among them is causing the error. Once you find the bad apple, rename the good ones back, log in to your admin, and re-activate them. It’s strongly recommended to also back-up and then delete the htaccess file in the root, as some plugins write redirect lines in there that could be the issue. WP will automatically create a new htaccess file once the site is live again anyway :). You can then even compare the old and new htaccess file and see if you can find the code that caused the issue… it’s another way to find the bad plugin quickly.
Either way, all of the above shouldn’t be necessary if your web host can help you out (which they should!).
Rebecca’s strengths are in SEO and data analysis, but she also knows her way around WordPress pretty well, and is in charge of finding specific WordPress problems that people have, and then offer solutions.
Check our about page for more info.