Too many redirects: untangle conflicting rules

What does this mean?

A redirect loop sends a browser between addresses until it stops following them. Common patterns include HTTP to HTTPS and back, www to the root domain and back, or login pages returning to themselves. Clearing cookies can help an account-specific problem, but it does not correct contradictory server rules.

What should I check first?

Copy the starting URL and test in a private browser window. In Developer Tools, open Network and preserve the request log while navigating once. Read the Location headers in sequence. Write down both the source and destination of each hop so you can identify the first repeated URL.

How can I diagnose the cause?

Compare redirect settings in the hosting panel, CDN, server configuration and CMS. A proxy can terminate TLS before forwarding traffic, so the origin may mistakenly believe the original request was HTTP. Confirm how the trusted proxy communicates the original scheme; never trust arbitrary forwarded headers without the host’s guidance.

How do I fix it safely?

Choose one canonical hostname and HTTPS, then remove the specific conflicting rule. Make a copy of existing settings before editing. On WordPress, confirm the configured site URLs match the intended public address. If a rule is in .htaccess, preserve unrelated security and application routing rules.

Verify the fix and know when to contact your provider

Retest all four host and scheme variants and a deep page with a query string. Each should reach the intended destination without revisiting a URL. Ask the hosting or CDN provider to check the proxy arrangement when application and edge settings disagree; share the observed hop sequence rather than only a screenshot.

Work through these checks in order

1. In the browser Network panel, enable Preserve log and navigate to the failing address once. For each 301, 302, 307 or 308 response, record the Location destination until you see a repeated address.
2. Compare the repeated pair with the hosting panel, CDN and CMS URL settings. If one rule adds www and another removes it, choose the intended canonical host and disable the exact conflicting rule.
3. Test http://domain/path, https://domain/path, and both www versions. A deep path and harmless query parameter should survive the canonical redirect, and no destination should send you back to the start.

Which tool can help?

Redirect checker (backend required) · HTTP header checker (backend required)

DNS tools show one resolver’s public answers. Record explainers do not authenticate a message, and calculators do not monitor a server. Use the evidence alongside your provider’s logs.