- Software and digital services
- Web browsers
ERR_TOO_MANY_REDIRECTS
ERR_TOO_MANY_REDIRECTS in Google Chrome: redirect loop
Risk level
Low
Usually safe to check without specialist tools.
Urgency
Medium
Quick answer
The page redirected you too many times and Chrome stopped the loop. Cookies that are not working correctly sometimes cause it: delete that site's cookies and open it again. If it persists, the loop is on the site.
Safety first
Stop and check this first
- Do not delete every cookie in the browser if only one site fails: delete that site's cookies so you are not signed out everywhere.
Safe checks you can perform
- The page in Incognito mode
- That site's cookies
- The server's redirect chain
Leave these tasks to a qualified professional
- Do not attempt this professional task: Break the loop in the configuration
- Do not attempt this professional task: Test the fix with and without cookies
What a technician must be able to justify
Technician visit
These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.
These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.
Break the loop in the configuration
What they doThe developer finds the rules that send to each other (server, CDN or application) and fixes one of them.
They must show youthe redirect chain before and after.
In writingwhich rule was changed.
Test the fix with and without cookies
What they doAfter the change, the team opens the address in a clean session and in a signed-in one.
They must show youboth tests with no repeated redirects.
In writingtime and result of each test.
Before accepting a part or repair
Nothing has been shown yet. Do not accept a part swap based on the code alone.
Follow these steps
Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.
The page in Incognito mode
- Who:
- you.
- How:
- open the same address in an Incognito window.
- Result that matters:
- whether it loads there without a loop.
- If it loads in Incognito:
- it points to cookies or stored data; continue by deleting the site's cookies.
- If it loops there too:
- rule out your cookies; the loop is on the site.
- Evidence to keep:
- result in the normal window and in Incognito.
Evidence: Google Chrome Help - Fix connection and loading errors in Chrome
That site's cookies
- Who:
- you.
- How:
- delete the site's cookies from Chrome's cookie settings and open the address again.
- Result that matters:
- whether the loop disappears.
- If it disappears:
- the cookies were the cause.
- If it persists after deleting them:
- the loop is on the server; tell the site the exact address.
- Evidence to keep:
- the failing address and the time after deleting the cookies.
Deleting the cookies signs you out of that site; have your password at hand.
Evidence: Google Chrome Help - Get help with common error messages in Chrome
The server's redirect chain
- Who:
- the site operator or developer.
- How:
- follow the chain of 3xx responses with a tool that shows each Location header, from a session without cookies.
- Result that matters:
- which two addresses repeat in the chain.
- If the chain repeats without cookies:
- the server's redirect rules are the cause.
- If it only repeats with a particular cookie:
- it indicates the logic reading that cookie causes the loop.
- Evidence to keep:
- list of addresses and status codes in the chain, with the time.
Only the site operator or developer. If you do not run the site, do not do it: send the address to the operator.
Evidence: RFC 9110 - HTTP Semantics
Still not solved
If the error persists, stop here. See what the technician must do and show you.
Where this code applies
A code is meaningful only inside the right product and version context.
Primary scope
- System
- Software and digital services
- Brand
- Google Chrome
- Product type
- Web browsers
Known code variants
- ERR_TOO_MANY_REDIRECTS
- ERR_TOO_MANY_REDIRECTS (-310)
- ERR_TOO_MANY_REDIRECTS Chrome
- net::ERR_TOO_MANY_REDIRECTS
What it means
Chromium defines ERR_TOO_MANY_REDIRECTS (-310) as loading a URL that resulted in too many redirects. RFC 9110 says a client should detect and intervene in cyclical redirections, meaning infinite loops of 3xx responses with a Location header. Chrome Help adds that pages sometimes will not open because cookies are not working correctly. The loop can be in the server configuration or depend on a cookie held by the visitor.
Warnings and stop conditions
- Loweditorial warning
Do not delete every cookie in the browser if only one site fails: delete that site's cookies so you are not signed out everywhere.
Evidence: Google Chrome Help - Get help with common error messages in Chrome
Symptoms and causes
Probable causes · in order
- Site cookies not working correctlyPossible
The loop disappears when you delete that site's cookies or open it in Incognito.
Evidence: Google Chrome Help - Get help with common error messages in Chrome · Google Chrome Help - Fix connection and loading errors in Chrome
- Looping redirect rules on the sitePossible
Two server rules sending to each other. The loop appears in any browser and network, also without cookies.
Evidence: RFC 9110 - HTTP Semantics · Chromium source - net/base/net_error_list.h (network error list)
Virtual technician
Does ERR_TOO_MANY_REDIRECTS still appear after these checks?
Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.
Sources and technical references
- 1
IETF / RFC Editor · 2022 · standard
- 2
Chromium source - net/base/net_error_list.h (network error list)
The Chromium Authors · 2026 · official_doc
- 3
Google Chrome Help - Get help with common error messages in Chrome
Google · 2026 · official_doc
Was this entry useful?