Troubleshooting "ERR_TOO_MANY_REDIRECTS"

The `ERR_TOO_MANY_REDIRECTS` error (often shown as "This page isn’t redirecting properly" or "The page isn't redirecting properly") occurs when your browser gets stuck in an infinite loop of redirects. This means Page A redirects to Page B, which redirects back to Page A, or through a longer chain that eventually leads back to a previously visited page.

What It Means

Redirects are normal web mechanisms used to send visitors from one URL to another (e.g., HTTP to HTTPS, old page to new page). However, when redirects are misconfigured, they can create a loop where the browser keeps getting sent back and forth between URLs without ever landing on a final destination. The browser detects this loop and stops, displaying the error.

Common Causes (Primarily Server/Configuration Issues)

  • Incorrect Server Configuration: Misconfigured rules in server files like `.htaccess` (Apache) or `nginx.conf` (Nginx) are common culprits, especially rules designed to force HTTPS or handle www/non-www versions of the domain.
  • CMS Settings Mismatch: In platforms like WordPress, having different URLs set for the "WordPress Address (URL)" and "Site Address (URL)" in the General Settings can sometimes cause loops, especially with HTTPS configurations.
  • Faulty Redirect Plugins: Plugins designed to handle redirects might be misconfigured or conflict with server settings.
  • CDN / Proxy Issues: Incorrect SSL settings or redirect rules configured in a Content Delivery Network (CDN) like Cloudflare or a reverse proxy can cause loops. For example, forcing HTTPS on the server while the CDN is also trying to force HTTPS can conflict.
  • Outdated Browser Cookies/Cache: Sometimes, old redirect information stored in your browser's cache or cookies can contribute to the loop.

How to Troubleshoot (If You're a Visitor)

  • Clear Browser Cookies and Cache: This is often the quickest fix if the issue is specific to your browser. Go into your browser settings and clear browsing data, specifically cookies and cached images/files for the affected site.
  • Try a Different Browser or Incognito Mode: This helps determine if the issue is related to your browser's stored data or extensions.
  • Check the URL: Ensure you haven't accidentally typed a URL known to cause redirects.
  • Wait and Retry: It's possible the website owner is currently fixing the configuration.

How to Fix (If You Own the Website)

  • Check Server Redirect Rules: Carefully examine your `.htaccess` (Apache) or Nginx configuration files for redirect rules (`Redirect`, `RedirectMatch`, `RewriteRule`, `return 301`, etc.). Look for conflicting rules, especially those related to HTTPS and www/non-www forcing. Temporarily commenting out rules can help isolate the problem.
  • Verify CMS URL Settings: In WordPress (or similar CMS), go to Settings > General and ensure the "WordPress Address (URL)" and "Site Address (URL)" are identical and correct (using the right protocol - HTTPS, and the correct www/non-www version). If you can't access the admin area, you might need to define these in `wp-config.php`:
    define( 'WP_HOME', 'https://yourdomain.com' );
    define( 'WP_SITEURL', 'https://yourdomain.com' );
  • Check CDN/Proxy Settings: Review SSL/TLS settings in your CDN (e.g., Cloudflare's SSL/TLS mode - "Full (Strict)" is generally recommended if your server has a valid certificate) and any redirect rules ("Page Rules" in Cloudflare). Ensure they don't conflict with server-side redirects.
  • Deactivate Redirect Plugins: If you use plugins to manage redirects, temporarily disable them (via admin dashboard if accessible, or by renaming the plugin folder via FTP/File Manager) to see if the error resolves.
  • Check HTTPS Configuration: Ensure your SSL certificate is correctly installed and that redirects from HTTP to HTTPS are set up correctly *once* (either at the server level or CDN level, usually not both in a conflicting way).
  • Use Redirect Checker Tools: Online tools can trace the redirect path for a URL, making it easier to spot where the loop occurs.
  • Clear Server Caches: If you use server-level caching, clear it after making configuration changes.