Home/Blog/How to Fix ERR_TOO_MANY_REDIRECTS in WordPress 2026

How to Fix ERR_TOO_MANY_REDIRECTS in WordPress 2026

WordPress ERR_TOO_MANY_REDIRECTS redirect loop error illustration

What Is ERR_TOO_MANY_REDIRECTS?

If you want to fix ERR_TOO_MANY_REDIRECTS in WordPress, you first need to understand what the browser is telling you. This error appears when a page keeps redirecting to another address, which redirects back again, in an endless circle. Browsers give up after about 20 hops and show the error instead of the page. Your site is not broken beyond repair — two settings are simply disagreeing about where visitors should end up.

On WordPress, the loop usually starts right after a change: installing an SSL certificate, turning on Cloudflare, moving to a new host, or adding a redirect plugin. The cause is almost always one of a handful of settings, and once you find the layer sending visitors in a circle, the fix is usually quick.

Common Causes of a WordPress Redirect Loop

A redirect loop needs two rules that each think they are right. One rule says the correct address is HTTPS, while the other cannot tell that the visitor already arrived over HTTPS, so it sends them around again. The most common culprits are Cloudflare set to Flexible SSL while the server also forces HTTPS, a mismatch between the WordPress Address and Site Address, HTTPS forced in two places, conflicting .htaccess or plugin rules, and stale cookies or cached redirects.

Less often, a proxy or load balancer hides HTTPS from WordPress, so WordPress keeps redirecting to HTTPS even though the visitor is already there. A loop on every page points to site-wide settings, while a loop only on wp-admin points to login cookies, SSL admin settings, or a security plugin.

Step 1: Rule Out Your Browser First

Before changing anything on the server, test in a private or incognito window and on your phone. If the loop only appears in one browser, clear that browser’s cookies for your domain only and try again. WordPress login cookies and cached 301 redirects can keep a loop alive long after the server side is fixed.

Step 2: Trace the Redirect Chain

Next, look at the actual redirect chain instead of guessing. From a terminal, run curl with the address of the failing page and read only the Location headers. A loop is any address that shows up twice. If the chain bounces between HTTP and HTTPS versions of the same page, you have an HTTPS disagreement; if it bounces between www and non-www versions, you have an address mismatch.

Step 3: Fix the Cloudflare SSL Mode

Cloudflare’s Flexible SSL mode is the single most common cause of this error on sites behind Cloudflare. In Flexible mode, Cloudflare talks to your origin server over plain HTTP. If your server or an SSL plugin redirects every HTTP request to HTTPS, Cloudflare passes that redirect to the browser, the browser asks again over HTTPS, and the cycle repeats. Switch Cloudflare’s SSL/TLS mode to Full or Full (Strict) once your origin has a valid SSL certificate installed.

Fixing a WordPress redirect loop caused by SSL and server settings

Step 4: Match Your WordPress and Site Addresses

In your WordPress dashboard, go to Settings, then General, and check the WordPress Address and Site Address fields. They must match exactly: the same https or http protocol, the same www choice, and no trailing slash. If you cannot reach wp-admin because of the loop, force the correct values by adding WP_HOME and WP_SITEURL definitions to wp-config.php above the line that says “That’s all, stop editing!”

Step 5: Force HTTPS in Only One Place

HTTPS should be enforced by exactly one layer: Cloudflare, your host, a plugin, or .htaccess — never two at once. If Cloudflare already redirects HTTP to HTTPS, turn off the duplicate redirect in your SSL plugin and your .htaccess file, and vice versa. Audit every place a redirect could live, keep the one matching your canonical address, and delete the rest. After each change, clear your page cache and test in a private window.

Step 6: Reset .htaccess and Test Your Plugins

If the addresses and SSL mode are correct and the loop continues, rename your .htaccess file via FTP or your hosting file manager, then regenerate a clean one by going to Settings, then Permalinks, in wp-admin and clicking Save Changes. If that does not help, deactivate all plugins by renaming the plugins folder, then reactivate them one at a time until the loop returns. The last plugin you reactivated is the culprit — commonly a redirect manager, an SSL-forcing plugin, or a caching plugin.

How to Prevent Redirect Loops in Future

Preventing the next loop is mostly about discipline. Make one address change at a time and test immediately, keep a note of where HTTPS is enforced, and never enable Flexible SSL on a server that already forces HTTPS. Back up wp-config.php and .htaccess before migrating hosts or adding a CDN. Purge all caches after any URL or SSL change, and check both the homepage and wp-admin. If your site also feels sluggish, read our guide on why your website loads slowly, and our Cloudflare Error 522 fix covers the next most common Cloudflare problem.

Conclusion

Fixing ERR_TOO_MANY_REDIRECTS in WordPress comes down to finding the two rules that disagree and keeping only one of them. Clear cookies, trace the chain, set Cloudflare to Full or Full (Strict), match your site addresses, enforce HTTPS once, and test plugins last. Work through the steps in order and test after each change. For more fixes like this, browse the KamiWeb Blog and explore our free online tools.