Redirected Too Many Times: Causes, Checks, and Fixes

Redirected too many times means a URL keeps sending the browser through the same redirect path until the page stops loading. The issue often appears after DNS changes, WordPress updates, CDN settings etc., but it is especially common when an HTTPS redirect setup conflicts with another rule.

What does “redirected too many times” mean?

“Redirected too many times” appears when a page enters a redirect loop. Instead of reaching a final destination, the browser keeps moving between URLs. After several attempts, Chrome, Safari, Firefox etc. stop the process and show an error message.

A simple loop can look like this:

http://example.com

↓

https://example.com

↓

http://example.com

↓

Loop continues

For users, the page looks broken. For website owners, the issue points to a conflict between browser cache, SSL rules, DNS records, CMS settings, CDN behavior, server redirects etc.

The business impact depends on the affected template. A loop on the homepage blocks most entry paths. Checkout, login, pricing, lead form, or service pages carry higher priority because they can affect revenue, qualified leads, support access, or trust.

Browser messages you may see

Different browsers describe the same redirect loop in slightly different ways. The message helps you recognize the error, but the fix depends on where the loop starts.

Browser	Common message
Chrome	ERR_TOO_MANY_REDIRECTS
Safari	Safari Can’t Open the Page
Firefox	The page isn’t redirecting properly
Edge	This page isn’t working right now

A browser message does not always mean the browser caused the problem. Cookies can trigger a local issue, while DNS, SSL, Cloudflare, WordPress, server rules etc. can affect every visitor.

What leads to the redirected too many times error?

The error usually comes from conflicting redirect instructions. One system sends the visitor to a URL, while another system sends the same visitor back. This often happens after a site launch, HTTPS migration, domain change, plugin update, or CDN configuration change.

Use this table before trying random fixes:

Loop layer	What to check	Best first action
Browser	Cookies, cache, old session data	Test incognito and clear site cookies
DNS or domain	Root vs www, A record, CNAME etc.	Check DNS host and default domain
HTTPS or SSL	HTTP ↔ HTTPS behavior	Test SSL certificate and force-HTTPS rules
CDN or proxy	Cloudflare mode, HSTS, edge redirects etc.	Compare CDN setting with origin behavior
CMS	WordPress URL settings or plugin rules	Check Site Address before disabling plugins
Server	.htaccess, Nginx, redirect pattern etc.	Trace the redirect chain first

This structure helps the technical owner avoid unnecessary changes. A cookie issue may need a quick browser fix, while a CDN-origin conflict needs SSL or redirect rule review.

Root domain vs www redirect loops

A common domain conflict appears when the root domain points to www, while www redirects back to the root domain.

Example:

example.com

↓

www.example.com

↓

example.com

↓

Loop continues

Choose one default domain, then make the other version redirect to it. The same rule should apply across CMS settings, DNS records, hosting panel, CDN rules etc. When several layers define the default domain differently, the browser can keep bouncing between versions.

HTTPS and SSL conflicts

HTTPS migration often creates redirect loops when more than one layer forces the protocol. A plugin may force HTTPS, while the server rule does the same. A CDN may also apply an edge redirect before the request reaches the origin.

Cloudflare’s official SSL/TLS documentation explains a common loop with Flexible SSL. In that setup, Cloudflare connects to the origin through HTTP, while the origin redirects HTTP back to HTTPS. The request then repeats.

Setting conflict	What happens
CDN sends HTTP to origin	Origin forces HTTPS
Origin sends HTTPS back	CDN repeats the original request pattern
Browser receives repeated redirects	Page fails with too many redirects

One of the most common causes of an infinite loop is an SSL mismatch. If your CDN connects via HTTP but your origin server forces HTTPS, the request will bounce back and forth endlessly.

When this happens, review Cloudflare SSL/TLS mode, Always Use HTTPS, HSTS, page rules etc. The right fix depends on the origin certificate and the website’s intended HTTPS setup.

WordPress URL mismatch

WordPress can create redirect loops when the WordPress Address and Site Address point to different protocol or domain versions. This often appears after migration, HTTPS cleanup, staging-to-live release, or plugin changes.

Check:

