Black FridayCyber Monday 2026
13Days
14Hrs
16Mins
32Secs
Flat20% OFF

Our biggest sale of the year20% off the first payment on all maintenance plans. Code BF2026

Grab the deal
WordPress

ERR_TOO_MANY_REDIRECTS in WordPress: Find the Redirect Loop

A redirect loop means two rules keep sending the browser to each other. Learn how to check URL settings, HTTPS rules, a CDN and plugins in a safe order.

wpallsolution Updated 7 min read

ERR_TOO_MANY_REDIRECTS in WordPress is the message Chrome shows when a page keeps sending the browser to another address that sends it back again, until the browser gives up. Other browsers word it differently, for example “The page isn’t redirecting properly”. The loop is almost always caused by two rules that disagree about the correct address, such as HTTP versus HTTPS or www versus non-www. This guide shows how to find those two rules and keep only one.

Quick answer

A redirect loop means rule A sends visitors to address B, and rule B sends them back to address A. Common pairs are the WordPress address settings against a server HTTPS rule, a CDN SSL mode against an origin redirect, and a redirect plugin against a rule in .htaccess. Start by clearing cookies, check that the Home and Site addresses match, check your CDN mode, make sure only one thing forces HTTPS or www, and then look at plugins and .htaccess.

How this guide was prepared: it is research-based. We used the WordPress developer documentation and the Cloudflare documentation listed under Sources, checked on October 23, 2026. We did not reproduce your loop on a live site, and your host or CDN may behave differently, so change one thing at a time and keep a backup.

What a redirect loop is

A redirect is a server answer that says “this page now lives at another address”. Browsers follow a chain of these but stop after a limit. In WordPress a loop usually involves the address stored in the settings, a rule that forces a certain scheme (https) or host (www), and sometimes a CDN in front of the site. Because several layers can each add a redirect, the same site can work for one visitor and loop for another, or loop only after you switch HTTPS on.

The decision tree: which two rules are fighting?

Flowchart for ERR_TOO_MANY_REDIRECTS in WordPress: five questions about cookies, site addresses, CDN SSL mode, duplicate HTTPS rules and recent changes
Five questions point to the two rules that are fighting.
  1. Fails only in your browser or on one device? Clear site cookies and test a private window (Step 1).
  2. Home and Site addresses do not match? Make them identical (Step 2).
  3. Using Cloudflare or another CDN with HTTPS? Check the SSL mode (Step 3).
  4. Two things force HTTPS or www? Keep one rule (Step 4).
  5. Started after a plugin or .htaccess change? Undo it or regenerate the rules (Step 5).

Symptoms and likely causes

What you seeLikely causeStart with
Loop only on your own deviceA stale cookie or cached redirectStep 1
Loop right after you added an SSL certificate or switched to HTTPSAddress settings or redirect rules disagree about the schemeSteps 2 and 4
Loop only when the CDN is onCDN SSL mode does not match the origin redirectStep 3
Loop after installing or changing a redirect or security pluginA plugin rule fights a server ruleStep 5
Loop only for non-www (or www)Two host rules point at each otherSteps 2 and 4

5 steps to fix ERR_TOO_MANY_REDIRECTS in WordPress

Step 1: Rule out your browser

Open the site in a private window and from another device or network. If it loads there, delete the cookies and cached data for your site in your browser and try again. A loop that appears only for you is a local problem, and the steps below are not needed.

Step 2: Make the Home and Site addresses match

WordPress stores two addresses: the WordPress Address (where the core files live) and the Site Address (what visitors type). The developer documentation says both should include https:// when you use HTTPS and should not end with a slash. If they disagree about the scheme or about www, a redirect plugin or server rule may keep correcting one to the other. Check them under Settings → General. They can be hard coded with WP_HOME and WP_SITEURL in wp-config.php, and then the screen cannot edit them. If you are locked out, WP-CLI can read and set the values with wp option get home, wp option get siteurl and wp option update, after you back up the database.

Step 3: Check your CDN or proxy SSL mode

Cloudflare documents the usual loops. In Flexible mode Cloudflare talks to your server over plain HTTP, so if your server redirects HTTP to HTTPS, the two keep bouncing. The fixes are to remove the HTTPS redirect from the server or to use Full or Full (strict), which need an SSL certificate on the origin (a valid one for strict). In Full modes a loop appears instead if the origin redirects HTTPS back to HTTP. Cloudflare also lists Always Use HTTPS, HSTS and redirect or page rules as other loop sources. Other CDNs have similar settings, so read yours.

Step 4: Keep only one redirect rule

List every place that can force HTTPS or a host: the .htaccess file or server configuration, your host’s “force HTTPS” switch, an SSL or redirect plugin, your SEO plugin’s redirects, and your CDN. Keep one authority and switch the others off. Then test the chain from the command line with curl -sIL https://yourdomain.com and read the HTTP and location lines; a healthy site shows at most one or two redirects, and a loop repeats the same addresses.

Step 5: Undo the last change or regenerate the rules

If it began after a plugin change, deactivate that plugin, or all plugins, from the dashboard or by renaming the plugin folder, and test. Our guide on finding the plugin that broke your site shows a safe way. If it began after an edit to .htaccess, restore the previous copy, or rename the file and save Settings → Permalinks to make WordPress write a fresh one (on servers that use it). If you moved the site recently, also read moving WordPress to a new host.

Version and hosting differences

  • Apache and LiteSpeed read .htaccess; Nginx uses its own server configuration, so ask your host where redirects live.
  • Managed hosts often have a built-in “force HTTPS” option, so a plugin doing the same adds a second rule.
  • Multisite stores addresses in the database and needs manual edits, as the developer documentation notes.

How to verify the fix

  • The site loads in a private window on http://, https://, with and without www, and lands on one final address.
  • curl -sIL shows a short, non-repeating chain.
  • Login, forms and checkout still work, and no mixed content warnings appear.

How to prevent it from happening again

  • Choose one place to force HTTPS and one preferred host, and write it down.
  • Back up before changing address settings or SSL options.
  • Test on a staging copy before switching a CDN mode on a live store.
  • Keep this kind of change in your maintenance routine so someone owns it.

Frequently asked questions

Is ERR_TOO_MANY_REDIRECTS a WordPress bug?

Usually not. It is two rules disagreeing, whether in WordPress, the server, a plugin or a CDN.

Why does it only happen after I enable HTTPS?

Because the address settings, server rule or CDN mode may not agree about the scheme. Check Steps 2 to 4.

Can clearing cookies fix it?

Only if the problem is in your browser. If it also fails in a private window or another device, the cause is on the site or the CDN.

Is it safe to edit .htaccess?

Yes with a copy of the file. A single wrong character can take the site down, so keep the original ready.

Related guide: WordPress Posts Showing 404 Errors: Fix Permalinks and Rewrite Rules

What to do next

Find the two rules, keep one and test the chain. If your site still loops, or a CDN or SSL change is involved, wpallsolution offers an emergency WordPress fix and WordPress maintenance packages. We cannot promise a result without seeing your setup.

Sources and official documentation

Keep reading

More guides

Need a hand with this?

Tell us what is happening. We reply with honest next steps.

Talk to us