How to Fix ERR_TOO_MANY_REDIRECTS in WordPress
Stuck in a redirect loop? Learn how to fix ERR_TOO_MANY_REDIRECTS in WordPress with our proven step-by-step checklist to get your site back online fast.
What Causes the ERR_TOO_MANY_REDIRECTS Loop?
To fix ERR_TOO_MANY_REDIRECTS in WordPress, you need to break the infinite loop where Server A forwards visitors to Location B, but Location B routes right back to Server A. This browser-level error almost always traces down to misconfigured site URLs in your database, conflicting reverse proxy SSL settings, corrupt browser cookies, or faulty rewrite rules inside your web server configuration file.
When a browser encounters a 301 or 302 HTTP response pointing to an address that immediately requests the original URL again, it halts execution after approximately twenty hops to protect system resources. The most frequent real-world trigger is an SSL mismatch: your origin web server expects requests over unencrypted HTTP, while a CDN like Cloudflare or a security plugin repeatedly enforces HTTPS across every incoming connection.
Step 1: Verify WordPress Address and Site Address URLs
The fastest diagnostic step is checking whether your WordPress Address (WP_SITEURL) and Site Address (WP_HOME) match exactly. If one directive uses HTTPS while the other relies on HTTP, or if one includes the 'www' subdomain while the other drops it, your server will continually bounce traffic back and forth in an inescapable routing loop.
Because the admin dashboard is usually inaccessible during this error, open your wp-config.php file via SFTP or your hosting file manager. Add explicit constants directly above the line that reads 'That's all, stop editing': define('WP_HOME', 'https://yourdomain.com'); and define('WP_SITEURL', 'https://yourdomain.com');. Hardcoding these strings instantly overrides corrupted values stored in the wp_options database table.
Save the modified configuration file and test your site in an incognito window. If the loop stops, inspect your database using phpMyAdmin later to permanently align the 'siteurl' and 'home' rows within the wp_options table, ensuring no trailing slashes or accidental protocol discrepancies remain.
Step 2: Correct Cloudflare and CDN SSL Encryption Modes
If your domain runs through an edge proxy such as Cloudflare, Sucuri, or QUIC.cloud, an SSL handshake mismatch is the primary culprit behind redirect loops. When Cloudflare's SSL/TLS encryption setting is toggled to 'Flexible', the proxy communicates with your origin hosting server over plain port 80 (HTTP), regardless of what the visitor sees in their address bar.
If your WordPress installation possesses an active SSL certificate and forces HTTPS via .htaccess, Nginx, or an SSL plugin, the origin server rejects the proxy's plain HTTP request and responds with a 301 redirect back to HTTPS. Cloudflare receives this instruction, re-requests the asset over HTTP, and generates the loop. Switching your Cloudflare SSL mode from 'Flexible' to 'Full' or 'Full (Strict)' eliminates this conflict immediately.
Wait sixty seconds after updating your encryption mode for edge nodes to synchronize. If your origin server lacks an installed TLS certificate, install a free Let's Encrypt certificate through your hosting control panel before enforcing Full Strict mode, ensuring both legs of the transmission remain fully authenticated.
Step 3: Reset Server Rewrite Rules and Purge Caching Layers
Corrupted routing directives inside Apache's .htaccess file or custom Nginx virtual host configurations often trigger persistent redirection loops. Third-party caching and security plugins frequently inject redirection instructions that collide with core WordPress permalink structures or force domain canonicalization incorrectly.
Rename your active .htaccess file to .htaccess_old using your FTP client. Then, create a clean replacement file containing default WordPress rules, save it with 644 permissions, and reload the webpage. If this resolves the problem, log into your restored WordPress admin area, navigate to Settings > Permalinks, and click 'Save Changes' to safely regenerate clean rewrite rules automatically.
Remember that browsers aggressively cache 301 Permanent Redirects locally on your computer. Even after rectifying server-side configurations, your local browser may serve the historical redirect response from disk. Clear your browser cache and cookies for the specific domain, or verify functionality using a terminal command like curl -IL https://yourdomain.com to view actual header responses.
Step 4: Audit Redirection Plugins and Reverse Proxy Headers
If manual URL definitions and clean rewrite rules fail to clear the error, audit your active plugins. Redirection modules, multilingual tools, and legacy SSL helpers like Really Simple SSL can enforce conflicting redirect chains. Rename your /wp-content/plugins folder to /wp-content/plugins_backup via SFTP to temporarily deactivate all extensions simultaneously and isolate culprit scripts.
Hosting environments sitting behind load balancers or Nginx reverse proxies often require proper forwarded header detection. Without the reverse proxy passing the 'HTTP_X_FORWARDED_PROTO' header, WordPress cannot tell that the user is connected via HTTPS, causing it to send an unnecessary HTTPS redirect. Inserting if (strpos($_SERVER['HTTP_X_FORWARDED_PROTO'], 'https') !== false) $_SERVER['HTTPS']='on'; at the top of wp-config.php completely solves this architecture edge case.
Questions readers ask about this topic
Why does ERR_TOO_MANY_REDIRECTS only appear on one device?
Can a corrupted WordPress plugin cause redirect loops?
How do I fix the redirect loop if I cannot access wp-admin?
What is the difference between Cloudflare Flexible and Full SSL?
Where to go next on Hostilo
One email a month. Hosting deals, new reviews, no fluff.
The WordPress performance checklist that actually works
Boost your WordPress speed with our performance checklist. Learn actionable tips that improve Core Web Vitals and user experience, ranked by real-world impact.
How to speed up WordPress: the only checklist you need
Learn how to speed up WordPress by focusing on the three changes that matter most: hosting, caching, and a CDN. Our guide ranks optimizations by impact.