Too Many Redirects After SSL appears when a browser is trapped in a redirect loop after HTTPS is enabled.
The request keeps bouncing between URLs and never reaches the final page. The browser eventually stops the process and displays a redirect error.
Quick Fix
- Clear browser cookies and cache.
- Check HTTP → HTTPS redirect rules in your server configuration.
- Verify WordPress Site URL and Home URL use HTTPS.
- Remove duplicate redirects from plugins.
- Ensure CDN SSL settings match the origin server configuration.
- Check www vs non-www redirect rules.
Redirect loops almost always occur when two systems try to enforce redirects at the same time.
What “Too Many Redirects After SSL” Actually Means
This error means the browser follows redirects that never resolve.
Instead of reaching a final page, the request cycles between URLs.
Example loop:
- http://example.com → https://example.com
- https://example.com → http://example.com
- repeat indefinitely
After several attempts, the browser stops and reports a redirect loop.
Why Redirect Loops Happen After SSL Installation
SSL migrations introduce multiple redirect points. If they conflict, a loop occurs.
Conflicting Redirect Rules
The server forces HTTPS while an application redirect sends the request back to HTTP.
Incorrect WordPress URL Settings
If WordPress URLs still use HTTP, WordPress may redirect away from HTTPS.
CDN SSL Misconfiguration
CDNs such as Cloudflare can enforce HTTPS independently from the origin server.
If both attempt to redirect incorrectly, the request loops.
Redirect Plugins
WordPress plugins that force HTTPS can conflict with server-level redirects.
www vs non-www Conflicts
Improper domain redirects combined with HTTPS rules can produce endless redirects.
How to Fix Too Many Redirects After SSL
Step 1 — Clear Cookies
Browsers sometimes store outdated redirect information.
- Clear cookies for the website.
- Reload the page.
This resolves many client-side loops.
Step 2 — Verify WordPress URLs
In WordPress:
- Go to Settings → General.
- Ensure both URLs use HTTPS.
- WordPress Address
- Site Address
If these differ, WordPress may trigger redirects.
Step 3 — Inspect Server Redirect Rules
Check your web server configuration.
Example Apache rule:
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
Only one HTTPS redirect rule should exist.
Step 4 — Review CDN SSL Mode
If using Cloudflare or another CDN, verify SSL mode.
Recommended setup:
- Origin server has a valid SSL certificate
- CDN SSL mode set to Full or Full (Strict)
Flexible SSL often creates redirect loops.
Step 5 — Disable Redirect Plugins
Temporarily disable plugins that force HTTPS or manage redirects.
Server-level redirects should handle HTTPS migration.
Step 6 — Fix Domain Redirect Rules
Ensure consistent redirects between domain versions.
Example configuration:
- http://example.com → https://example.com
- http://www.example.com → https://example.com
Avoid multiple redirect paths.
Advanced Troubleshooting
Inspect Redirect Chains
Use browser developer tools to view the redirect sequence.
This reveals where the loop begins.
Test Without CDN
Temporarily disable the CDN proxy to test the origin server directly.
Check Proxy Headers
Applications behind proxies rely on headers such as X-Forwarded-Proto.
If these headers are missing, the application may misinterpret HTTPS requests.
Review Framework Redirect Settings
Some web frameworks automatically redirect to HTTPS and may conflict with server rules.
Does This Error Affect SEO?
Yes.
- Search engines cannot reach the page.
- Crawling stops at the redirect loop.
- Users abandon the site.
Redirect loops effectively make the site inaccessible.
Prevention Tips
- Use a single redirect strategy.
- Handle HTTPS redirects at the server level.
- Avoid redirect plugins when possible.
- Test HTTPS migrations before going live.
- Confirm CDN SSL configuration.
Simpler redirect logic prevents most loops.
When to Contact Support
Contact your hosting provider if:
- You cannot access server configuration.
- Redirect behavior differs across environments.
- CDN SSL configuration conflicts with the origin server.
Provide redirect logs and server configuration details.
FAQ
Why does “Too Many Redirects” appear after installing SSL?
Usually because two redirect systems conflict.
Can browser cookies cause redirect loops?
Yes. Old cookies sometimes trigger outdated redirects.
Does Cloudflare Flexible SSL cause redirect loops?
Yes. Flexible SSL often conflicts with server HTTPS redirects.
Is this error dangerous?
No, but it makes the website unreachable.
How long does fixing redirect loops take?
Once the conflicting redirect is identified, the fix typically takes minutes.
Summary
Too Many Redirects After SSL is caused by conflicting redirect rules between servers, applications, and CDNs.
Fixing the issue usually requires simplifying redirect logic and ensuring HTTPS is enforced consistently across the entire stack.