Website Redirect Loop: How to Fix Too Many Redirects

A website redirect loop produces a “too many redirects” message when repeated rules send the browser to another URL instead of returning the page. A common pattern is HTTP redirecting to HTTPS while another rule sends HTTPS back to HTTP. Record the affected URL and the time the error started before changing settings.

Trace the website redirect loop

Test the home page and one affected inner page in a private browser window. Note whether both fail and whether the address changes between www and non-www or HTTP and HTTPS. If you can inspect response headers, follow the Location values in the redirect chain to see which two URLs repeat. A private window helps rule out an old browser cookie, but it does not prove the server configuration is correct.

Compare WordPress and hosting URLs

In WordPress Settings, the WordPress Address and Site Address should use the intended domain and protocol. If the dashboard is inaccessible, check the configured values in the hosting environment before editing the database. A wrong URL can lock you out, so keep a copy of the current values and a working backup before changing them.

Find HTTPS rules behind a website redirect loop

Review redirects at the hosting control panel, web server, WordPress plugins and any CDN or proxy. Each layer should agree about the final HTTPS address. When a proxy handles HTTPS for visitors but connects to the origin using HTTP, an origin rule that forces HTTPS can create a loop if the proxy mode is incompatible. Confirm the proxy SSL mode and origin certificate before changing either.

Check recent plugin or migration changes

Redirect, security, SSL and cache plugins may each add rules. If the problem began after enabling one, review its redirect setting first. During a domain migration, inspect old-to-new redirects and avoid a reverse rule on the new domain. Change one rule at a time and retest the exact affected URL after each change.

Verify the website redirect loop fix

After correcting the website redirect loop, test the homepage, an inner page and the login screen. Confirm they settle on a single HTTPS address and that forms still work. Do not disable all redirects permanently: the site should still have one consistent canonical version.

If you need help tracing the chain, our website technical support and hosting assistance can inspect the conflicting rules. For symptoms that began after a move, see common WordPress migration problems.

Use the guidance for your proxy

If Cloudflare is in front of the site, compare the observed redirect chain with its too-many-redirects troubleshooting guide. The correct fix depends on how HTTPS is configured between the visitor, proxy and origin. Do not turn off certificate validation or send visitors to an insecure version of the site just to hide the error.