WordPress Redirect Loop: Fixing ERR_TOO_MANY_REDIRECTS

Short answer: something is redirecting the request in a circle. Two rules disagree about the canonical address — usually about HTTPS, or about whether the domain includes www. The browser stops after a set number of hops and reports the loop.

Confirm the two addresses first

Open Settings › General and check that WordPress Address and Site Address match exactly — same protocol, same www choice. A mismatch here (for example site set to http:// while the server forces https://) is the single most common cause of the loop.

Where the conflict usually lives

• Site/home URLs disagreeing with a server redirect rule.
• An HTTPS redirect at the CDN while the origin still redirects to HTTP — a classic Cloudflare “Flexible SSL” loop; set it to Full instead.
• A www-to-non-www rule duplicated in two places, in opposite directions.
• A caching or security plugin adding its own canonical redirect.
• A reverse proxy not passing the original protocol, so WordPress thinks HTTPS requests are HTTP and redirects them.

Trace the chain, do not guess

1. Follow the redirect chain and record each hop and its target; the point where the address repeats identifies the conflicting pair.
2. If a proxy sits in front (Cloudflare, a load balancer), add define('FORCE_SSL_ADMIN', true); and the HTTP_X_FORWARDED_PROTO handling to wp-config.php so WordPress detects HTTPS correctly.
3. Test with cookies cleared — a login-only loop is often a cookie or domain mismatch, not a redirect rule.
4. Temporarily rename the plugins folder to rule a plugin in or out.

Fix one layer, then verify all four combinations

Decide the single canonical form and make exactly one layer enforce it. Then test all four of http/https and www/non-www — each should reach the canonical address in one redirect — and confirm you can log in and stay logged in, since admin loops often survive a fix that only addressed the front end.