ERR_TOO_MANY_REDIRECTS: Fixing the Loop

• HTTP → HTTPS → HTTP loop (CDN treats connection as HTTP)
• Cloudflare Flexible SSL (origin HTTP, edge HTTPS) + HTTPS redirect in WordPress
• WordPress/Bitrix: siteurl vs home mismatch — auto-redirect
• www → non-www in rule A, non-www → www in rule B
• HSTS client cache + stale reverse-direction redirect rule

1. In shell: curl -ILk https://example.com — see chain and loop point
2. Cloudflare: switch SSL/TLS encryption mode to Full (not Flexible)
3. WordPress: check wp_options → siteurl + home — must match
4. Clear HSTS cache: chrome://net-internals/#hsts → Delete domain
5. Bitrix: settings.php → "s1" → "server_name" — single canonical domain

Check the redirect chain →

• NET::ERR_CERT_AUTHORITY_INVALID
• ERR_SSL_PROTOCOL_ERROR
• SSL Handshake Failed
• All SSL errors

The ERR_TOO_MANY_REDIRECTS error occurs when a website enters a redirect loop, causing the browser to fail in loading the page. To resolve this, check your server configuration for conflicting redirect rules, clear browser cache, and ensure that your website's URL settings are correctly configured in CMS or server settings. For instance, verify the .htaccess file or Nginx configuration for any misconfigured directives.

Redirect loops happen when a URL redirects to another URL that eventually redirects back to the original URL, creating an infinite loop. This can stem from various sources, including:

• Server Configuration: Incorrectly configured web servers, such as Apache or Nginx, can create redirect loops. For example, if you have both www and non-www versions of your site, improper handling can lead to a loop.
• CMS Settings: Content Management Systems (CMS) like WordPress might have redirect settings that conflict with server settings. For instance, if your WordPress Address (URL) and Site Address (URL) differ and are incorrectly set, it can trigger this error.
• Termination Mismatch at a CDN: with Cloudflare Flexible SSL the edge speaks HTTPS while the origin is reached over plain HTTP, so the origin keeps redirecting to HTTPS and the edge keeps arriving over HTTP. The certificate is not the cause — the mismatch is where TLS terminates. Switching the mode to Full ends the loop.

To diagnose a redirect loop, you can use tools like Redirect Checker or browser developer tools to trace the redirect path. Analyzing the HTTP response codes can help pinpoint the issue.

To fix the ERR_TOO_MANY_REDIRECTS error, follow these practical steps:

1. Check .htaccess File (for Apache users): Open your .htaccess file and look for redirect rules. An example of a conflicting rule might look like:

RewriteEngine On
RewriteCond %{HTTP_HOST} ^example.com [NC]
RewriteRule ^(.*)$ https://www.example.com/$1 [L,R=301]

1. Review Nginx Configuration (for Nginx users): Check your Nginx configuration file (commonly located at /etc/nginx/sites-available/default). Look for any conflicting server blocks. An example of a potential issue:

server {
    listen 80;
    server_name example.com;
    return 301 https://www.example.com$request_uri;
}

server {
    listen 80;
    server_name www.example.com;
    return 301 http://example.com$request_uri;
}

1. Clear Browser Cache: Cached redirects can cause persistent issues. Clear your browser cache or test in incognito mode to see if the problem persists.
2. Examine CMS Settings: If using a CMS like WordPress, check the settings under General > Settings. Ensure that both the WordPress Address and Site Address are set to the same URL format (e.g., both with or without 'www').
3. Check SSL Configuration: If you have recently installed an SSL certificate, ensure that the HTTPS redirection rules do not conflict with existing HTTP rules. Use a tool like SSL Labs to test your SSL configuration.

After implementing the changes, be sure to restart your web server and clear your browser cache again. This should resolve the ERR_TOO_MANY_REDIRECTS error. If issues persist, consider consulting server logs for more detailed error messages.