WordPress field	What to verify
WordPress Address	Correct protocol and domain
Site Address	Same canonical version
Plugin redirects	Recent SSL or redirect plugin changes
Server rules	Duplicate HTTPS or domain redirect logic

If the admin dashboard is inaccessible, a developer can review WP_HOME and WP_SITEURL in wp-config.php. Handle this carefully because a wrong value can keep the loop active.

Server redirect conflicts

Server rules can create redirect loops when the pattern is too broad. For example, a rule may redirect an old URL to a destination that still matches the same rule. The browser then enters the rule again.

This often happens in .htaccess, Nginx config, hosting-level redirect tools etc. The safest approach is to inspect the redirect chain before adding another redirect.

How to recognize too many redirects on your website

Start by checking whether the issue affects everyone or only one browser. Open the page in an incognito window, then test from another device or network. If the page fails everywhere, move from browser checks to technical diagnosis.

A redirect-chain check gives faster clarity than guessing.

Useful checks:

• Open DevTools and review the Network tab.
• Use a redirect checker to inspect each hop.
• Test http://, https://, root domain, www etc.
• Ask the developer to run curl -I for the affected URL.
• Compare CDN behavior with direct origin behavior where possible.

The key is to find the repeating step. Once the repeated hop is visible, the fix becomes more specific.

Symptom	Likely layer
Only one browser fails	Cookies or cache
Every device fails	Server, CDN, DNS, or CMS
Only HTTPS version fails	SSL or force-HTTPS rule
Only www version fails	Canonical domain conflict
Only WordPress admin fails	Plugin, session, or site URL setting
Only checkout/login fails	Session, cookie, or application rule

How to fix redirected too many times

Fix the loop based on the layer that causes it. Browser-side fixes are safe for one user, while site-wide loops need DNS, SSL, CMS, CDN, or server review.

Clear cookies on the redirecting website

Cookies can store old session or location data that sends one user back into a loop. This is common on login pages, membership pages, checkout flows etc.

Clear cookies for the affected domain first, then reload the page. If the issue disappears only for that browser, the site may still need a session or cookie review. When every browser fails, continue with technical checks.

Clear browser cache

Browser cache can keep old redirects after a domain or HTTPS change. A hard refresh or incognito test can reveal whether the browser is holding outdated behavior.

This step helps users, but it rarely solves a site-wide loop. If multiple visitors report the same issue, the technical owner should inspect redirect rules instead of relying on cache clearing.

Ensure SSL certificate is properly installed

SSL issues can trigger loops when the website forces HTTPS before the certificate and origin configuration are aligned. Start by confirming that the certificate is valid and installed on the right host.

Check these items:

Item	Why it matters
Valid certificate	HTTPS needs a trusted certificate
Canonical protocol	Site should settle on one HTTPS version
Force-HTTPS rule	Duplicate rules can conflict
Mixed CDN/origin behavior	Proxy settings can change the request path

For recently migrated websites, test both old and new protocol versions. The loop may only appear on one entry point.

Check third-party services such as Cloudflare

CDN or proxy services can change the redirect path before the request reaches your server. Cloudflare’s troubleshooting guide specifically lists Flexible SSL, Full SSL, Full strict, Always Use HTTPS, HSTS, and redirect rules as areas to review when ERR_TOO_MANY_REDIRECTS appears.

A practical review order:

1. Confirm the origin server supports HTTPS.
2. Check Cloudflare SSL/TLS mode.
3. Review edge redirect rules.
4. Disable duplicate HTTPS forcing where needed.
5. Test the redirect chain again.

For business-critical templates such as checkout or login, ask the CDN owner and developer to review this together. A CDN-only change can hide an origin-level issue.

Check DNS records after custom domain setup

Custom domain errors often come from DNS records that point to the wrong service or conflict with a default domain setting. This can happen when the root domain and www version do not follow the same canonical direction.

Review:

DNS item	What to check
A record	Points to the correct platform IP
CNAME	Points to the correct platform host
Duplicate records	Avoid conflicting values
Default domain	Match platform publishing settings

After DNS changes, wait for propagation before changing settings again. Repeated edits can make diagnosis harder because the redirect path may shift while records are still updating.

