ERR_TOO_MANY_REDIRECTS
ERR_TOO_MANY_REDIRECTS Error
What This Error Means
The ERR_TOO_MANY_REDIRECTS error, also known as a redirect loop, occurs when the website keeps redirecting the browser between different URLs in an infinite circle. For example, URL A redirects to URL B, which redirects back to URL A. The browser detects this loop and stops loading the page to prevent crashing. This is almost always a server-side configuration issue, though client-side caches can sometimes retain old redirect rules.
Common Causes
- An HTTP to HTTPS loop happens when the server forces HTTPS, but the application or a proxy like Cloudflare sends requests back to HTTP, causing an infinite loop.
- A WordPress URL mismatch occurs when the Site Address and WordPress Address settings in the dashboard do not match the actual protocol or domain being accessed.
- Using Flexible SSL mode on Cloudflare while the origin server forces HTTPS causes a loop because Cloudflare sends HTTP to the origin, which redirects back to HTTPS.
- Conflicting rewrite rules in .htaccess or Nginx configuration files can redirect a page to itself or a parent directory repeatedly.
- SEO or Redirection plugins in WordPress often fight over how a URL should be handled, creating circular logic.
How to Fix It (For Users)
- 1 Before assuming the site is broken, try these steps to rule out local issues.
- 2 Clear cookies for the site, as old cookies might be storing a session that is stuck in a redirect loop.
- 3 Try loading the page in Incognito or Private mode to see if the issue is caused by your browser cache or extensions.
- 4 Disable VPNs, privacy extensions, or tools like HTTPS Everywhere to see if they are forcing a protocol that causes the conflict.
For Site Owners / Developers
- Check redirect chains using the command line to see exactly what is happening. Run curl -I -L your-site.com to inspect the headers.
- If you use Cloudflare, log in and check your SSL/TLS settings. If it is set to Flexible, change it to Full or Full (Strict).
- Check your wp-config.php file to ensure you aren't hardcoding WP_HOME or WP_SITEURL to HTTP if you have an SSL certificate.
- Rename your .htaccess file to .htaccess_backup to disable it. If the site loads, the error is in your rewrite rules.
- If you are using a load balancer or proxy, ensure it is passing the X-Forwarded-Proto header correctly and your application is configured to trust it.
When It Is NOT Your Fault
If you are a visitor, this is rarely your fault unless your browser is aggressively caching an old redirect. If clearing cookies doesn't fix it, the website administrator must resolve the server configuration.
Is the website actually down?
Sometimes the issue is just on your end. Check if the website is down for everyone or just you.
Check Website Status →