Facing the error_too_many_redirects WordPress Cloudflare loop is a nightmare that can take your entire website offline instantly. You activated Cloudflare to make your site faster, but instead, your browser is displaying a frustrating message: “ERR_TOO_MANY_REDIRECTS”.
This is one of the most panic-inducing errors for website owners because it locks you out of everything—your homepage, your admin dashboard, and your content. No matter how many times you refresh, the browser eventually gives up.
The error_too_many_redirects WordPress Cloudflare loop is not a server crash. It is a communication breakdown. Essentially, Cloudflare and your WordPress hosting server are playing a game of “hot potato,” passing your visitor back and forth until the browser stops the madness. You can read more about redirect loops in the official Cloudflare Documentation.
🚀 Need this fixed instantly? If you are uncomfortable editing config files or SSL settings, Click here to order our Emergency Fix Service. We will resolve the error_too_many_redirects WordPress Cloudflare issue and restore your site uptime within one hour.
In this extensive guide, we will visualize exactly why this infinite loop happens. Furthermore, we will provide you with 6 proven methods to break the cycle and get your site back online.
Why the Error_too_many_redirects WordPress Cloudflare Loop Happens
To fix the issue, you must understand the architecture. The error_too_many_redirects WordPress Cloudflare issue almost always stems from a conflict in SSL (Secure Sockets Layer) settings.
Here is the common scenario:
Cloudflare (Flexible Mode): You selected “Flexible” SSL in Cloudflare. This tells Cloudflare to secure the connection between the Visitor and Cloudflare, but send traffic to your Server via HTTP (unsecured) to ensure compatibility.
Your Server (Force HTTPS): Your WordPress site or hosting server has a rule that says “If anyone tries to visit via HTTP, redirect them to HTTPS.”
The Infinite Loop:
Cloudflare sends a request to your server via HTTP.
Your server sees the HTTP request and sends a redirect back: “Please use HTTPS.”
Cloudflare receives the redirect and tries again… via HTTP (because it is set to Flexible).
Your server redirects it again.
Result: The error_too_many_redirects WordPress Cloudflare crash.
We will address this by aligning your encryption protocols.
Method 1: Change SSL to Full to Fix the Loop
In 90% of cases, this single setting resolves the error_too_many_redirects WordPress Cloudflare conflict immediately. You need to tell Cloudflare to stop downgrading the connection to HTTP.
Step 1: Log in to Cloudflare
Access your Cloudflare dashboard and select the domain experiencing the error.
Step 2: Navigate to SSL/TLS
Click the SSL/TLS icon in the sidebar menu.
Step 3: Switch Mode
You will likely see “Flexible” selected. Change this to “Full” or “Full (Strict)”.
Full: Encrypts traffic to your server. It allows self-signed (invalid) certificates on the server. (Safest bet).
Full (Strict): Encrypts traffic and requires a valid Let’s Encrypt/Commercial certificate on the server. (Best for security).
Step 4: Clear Cache
After switching, wait 30 seconds. Then, try accessing your site in an Incognito window. The loop should be broken.
Method 2: Edit wp-config.php for Error_too_many_redirects WordPress Cloudflare Fix
If Method 1 did not work, or if your WordPress database still thinks the site URL is “http://”, you need to force WordPress to recognize the secure connection.
Since you cannot access your dashboard to change settings, you must edit the wp-config.php file directly to apply this error_too_many_redirects WordPress Cloudflare patch.
Step 1: Access File Manager
Log in to your hosting control panel (cPanel, Hostinger hPanel, etc.) and open File Manager.
Step 2: Edit wp-config.php
Navigate to public_html and edit wp-config.php.
Step 3: Add the Fix Code
Scroll down near the top, just after the <?php opening tag. Paste the following code:
$_SERVER['HTTPS'] = 'on';
define('WP_HOME','https://yourdomain.com');
define('WP_SITEURL','https://yourdomain.com');
Replace yourdomain.com with your actual domain.
This code overrides the database settings and forces WordPress to accept that the connection is secure.
Method 3: Disable “Always Use HTTPS” to Stop the Redirect Loop
Sometimes, the conflict is reversed. Your server is allowing HTTP, but Cloudflare is aggressively forcing HTTPS before the server is ready. To troubleshoot this specific problem, try temporarily disabling this rule.
Step 1: Go to Edge Certificates
In Cloudflare, go to SSL/TLS > Edge Certificates.
Step 2: Toggle Off
Scroll down to “Always Use HTTPS”. Toggle the switch to OFF.
Step 3: Test
Clear your browser cache and check the site. If it loads (even as “Not Secure”), you know the loop was caused by this rewrite rule. You can now fix your internal SSL issues before turning this back on.
Method 4: Check .htaccess for Conflicting Redirect Rules
Your .htaccess file is a powerful server configuration file. If you have a plugin (like Really Simple SSL) or an old rule forcing redirects, it might be fighting with Cloudflare, causing the error_too_many_redirects WordPress Cloudflare loop. For more on .htaccess, verify the standard rules at WordPress.org.
Step 1: Locate .htaccess
In your hosting File Manager, find .htaccess in the public_html folder.
Step 2: Inspect Rules
Look for rewrite rules like this:
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
Step 3: Disable Temporarily
To verify if this is the cause of the loop, rename the file to .htaccess_backup.
If the site loads after renaming it, the error is inside that file. You should generate a fresh, default WordPress .htaccess file.
Method 5: Purge Caches to Clear Ghost Redirects
Sometimes, the loop is actually fixed, but your computer remembers the error. Browsers and Cloudflare cache 301 (Permanent) Redirects aggressively, making it look like the error_too_many_redirects WordPress Cloudflare issue is still there when it isn’t.
Step 1: Purge Cloudflare
Go to Caching > Configuration.
Click Purge Everything.
Step 2: Clear Browser Cache
Do not just refresh.
Chrome: Right-click > Inspect > Right-click the Refresh button > Empty Cache and Hard Reload.
Or: Test in a completely different browser or on your phone (disconnected from WiFi).
This ensures you aren’t diagnosing a “ghost” loop that no longer exists.
Method 6: Use the “Cloudflare Flexible SSL” Plugin
If you absolutely must use “Flexible” mode (perhaps your host doesn’t support SSL certificates), you need a patch to make WordPress understand it and prevent the crash.
Since you cannot access the admin dashboard, you must install this plugin manually via FTP/File Manager.
Download the “Cloudflare Flexible SSL” plugin from the WordPress repository.
Unzip the folder.
Upload the folder to
/wp-content/plugins/.Rename the folder to force activation (or use WP-CLI if you have SSH access).
Note: This is a legacy fix. Method 1 (Switching to Full SSL) is vastly superior and more secure.
Conclusion on Fixing the Loop
The error_too_many_redirects WordPress Cloudflare loop is a rite of passage for new Cloudflare users. It is almost always a sign that Cloudflare is speaking “HTTP” while your server is demanding “HTTPS.”
By switching your SSL mode to Full, editing your wp-config.php, or checking your .htaccess rules, you can align these protocols and restore your site.
Summary of Fixes:
SSL Mode: Switch Cloudflare to Full.
Config: Add
HTTPS = ontowp-config.php.Edge Rules: Disable “Always Use HTTPS” temporarily.
Server: Check
.htaccessfor conflicting rewrites.Cache: Purge Cloudflare and Browser cache.
Still Stuck in the Loop? If you have tried all 6 methods and the error_too_many_redirects WordPress Cloudflare screen persists, the issue might be a deep-level DNS propagation delay or a host-specific firewall rule. 👉 Contact Us Here for a professional audit, or check out our Services Price Plan to prevent downtime like this in the future.
