ERR_TOO_MANY_REDIRECTS WordPress: 7 PROVEN Fixes (2026 Guide)

✍️ By Vikas Rohilla 📅 Updated: March 2026 ⏱️ 9 min read 🏷️ WordPress Errors

You open your WordPress site and instead of your homepage, you see this:

“This page isn’t working. yourdomain.com redirected you too many times. ERR_TOO_MANY_REDIRECTS”

No site. No admin panel. Just a browser error and a completely inaccessible website.

The ERR_TOO_MANY_REDIRECTS WordPress error is one of the most frustrating problems you can encounter — because unlike most WordPress errors, it locks you out of both your frontend AND your wp-admin simultaneously. You cannot log in to fix it from inside WordPress. Everything has to be done via cPanel, File Manager, or phpMyAdmin.

But here is what makes this error different from other WordPress crashes: it almost always has a clear, identifiable cause. Once you know the diagnosis flow, the fix is almost always found in under 15 minutes. This guide walks you through every step.

🚨 Site down right now? Do these three things immediately: (1) Clear your browser cookies and cache. (2) Go to Settings → General via wp-admin if accessible — verify WordPress Address and Site Address match exactly. (3) If you cannot access wp-admin — open wp-config.php via cPanel and add: define(‘WP_HOME’,’https://yourdomain.com’); define(‘WP_SITEURL’,’https://yourdomain.com’); — this overrides the stored URL and often resolves the ERR_TOO_MANY_REDIRECTS WordPress error instantly.
err_too_many_redirects wordpress chrome browser error screen redirect loop
The ERR_TOO_MANY_REDIRECTS WordPress error in Chrome — “This page isn’t working” with the ERR_TOO_MANY_REDIRECTS code — locks out both frontend visitors and the wp-admin dashboard

How ERR_TOO_MANY_REDIRECTS Looks in Different Browsers

The same redirect loop error appears differently depending on which browser your visitor is using. All of these mean exactly the same thing — a redirect loop has been detected:

🌐

Google Chrome

“This page isn’t working. yourdomain.com redirected you too many times. ERR_TOO_MANY_REDIRECTS”

🦊

Mozilla Firefox

“The page isn’t redirecting properly. Firefox has detected that the server is redirecting the request in a way that will never complete.”

🧭

Safari

“Safari Can’t Open the Page. Too many redirects occurred trying to open yourdomain.com.”

🔷

Microsoft Edge

“Hm, we can’t reach this page. yourdomain.com redirected you too many times.”

What Causes the ERR_TOO_MANY_REDIRECTS WordPress Error?

A redirect loop happens when your server tells the browser to go from URL A to URL B — but URL B then redirects back to URL A. The browser bounces back and forth until it gives up and shows the ERR_TOO_MANY_REDIRECTS WordPress error.

What makes it particularly confusing is that the loop is rarely obvious. It can be caused by a single misconfigured setting, a plugin that modified your .htaccess file, or a mismatch between your SSL configuration and your stored WordPress URL — all of which look normal from inside your dashboard.

CauseHow CommonFix
🔴 Wrong WordPress/Site URLMost commonFix 1 — Settings → General
🔴 SSL/HTTPS misconfigurationVery commonFix 2 — Force HTTPS settings
🟡 Caching plugin serving old redirectsCommonFix 3 — Clear all caches
🟡 Corrupted .htaccess fileCommonFix 4 — Reset .htaccess
🟠 Plugin conflictCommonFix 5 — Disable plugins
🔵 Browser cookies/cacheFrequentFix 6 — Clear browser data
🟢 CDN misconfigurationLess commonFix 7 — CDN settings

Quick Diagnosis — Find Your Cause in 2 Minutes

1
Can you access wp-admin?
✅ Yes → Check Settings → General (Fix 1). URL mismatch is the most likely cause.
❌ No → Go directly to Fix 1 via wp-config.php override, then Fix 3 (clear cache).
2
Did the error start after adding SSL/HTTPS?
✅ Yes → SSL loop is the cause. Go directly to Fix 2.
❌ No → Continue diagnosis below.
3
Did the error start after installing or updating a plugin?
✅ Yes → Plugin conflict. Go directly to Fix 5.
❌ No → Try Fix 3 (clear cache) then Fix 4 (.htaccess reset).
4
Does the error appear in incognito/private mode?
❌ No → Browser cookies/cache is the issue. Fix 6 resolves it in 2 minutes.
✅ Yes → The error is server-side. Continue with Fixes 1–5.

Fix 1: Correct Your WordPress URL Settings

The most common cause of the ERR_TOO_MANY_REDIRECTS WordPress error is a mismatch between your WordPress Address and Site Address — or between those settings and your actual domain. Even a single character difference (http vs https, www vs non-www) creates a redirect loop.

Method A — Via wp-admin Settings (If You Can Access It)

  1. Go to WordPress Dashboard → Settings → General
  2. Check both WordPress Address (URL) and Site Address (URL)
  3. Both must be identical and must match your actual domain exactly — including http vs https and www vs non-www
  4. If using SSL: both should start with https://
  5. Click Save Changes → test your site
📖 Related: After fixing redirect loops, always check your WordPress Permalink Settings — .htaccess resets that fix redirect loops sometimes also reset your permalink rewrite rules, requiring a Settings → Permalinks → Save Changes to restore URLs.
wordpress settings general url fields wordpress address site address err_too_many_redirects fix
WordPress → Settings → General — both WordPress Address and Site Address must match exactly, including http/https and www/non-www — a mismatch here is the most common cause of ERR_TOO_MANY_REDIRECTS in WordPress

Method B — Via wp-config.php (If wp-admin Is Inaccessible)

  1. Open Hostinger hPanel → File Manager → public_html
  2. Find wp-config.php → right-click → Edit
  3. Add these two lines before the /* That’s all, stop editing! */ comment:
define(‘WP_HOME’,’https://yourdomain.com’); define(‘WP_SITEURL’,’https://yourdomain.com’);
  1. Replace yourdomain.com with your actual domain
  2. Save → test your site
  3. Once site loads — go to Settings → General → confirm URLs → remove these lines from wp-config.php
✅ Why this works: wp-config.php definitions override whatever is stored in the database — bypassing the redirect loop entirely. This is the fastest way to regain access to a site stuck in an ERR_TOO_MANY_REDIRECTS WordPress loop when you cannot reach wp-admin.

Fix 2: Fix SSL/HTTPS Redirect Loop

The second most common cause of ERR_TOO_MANY_REDIRECTS in WordPress is an SSL misconfiguration — where your server forces HTTPS but your WordPress URL settings still use HTTP, or vice versa. The result is an endless loop between the two protocols.

Check Your SSL Configuration

  1. Confirm your SSL certificate is active — Hostinger hPanel → SSL → check green status
  2. Go to Settings → General → make sure both URLs start with https:// (not http)
  3. Check your .htaccess file — look for any HTTP-to-HTTPS redirect rules
  4. If using LiteSpeed cache — go to LiteSpeed → General → Force HTTPS → make sure it is not conflicting with an SSL plugin doing the same thing

Fix Double HTTPS Redirect in .htaccess

Sometimes two conflicting HTTPS redirect rules exist in .htaccess — one from WordPress and one from a plugin or hosting panel. Check for duplicate redirect rules and remove one:

# REMOVE duplicate if two exist — keep only ONE RewriteCond %{HTTPS} off RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
📖 Related: SSL issues affect more than redirects — they also hurt your Core Web Vitals and technical SEO signals. After fixing the redirect loop, run a full audit at ToolXray SEO Audit Tool to confirm no other SSL-related issues remain.
📖 Related: If the redirect error is specific to wp-admin only, you may have a WordPress login redirect loop rather than a site-wide redirect issue — different cause, different fix.

Fix 3: Clear All Caches

Redirect loops get cached — meaning even after you fix the underlying issue, your site may continue showing the error because an old cached redirect is still being served. Clearing all caches is an essential step in fixing any ERR_TOO_MANY_REDIRECTS WordPress situation.

Clear LiteSpeed Cache (Hostinger)

  1. Go to WordPress Dashboard → LiteSpeed Cache
  2. Click Purge All in the top toolbar
  3. Also go to LiteSpeed → Toolbox → Purge → Purge All
litespeed cache purge all button wordpress err_too_many_redirects fix clear cache
LiteSpeed Cache → Purge All — clearing all cached data is an essential step in fixing ERR_TOO_MANY_REDIRECTS in WordPress, as redirect loops are frequently served from cache even after the underlying issue is fixed

Clear Browser Cache and Cookies

  1. Chrome: Press Ctrl + Shift + Delete → select All time → check Cookies and Cached images → Clear data
  2. Or open your site in Incognito mode (Ctrl + Shift + N) — if it loads in incognito, browser cache was the cause
  3. Also try accessing your site from a different device or network to confirm the error is server-side
💡 Pro tip: Always test in incognito mode first. If your site loads normally in incognito but shows the redirect error in your regular browser — the issue is entirely local to your browser cookies and cache. Clear both and the error will disappear without any server-side changes needed.

Fix 4: Reset Your .htaccess File

The .htaccess file controls all URL routing on your server. Plugins — particularly SEO plugins, redirect managers, and SSL plugins — can add conflicting redirect rules to .htaccess that create loops. Resetting it to the clean WordPress default fixes this type of ERR_TOO_MANY_REDIRECTS WordPress error completely.

  1. Open hPanel → File Manager → public_html
  2. Enable Show Hidden Files → find .htaccess
  3. Right-click → Rename → rename to .htaccess_old (keep as backup)
  4. Create a new file named .htaccess
  5. Paste this clean WordPress default content:
# BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteRule ^index\.php$ – [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> # END WordPress
  1. Save the file → test your site
  2. If site loads — the old .htaccess had conflicting redirect rules
  3. Go to Settings → Permalinks → Save Changes to regenerate clean rewrite rules. The default .htaccess content is sourced from the official WordPress documentation
cpanel file manager htaccess file wordpress err_too_many_redirects reset fix
cPanel File Manager → find .htaccess → rename to .htaccess_old → create fresh .htaccess with clean WordPress default content — fixes redirect loops caused by conflicting rules added by plugins or SSL configuration

Fix 5: Disable All Plugins via File Manager

Plugin conflicts are one of the most frequent causes of the ERR_TOO_MANY_REDIRECTS WordPress error — particularly redirect manager plugins, SSL plugins, SEO plugins with redirect features, and caching plugins. Since the error often locks you out of wp-admin, you need to disable them via File Manager rather than the WordPress dashboard.

  1. Open hPanel → File Manager → public_html → wp-content
  2. Find the plugins folder
  3. Right-click → Rename → rename to plugins_disabled
  4. This deactivates ALL plugins simultaneously
  5. Test your site — if it loads, a plugin was causing the redirect loop
  6. Rename plugins_disabled back to plugins
  7. Reactivate plugins one at a time via wp-admin → Plugins → when the error returns, that plugin is the cause
cpanel file manager plugins folder renamed plugins_disabled wordpress err_too_many_redirects plugin conflict fix
cPanel File Manager → wp-content → rename plugins folder to plugins_disabled — instantly deactivates all plugins to diagnose whether a plugin conflict is causing the ERR_TOO_MANY_REDIRECTS WordPress error
⚠️ Most likely plugin culprits: Rank Math or Yoast (redirect features), Really Simple SSL, WP Force SSL, Redirection plugin, LiteSpeed Cache (HTTPS force setting), Cloudflare plugin, and any plugin recently installed or updated just before the error appeared.

Fix 6: Clear Browser Cookies Completely

Sometimes the ERR_TOO_MANY_REDIRECTS WordPress error is not a server problem at all — it is a corrupted browser cookie storing an old redirect that no longer exists. This is more common than most people realize, and it is the easiest fix of all.

  1. In Chrome — press Ctrl + Shift + Delete
  2. Set Time range to All time
  3. Check Cookies and other site data AND Cached images and files
  4. Click Clear data
  5. Close all browser tabs → reopen → visit your site
📖 Related: Redirect errors after a site migration are extremely common. If you recently moved hosts, read WordPress Database Error Fix — migration-related URL issues often trigger both database errors and redirect loops simultaneously.
📖 Related: Plugin update triggered a redirect loop? Check first if WordPress is stuck in maintenance mode — sometimes both errors appear together after a failed SSL plugin update.

Fix 7: Check CDN and Cloudflare Settings

If you are using Cloudflare or another CDN, a common SSL misconfiguration causes an endless redirect loop between Cloudflare and your server. This specific issue has a well-known cause and a one-setting fix.

  1. Log into your Cloudflare dashboard
  2. Select your domain → click SSL/TLS in the left menu
  3. Check the encryption mode — if it is set to Flexible, change it to Full or Full (Strict)
  4. Save → wait 2-3 minutes → test your site
💡 Why Flexible causes redirect loops: Cloudflare Flexible SSL means Cloudflare connects to your origin server via HTTP — but your WordPress settings force HTTPS. Your server then redirects back to HTTPS, Cloudflare serves HTTP again, and the loop never ends. Switching to Full SSL breaks the loop instantly.

Redirect errors caused by your hosting configuration?

Hostinger Business and Cloud plans include LiteSpeed SSL, Cloudflare integration, and priority support — eliminating the most common server-side causes of redirect loops for growing WordPress sites.

View Hostinger Plans →

How ERR_TOO_MANY_REDIRECTS Hurts Your SEO

The ERR_TOO_MANY_REDIRECTS WordPress error does not just take your site offline for visitors — it has immediate and measurable SEO consequences that continue even after the error is resolved.

  • Googlebot cannot crawl your site: Search engine bots hit the same redirect loop as browsers. During the time your site is down, Googlebot cannot crawl any of your pages — new content goes undiscovered and existing rankings begin to decay.
  • Crawl budget waste: When Googlebot does attempt to crawl and encounters repeated redirect loops, it consumes crawl budget without successfully indexing anything — leaving your other pages less frequently visited.
  • Potential deindexing: If the ERR_TOO_MANY_REDIRECTS WordPress error persists for days or weeks, Google may begin removing affected pages from its index — requiring a manual resubmission via Google Search Console after the fix.
  • Traffic loss compounds: Every hour your site is offline is traffic your competitors receive instead. For sites with established rankings, a multi-day outage can take weeks of normal operation to fully recover from.
📖 Related: After fixing your redirect error, check your Google Search Console immediately — Complete Technical SEO Audit Guide covers the post-recovery checks including resubmitting affected URLs and monitoring for residual crawl errors.
🔍

Free WordPress Technical Audit — ToolXray

After fixing your redirect error — check Core Web Vitals, PageSpeed, TTFB and 80+ technical signals. Free, no signup needed.

Run Free Audit →

How to Prevent ERR_TOO_MANY_REDIRECTS From Coming Back

  • Set URLs correctly from day one: When installing WordPress on a new domain or after any migration — immediately verify Settings → General has both URLs set correctly with the right protocol (https://) and www preference.
  • Only use one SSL plugin: Having both LiteSpeed’s Force HTTPS and a dedicated SSL plugin like Really Simple SSL active simultaneously almost guarantees a redirect conflict. Choose one and disable the other.
  • Test after every redirect plugin update: Redirect manager plugins and SEO plugins with redirect features are the most common source of .htaccess conflicts. Test your site immediately after updating any of these.
  • Set Cloudflare SSL to Full — not Flexible: Flexible SSL is a redirect loop waiting to happen on any WordPress site with HTTPS. Set it to Full or Full (Strict) and never change it back.
  • Monitor performance after fixing: A redirect loop causes TTFB spikes and LCP degradation. After fixing, check Why TTFB Is Critical, Fix LCP in WordPress and Fix INP in WordPress to restore performance scores.
  • Keep a working wp-config.php backup: Having WP_HOME and WP_SITEURL defined and ready to paste into wp-config.php means you can recover from a redirect loop in under 2 minutes regardless of what caused it.
📖 Related: Preventing redirect errors is part of a broader WordPress maintenance routine. Read WordPress Security Guide and WordPress Speed Optimization to keep your site stable and fast after fixing the redirect loop.

The Bottom Line

The ERR_TOO_MANY_REDIRECTS WordPress error is alarming precisely because it locks you out of everything simultaneously — but it is almost always caused by one of seven identifiable issues, and most of them are fixed in under 5 minutes once you know where to look.

Start with the diagnosis flow: can you access wp-admin? Did the error start after an SSL change or plugin update? Does it appear in incognito mode? These three questions cut the possible causes in half and point you directly to the right fix.

The fastest recovery path for most sites: clear browser cookies → check URLs in Settings → General → clear all caches. Between these three steps, the majority of ERR_TOO_MANY_REDIRECTS WordPress errors are resolved without ever touching .htaccess or disabling plugins.

🔍 Free WordPress Technical Audit

After fixing your redirect error — check Core Web Vitals, broken links, PageSpeed and 80+ signals

Run Free Audit at ToolXray →

Related Articles

💀

WordPress White Screen of Death

Another site-wide crash — different cause, same urgency. 9 proven fixes.

🔴

WordPress 404 Error Fix

Pages returning “not found” after fixing redirects? 7 solutions.

🗄️

WordPress Database Error Fix

Migration causing both database errors and redirect loops? Fix both here.

WordPress Memory Limit Fix

Fatal error after fixing redirects? Memory limit may be the next issue.

🚨

WordPress Site Hacked

Redirect loops caused by malware injection — signs and recovery steps.

🆓

Free Alternative to Ahrefs

Monitor recovery after redirect errors — free SEO tools, no subscription needed.

🎨

WordPress Theme Detector

Check which theme and plugins are active on your site — useful for diagnosing plugin conflicts.

🔬

Technical SEO Audit Guide

Post-redirect fix audit — crawlability, indexing, performance and 80+ checks.

Frequently Asked Questions

❓ What is the fastest fix for ERR_TOO_MANY_REDIRECTS in WordPress?
The fastest fix is to clear your browser cookies and cache first — test in incognito mode to confirm the issue is server-side. If it persists in incognito, add define(‘WP_HOME’,’https://yourdomain.com’) and define(‘WP_SITEURL’,’https://yourdomain.com’) to wp-config.php via cPanel File Manager. This overrides the stored URL settings and resolves the ERR_TOO_MANY_REDIRECTS WordPress error in the majority of cases within 2 minutes.
❓ Can ERR_TOO_MANY_REDIRECTS lock me out of wp-admin?
Yes — ERR_TOO_MANY_REDIRECTS in WordPress typically locks you out of both the frontend and wp-admin simultaneously. All fixes must be done via cPanel File Manager, phpMyAdmin, or FTP. The wp-config.php override method (Fix 1 Method B) is specifically designed for this scenario — it bypasses the redirect loop without requiring any access to wp-admin.
❓ Why does ERR_TOO_MANY_REDIRECTS happen after adding SSL?
After adding SSL, the most common cause is a conflict between your WordPress URL settings (still set to http://) and a plugin or server rule forcing https://. WordPress tries to load on http, gets redirected to https, but the WordPress URL setting redirects back to http — creating an infinite loop. Fix: update both WordPress Address and Site Address in Settings → General to use https://. If using Cloudflare, check that SSL mode is set to Full, not Flexible.
❓ Does ERR_TOO_MANY_REDIRECTS affect Google rankings?
Yes — while the error is active, Googlebot cannot crawl your site at all. If it persists for more than a day or two, Google may begin removing affected pages from search results. After fixing the error, check Google Search Console for any coverage issues and resubmit your sitemap. Rankings typically recover within 1-2 weeks of normal site operation after the redirect error is resolved.
❓ How is ERR_TOO_MANY_REDIRECTS different in Chrome vs Firefox?
The underlying error is identical — a redirect loop. Chrome displays “ERR_TOO_MANY_REDIRECTS”, Firefox shows “The page isn’t redirecting properly”, Safari says “Too many redirects occurred”, and Edge shows “redirected you too many times”. The browser-specific wording causes confusion but all four messages mean the same thing and are fixed with the same methods described in this guide.

    Leave a Comment

    Your email address will not be published. Required fields are marked *

    Scroll to Top