How to Fix ERR_TOO_MANY_REDIRECTS

ERR_TOO_MANY_REDIRECTS means a website keeps sending your browser from one address to another in a loop until Chrome gives up. The message usually reads “This page isn’t working” and “redirected you too many times”. The cause is either a bad cookie in your browser or a redirect rule on the site itself, so this guide covers both.

What causes too many redirects

• A damaged or outdated cookie stored for that site in your browser.
• A site address that mixes http and https, so each version redirects to the other.
• A security or caching plugin that forces HTTPS while the server also forces it.
• A CDN or proxy, such as Cloudflare, set to a mode that conflicts with the server’s redirects.
• A faulty rule in the .htaccess file.

1. Clear cookies for the site (visitors)

In Chrome, open the padlock or settings icon next to the address, choose Cookies and site data, then Manage on-device site data, and delete the entries for the site. You can also open Settings > Privacy and security > Third-party cookies > See all site data and permissions, search for the site and delete its data. Reload the page.

2. Test in Incognito and another browser (visitors)

Open the site in an Incognito window. If it loads, an extension or stored data is the cause. Disable extensions one at a time. If it fails in every browser and on other devices, the problem is on the website, so contact the site owner.

3. Check the WordPress address settings (site owners)

In the WordPress dashboard, go to Settings > General and check that WordPress Address (URL) and Site Address (URL) both use the same scheme, normally https://, and the same form of the domain (with or without www). If you cannot log in, you can set them in wp-config.php above the stop-editing comment:

define( 'WP_HOME', 'https://example.com' );
define( 'WP_SITEURL', 'https://example.com' );

Replace example.com with your own domain and keep a backup of the file.

4. Check HTTPS and CDN settings (site owners)

If you use Cloudflare, a common cause is the SSL/TLS mode set to Flexible while the server also redirects to HTTPS. Cloudflare then talks to the server over http, the server redirects to https, and the loop begins. Change the mode to Full or Full (strict) once your server has a valid certificate. Also make sure only one thing, your server, a plugin or the CDN, forces HTTPS.

5. Deactivate redirect and caching plugins (site owners)

If you can reach the dashboard, deactivate any plugin that handles HTTPS, redirects, security or caching and test. If you cannot log in, rename the wp-content/plugins folder to plugins-off using File Manager or FTP, test, then rename it back and reactivate plugins one by one. Clear the plugin and server cache when you finish.

6. Reset the .htaccess file (site owners on Apache)

Rename .htaccess to .htaccess-old and reload the site. If it loads, go to Settings > Permalinks in the dashboard and select Save Changes to create a clean file. If you had custom rules, add them back one at a time.

Frequently asked questions

Is it my computer or the website?

Try another browser and another device. If it fails everywhere, the problem is on the website. If it only fails in one browser, clear that browser’s cookies for the site.

Can I fix this on a site I do not own?

Only clearing cookies and testing another browser are in your control. Otherwise tell the site owner.

Why did it start after I installed an SSL certificate?

Mixed http and https settings are the usual cause. Make the site address and the CDN mode consistent.

When to contact support

If you own the site and the loop continues after steps 3 to 6, contact your host and mention the exact redirect behaviour. If you hit the error on a site you do not own, contact the site’s support. For a full site crash, see how to fix the WordPress critical error.