WordPress is, for the most part, a reliable content management system that can be used with very little trouble. Where problems do arise, these can generally be rectified within a matter of minutes. One problem that has bothered a number of users over the years, however, has proven rather more troublesome to fix. ‘Too Many Redirects’, also known as ‘Error 310’, typically occurs due to a reconfiguration error caused by one or more of the redirection tools on your website. The SEO-friendly URL structure that WordPress uses relies on redirect functionality as do many popular plugins.
When users encounter a Too Many Redirects problem, a message will be displayed in the web-browser, which explains that the webpage is unable to redirect. Fortunately, like all other problems in WordPress, there is a way to solve this error without too much trouble.
Solving the Too Many Redirects Problem
The most common reason for the Too Many Redirects problem is due to an issue with the user’s WordPress Address (URL) and Site Address (URL) fields within the General Settings of their site.
Most WordPress web hosts allow you to decide whether you would like to add the www prefix to your chosen URL or not. If you chose to add or opt not to use this prefix and then add the opposite in your WordPress settings, an error will occur.
With the wrong settings in place, a user intending to visit http://yourwebsite.com could be directed to http://www.yourwebsite.com by your server’s configuration and then back to http://yourwebsite.com by WordPress due the settings you have in place – it is a complicated process for what is a simple error.
To solve the problem go to Settings > General in your WordPress dashboard and change the WordPress Address (URL) and Site Address (URL) settings accordingly. If you have the www prefix on your address change the settings to look like http://yourwebsite.com. If you don’t have the www prefix, do the opposite.
Solving the Too Many Redirects Problem via FTP
If you are unable to access your WordPress dashboard, you will need to solve the problem by accessing the wp-config.php file in your WordPress database. You can do this by logging into your database via an FTP client.
Once you have access to your database, download the wp-config.php file and edit it using Notepad (or whichever text editor you use). In Notepad, add the following two lines of code to the fine, replacing yourwebsite.com with the appropriate URL:
1 | define('WP_HOME','http://yourwebsite.com');
2 | define('WP_SITEURL','http://yourwebsite.com');
Upload the file back to your WordPress database close the FTP client. You should now be able to regain access to your site.