ERR_TOO_MANY_REDIRECTS

What Does ERR_TOO_MANY_REDIRECTS Mean?

ERR_TOO_MANY_REDIRECTS occurs when a website sends your browser through an infinite loop of redirects. When you visit a URL, the server can redirect you to a different URL. That URL can then redirect you to yet another URL, and so on. Browsers have a built-in limit (typically 20 redirects) to prevent infinite loops, and when this limit is exceeded, they display the ERR_TOO_MANY_REDIRECTS error.

Redirects are a normal part of how the web works. They are used to send users from HTTP to HTTPS, from www to non-www versions of a domain, from old URLs to new ones, and for authentication flows. Problems arise when the redirect chain forms a loop: URL A redirects to URL B, which redirects back to URL A, creating an infinite cycle that never reaches an actual web page.

This error is almost always a server-side configuration problem rather than a client-side issue. However, corrupted cookies on the client side can sometimes contribute to redirect loops, especially when the website uses cookies to determine whether to redirect. This is why clearing cookies often resolves the issue even though the root cause is typically server-side.

Common Causes

The most common cause is conflicting redirect rules in the server configuration. For example, one rule redirects HTTP to HTTPS while another redirects HTTPS back to HTTP, creating an infinite loop. Similarly, one rule might redirect non-www to www while another redirects www to non-www. These conflicts often occur when redirect rules are set in multiple places (web server config, .htaccess, application code, or CDN settings).

SSL/HTTPS configuration issues frequently cause redirect loops. When a website is behind a reverse proxy or CDN (like Cloudflare) that handles SSL termination, the web server may see incoming requests as HTTP and redirect them to HTTPS. But the CDN converts the HTTPS request back to HTTP before forwarding it to the server, creating a loop. Misconfigured SSL certificates or mixed-content issues can also trigger redirect loops.

CMS and application-level issues can cause redirect loops too. WordPress sites are particularly prone to this when the site URL settings do not match the actual domain, when plugin conflicts create contradictory redirect rules, or when caching plugins serve stale redirect responses. Authentication systems can create loops when they redirect unauthenticated users to a login page that itself requires authentication cookies that cannot be set.

Step-by-Step Fix

Start by clearing your browser cookies for the affected website. In Chrome, click the lock icon next to the URL, go to Site Settings or Cookies, and delete all cookies for that domain. Then reload the page. If this fixes the issue, a corrupted cookie was contributing to the redirect loop.

If clearing cookies does not help, the problem is server-side. If you are the site owner, check your server configuration for conflicting redirect rules. Review your .htaccess file, web server configuration (Nginx or Apache config), application settings, and CDN rules. Make sure you do not have contradictory rules (like both HTTP-to-HTTPS and HTTPS-to-HTTP redirects). If using a CDN like Cloudflare, ensure the SSL mode matches your server's configuration (use Full or Full Strict if your server has a valid SSL certificate).

For WordPress sites, check the WordPress Address and Site Address in Settings > General to ensure they match your actual domain and use the correct protocol (http or https). Disable all plugins by renaming the plugins folder via FTP and check if the redirect loop stops, then re-enable plugins one by one to find the culprit. For other CMS platforms, review the application's URL and redirect settings. Use our HTTP Headers tool to inspect the redirect chain and identify where the loop occurs.

Related Network Errors