Skip to content
Glitchary
ERR_TOO_MANY_REDIRECTS6 troubleshooting steps3 sources linked

ERR_TOO_MANY_REDIRECTS: check cookies, then the website

Chrome reports too many redirects when a page keeps sending you elsewhere. Try deleting that site's cookies; a persistent loop may need the website owner to repair its redirects.

By Glitchary · Updated · 2 min read

The short version

  1. 01Record the failing address and exact redirect error.
  2. 02Delete cookies for the affected site in Chrome, allowing for a sign-out and lost site preferences.
  3. 03Reload the original address and sign in again if the website requires it.
  4. 04Compare the same address in another browser to gather evidence about the scope of the failure.
  5. 05Send the URL and comparison results to the website owner if the loop continues.
  6. 06As the owner, align origin HTTPS behavior with edge settings and remove conflicting redirect rules.

Raw message

ERR_TOO_MANY_REDIRECTS

Likely causes

  • Cookies for the affected website may be causing incorrect redirects.
  • The website has conflicting redirects between URLs or between HTTP and HTTPS.
  • On a Cloudflare site, origin redirects may conflict with the SSL/TLS encryption mode or edge HTTPS settings.

Visitors: remove the affected site's cookies

Google says Chrome has encountered too many redirects and that cookies can sometimes cause the problem. Start with that site's cookies. Deleting them can sign you out and remove saved preferences for the site.

On a computer, open Chrome Settings > Privacy and security > Third-party cookies > See all site data and permissions. Search for the website, delete its entry and confirm. Reload the original address afterward.

Google Chrome: connection errors and too many redirectsGoogle Chrome: delete and manage cookies

Use a comparison to decide who should investigate

Our recommendation is to try the exact address in another browser. A working comparison gives useful evidence about the browser session; failure in both gives the owner a reproducible test. Neither result alone identifies the faulty setting.

If deleting site cookies does not help, send the owner the URL, time, browser and test results. A visitor cannot change the website's redirect rules; Cloudflare directs questions about origin redirects to the host or site administrator.

Google Chrome: connection errors and too many redirectsCloudflare: troubleshoot ERR_TOO_MANY_REDIRECTS

Owners: align redirects and HTTPS settings

Cloudflare documents loops caused by conflicting URL rules or HTTPS settings. With Flexible mode, it contacts the origin over HTTP; an origin that immediately redirects to HTTPS creates a loop. With Full or Full (strict), an origin redirect back to HTTP can also loop.

Use Cloudflare's configuration-specific remedies below. If moving to Full or higher, configure an origin certificate first. Check edge HTTPS settings and origin redirects together, and remove rules that send requests back to an earlier URL. Our recommendation is to have the host preserve a consistent HTTPS destination while correcting the conflict.

Cloudflare: troubleshoot ERR_TOO_MANY_REDIRECTS

Sources and review notes

Checked on . Based on Google's Chrome error and cookie guidance and Cloudflare's redirect-loop documentation. Cross-browser comparison and recording results are editorial guidance. The Cloudflare settings section applies to site owners using that service. Glitchary is independent of Google and Cloudflare.

Tags

chromebrowserredirectredirect-loopcookiescloudflarehttps