What the “Too Many Redirects” Error Means
If you are trying to fix Cloudflare too many redirects, the key is understanding that the browser is being sent back and forth between URLs until it stops.
This usually happens when Cloudflare, your origin server, or an application such as WordPress keeps redirecting the same request in conflicting ways.
Cloudflare sits between visitors and your origin server as a reverse proxy.
That position is useful for security and performance, but it also means SSL settings, redirect rules, and canonical URL preferences must agree across every layer.
Common Causes of Cloudflare Redirect Loops
Most redirect loops are caused by a mismatch between Cloudflare and the origin server.
In many cases, the site is forcing HTTPS in more than one place, or Cloudflare is using the wrong SSL mode for how the origin is configured.
- SSL mode mismatch between Cloudflare and the web server
- Conflicting HTTPS redirects in Cloudflare, the server, or CMS plugins
- Incorrect origin certificate setup or expired certificate
- Wrong WordPress site URL settings or database values
- Redirect rules in .htaccess, nginx config, or page rules
- Mixed www and non-www canonical settings
Check Cloudflare SSL/TLS Settings First
The most common fix is to review Cloudflare SSL/TLS settings.
If Cloudflare is set to Flexible while your server forces HTTPS, the browser may loop because Cloudflare requests the origin over HTTP while the origin sends traffic back to HTTPS.
Use the right SSL mode
- Flexible: Cloudflare connects to the origin over HTTP.
Avoid this if your origin forces HTTPS.
- Full: Cloudflare connects over HTTPS, but does not validate the certificate.
- Full (strict): Cloudflare connects over HTTPS and validates a trusted certificate.
This is usually the best long-term setting.
If your origin has a valid certificate, switch to Full (strict).
If not, install a proper certificate first, such as a Cloudflare Origin Certificate, Let’s Encrypt certificate, or another trusted TLS certificate.
Review the “Always Use HTTPS” feature
Cloudflare’s Always Use HTTPS can conflict with server-side redirects.
If your origin already redirects all HTTP traffic to HTTPS, try disabling this Cloudflare feature temporarily and test again.
Only one layer should usually handle the HTTP-to-HTTPS redirect.
Verify Your Origin Server Configuration
Cloudflare cannot fix a redirect loop created by the origin server itself.
Check whether the web server is sending redirects that conflict with Cloudflare’s behavior.
Apache and .htaccess checks
On Apache, inspect the .htaccess file for repeated redirects, forced HTTPS rules, or www-to-non-www logic that loops.
A common issue is multiple redirect blocks from plugins, hosting panels, or custom rules that all try to control the same URL path.
nginx configuration checks
On nginx, review server blocks for duplicate redirect directives, especially in return 301 or rewrite statements.
Confirm that the server_name, HTTPS listener, and canonical domain rules do not conflict.
Application-level redirects
Many applications add their own redirect logic.
WordPress plugins, Laravel middleware, Magento store settings, and similar systems can create loops if they disagree with the edge layer.
Disable redirect plugins temporarily and test the site again.
Fix WordPress URL and HTTPS Settings
WordPress is one of the most common environments where users search for how to fix Cloudflare too many redirects.
If the WordPress Address and Site Address are wrong, the site may keep bouncing between domains or protocols.
Check the WordPress Address and Site Address
In Settings > General, make sure both URLs use the same preferred domain and protocol.
For example, if your public site should load on HTTPS with www, both values should match that format.
Look for hardcoded values in wp-config.php
Some sites define WP_HOME and WP_SITEURL in wp-config.php.
If these constants disagree with the database values or Cloudflare settings, redirect loops can follow.
Keep the canonical URL consistent in one place whenever possible.
Temporarily disable redirect or SSL plugins
Plugins such as Really Simple SSL, Redirection, or security plugins can change how requests are routed.
Disable them one by one and retest.
If the loop disappears, reconfigure the plugin so it does not duplicate redirects already handled by Cloudflare or the server.
Align www and Non-www Preferences
Another frequent cause is a mismatch between www and non-www versions of the same domain.
Cloudflare, the origin server, and the CMS should all point to one canonical hostname.
Choose a preferred version and make every layer match it:
- Cloudflare page rules or redirect rules
- Web server redirect logic
- WordPress or CMS site URL settings
- SSL certificate coverage for both hostnames
If you redirect non-www to www, ensure the server certificate includes the www hostname.
If the certificate only covers the root domain, the browser may fail during redirect handling or behave unpredictably.
Inspect Cloudflare Page Rules, Redirect Rules, and Transform Rules
Cloudflare can create redirects at several levels.
A simple rule intended to improve SEO can become part of a loop if it overlaps with other redirect logic.
Places to review
- Redirect Rules in the Cloudflare dashboard
- Page Rules that force forwarding URLs
- Bulk Redirects lists
- Transform Rules that alter request paths or hostnames
Check whether any rule sends traffic from one URL to another that the origin already sends back.
For example, one rule may force http://example.com to https://www.example.com while the origin forces www back to non-www.
Clear Caches and Test in a Controlled Way
After changing settings, clear every cache that could preserve old redirect behavior.
That includes Cloudflare cache, origin cache, plugin cache, and server-side caching systems such as Varnish or LiteSpeed Cache.
Then test using an incognito window or a command-line tool such as curl -I to inspect the redirect chain.
A healthy setup should show a short sequence ending at a single canonical URL, not an endless back-and-forth.
Useful checks during testing
- Confirm the final URL uses the correct protocol
- Confirm the domain matches your preferred canonical hostname
- Check whether the redirect chain repeats the same URLs
- Test both the root domain and important subpaths
Use a Simple Troubleshooting Order
If you need a fast way to fix Cloudflare too many redirects, use this order so you do not chase symptoms instead of causes.
Start with SSL mode, then move to origin redirects, then application settings, then Cloudflare rules.
- Set Cloudflare SSL/TLS to the correct mode, ideally Full (strict)
- Disable overlapping HTTPS or www redirects temporarily
- Check the origin server configuration for repeated redirects
- Verify WordPress or CMS site URLs and plugin behavior
- Review Cloudflare Redirect Rules, Page Rules, and Bulk Redirects
- Clear all caches and retest the full redirect path
When the Issue Comes from Hosting or Certificate Problems
Sometimes the loop is not caused by a visible redirect rule at all.
Shared hosting environments, managed WordPress platforms, and misconfigured certificates can create behavior that looks like a redirect problem but is actually a TLS or server mismatch.
If the origin certificate is expired, invalid, or not trusted by Cloudflare in Full (strict) mode, fix the certificate first.
If you recently changed hosting, DNS, or nameservers, allow time for propagation and verify that Cloudflare is pointing to the correct origin IP address.
Practical Prevention Tips
Once the error is resolved, keep the configuration simple.
The fewer systems that enforce redirects, the easier it is to avoid future loops.
- Use one canonical hostname and one canonical protocol
- Let only one layer handle HTTP-to-HTTPS redirects
- Keep SSL certificates valid and properly matched to hostnames
- Document redirect rules in Cloudflare and the origin server
- Retest after installing new plugins, changing themes, or updating server config
With consistent SSL settings, aligned canonical URLs, and a clean redirect strategy, Cloudflare can proxy your site without triggering the same loop again.