← Back to Troubleshooting

How to Fix ERR_TOO_MANY_REDIRECTS (This Page Isn't Working)

2 min read •
Beginner Redirect Error Chrome Fix

Chrome shows: "This page isn't working. [website] redirected you too many times. ERR_TOO_MANY_REDIRECTS."

This means the website is stuck in a redirect loop — page A sends you to page B, which sends you back to page A, endlessly. Your browser gives up after about 20 redirects.

Fix 1: Clear Cookies for That Site

The #1 fix. A corrupted cookie can cause a redirect loop:

Chrome:

  1. Click the padlock icon in the address bar
  2. Click Cookies (or Site settings)
  3. Click Remove or Delete for that site
  4. Refresh the page

Or clear all cookies: Ctrl + Shift + Delete → "All time" → check "Cookies and other site data" → Delete

Warning: Clearing all cookies logs you out of every website.

Fix 2: Try Incognito Mode

Ctrl + Shift + N → visit the same URL. Incognito has no cookies — if it works, a cookie is causing the loop.

Fix 3: Check the URL

Some redirect loops happen because of URL variations:

  • Try https://www.example.com instead of https://example.com
  • Try without the trailing path
  • Try http:// instead of https://

Fix 4: Clear Browser Cache

Ctrl + Shift + Delete → "Cached images and files" → Delete

Fix 5: Disable Browser Extensions

Extensions (especially ad blockers and privacy tools) can modify redirect behavior:

  1. chrome://extensions/
  2. Disable all
  3. Try the site

Fix 6: Check VPN/Proxy

VPNs and proxies can create redirect loops if the website behaves differently based on your location:

  • Disable VPN → try the site
  • Disable proxy settings → try the site

For Website Owners

If YOUR site has this error, the problem is in your server configuration:

Common Causes

1. HTTP → HTTPS + HTTPS → HTTP loop

Your server redirects HTTP to HTTPS, but something else redirects HTTPS back to HTTP: 

http://example.com → 301 → https://example.com → 301 → http://example.com → ...

Fix: Check your nginx/Apache config. A common cause is Cloudflare SSL set to "Flexible" while your server also redirects to HTTPS. Set Cloudflare SSL to "Full (strict)".

2. www ↔ non-www loop 

example.com → 301 → www.example.com → 301 → example.com → ...

Fix: Pick one (www or non-www) and make ALL redirects go to it. Do not have conflicting rules.

3. WordPress redirect loop

Common with WordPress behind a reverse proxy or CDN:

  • Check wp_options table: siteurl and home should match your actual URL
  • Check .htaccess for conflicting redirect rules
  • Check wp-config.php for forced SSL settings

4. Cloudflare + server redirect conflict

If you use Cloudflare:

  • SSL/TLS → set to Full (strict) (not Flexible or Full)
  • Check Page Rules for conflicting redirects
  • Check "Always Use HTTPS" setting

How to Debug

Check the redirect chain: 

curl -I -L https://example.com 2>&1 | grep -E "HTTP/|Location:"

Or use our HTTPS Redirect Tester to see the full redirect chain.

Related Tools