Check your plugins

Plugins can add redirect rules without making the chain obvious. In WordPress, recent SSL plugins, redirect managers, security tools etc. should be reviewed first.

Use a safe testing process:

• Disable the most recent redirect or SSL plugin first.
• Clear site cache after each change.
• Test the redirect chain again.
• Re-enable only the plugin that remains necessary.
• Keep one canonical HTTPS or domain rule.

Avoid disabling all plugins on a live revenue page without staging or hosting support. For high-priority pages, use a controlled test window.

Reset or review the .htaccess file

For Apache websites, .htaccess can create redirect loops when rules overlap. A broad redirect pattern may keep matching the destination URL, sending the browser back through the same rule.

If the site uses Apache, review the exact 301 redirect in .htaccess before adding another rule, especially after a migration or HTTPS cleanup.

Risky pattern	Why it loops	Safer direction
Old URL redirects to a pattern that still matches the old rule	Browser keeps entering the same rule	Anchor the pattern or exclude the destination
Plugin and server both force HTTPS	Two layers compete	Keep one canonical HTTPS rule
Root redirects to www, then www redirects to root	Domain canonical conflict	Choose one default domain

Back up the file before editing. If the loop affects every page, ask the developer to inspect the server rule before adding more redirects.

Reach out to your hosting provider

Hosting support can help when the loop involves server configuration, SSL installation, cache layers, or platform routing. Send clear context so the support team can reproduce the issue quickly.

Include:

• Affected URL
• Redirect-chain screenshot
• Recent change history
• DNS provider
• CDN status
• CMS or plugin changes
• Business priority of the affected template

For a homepage, checkout, lead form, account page etc., mark the ticket as urgent. The business impact is higher because users cannot continue their main path.

What to check after fixing the redirect loop

After the loop is fixed, review the affected user path again. A redirect loop may hide another issue, especially when old URLs were pointing to deleted pages.

Check whether Google has discovered broken destination URLs and follow a separate 404 error fix process in Google Search Console if old redirect targets now return missing-page errors.

If some old URLs should remain unavailable after cleanup, use clear 404 page examples as a reference for recovery copy, search paths, and helpful next steps. The user still needs a clear route when a page is intentionally gone.

FAQ about redirected too many times

What causes ERR_TOO_MANY_REDIRECTS after HTTPS migration?

HTTPS migration can create a loop when several layers force HTTPS at the same time. A plugin, server rule, CDN setting etc. may each redirect the request. Trace the redirect chain first, then keep one canonical HTTPS rule.

Is redirected too many times a browser problem or website problem?

It can be either. If only one browser fails, cookies or cache may be involved. When the same URL fails across devices, the issue usually sits in DNS, SSL, CDN, CMS, server rules etc.

Can Cloudflare Flexible SSL cause too many redirects?

Yes. Cloudflare explains that Flexible SSL can create a loop when Cloudflare connects to the origin through HTTP, while the origin redirects HTTP to HTTPS. Switching SSL mode or adjusting origin behavior can resolve the conflict.

How do I check the redirect chain?

Use DevTools Network, a redirect checker, or curl -I to view each redirect hop. The repeated hop reveals the source of the loop. After that, check the layer responsible for that hop, such as CDN, CMS, DNS, or server rules.

Why does my WordPress site keep redirecting after plugin changes?

WordPress redirect loops often happen when plugins change HTTPS, login, cache, or redirect behavior. Check recently updated plugins first. Also review WordPress Address, Site Address, .htaccess, server cache etc. before changing unrelated settings.

How long should I wait after changing DNS?

DNS propagation can take time depending on the domain provider, TTL, and hosting setup. During that window, avoid repeatedly changing records because each update can make the redirect path harder to diagnose.

Final thoughts

The redirected too many times error should be handled as a redirect-chain problem, not just a browser warning. Start by checking whether the issue affects one user or the whole site, then trace where the URL repeats.

For business-critical pages, assign the right owner quickly. The marketer can identify affected templates and traffic impact. The developer can inspect server rules. The CDN or hosting owner can verify SSL and proxy behavior. When those checks are connected, the fix becomes faster and safer for users.