What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Delete the affected website’s cookies in Chrome, then reload the page. Google Chrome Help identifies this message as a page that has “tried to redirect you too many times” and recommends deleting the site’s cookies when cookies are not working correctly.
If that does not solve it, use Incognito, temporarily disable extensions, and test the URL in another browser or on another network. Those checks show whether the loop comes from saved browser data or from the website’s own redirect configuration.
As an Amazon Associate I earn from qualifying purchases.
What “too many redirects” means
Chrome’s ERR_TOO_MANY_REDIRECTS message describes a redirect loop. A redirect is an instruction that sends your browser from one URL to another. A loop occurs when the destination sends you back to an earlier URL, or when several URLs keep sending the browser around the same chain. Chrome stops following the chain instead of displaying a page.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11This is not the same as a missing page, an incorrect password, or a normal temporary loading delay. The address can be valid while the instructions between the addresses are inconsistent.
#1 Best Overall
There are two broad possibilities:
- Browser-side state: Cookies, cached site data, or an extension can cause the site to make a redirect decision based on stale or conflicting information.
- Website-side rules: The site can be configured to send visitors between HTTP and HTTPS, between two hostnames, or between login and non-login pages in a loop. MDN Web Docs notes that “Most of the time this is a server problem,” although damaged cookies or cache can occasionally make the problem local to your browser.
First, establish the scope of the failure
Check the address and reload once
- Read the address carefully. Make sure the domain and path are the one you intended to open, without a typo or an old bookmark pointing to a different version of the site.
- Reload the page once. Repeatedly refreshing a loop does not repair the redirect rules and can make it harder to tell whether a later test changed anything.
- Note whether the error appears before or after you sign in. This helps you describe the failure to the site owner if the problem is server-side.
Try a second page on the same site
Open the site’s home page and one other ordinary page, if you can do so without repeatedly following the failing link. If only one domain or one path fails, start with that site’s cookies. If several unrelated sites fail, a browser-wide setting, extension, network, or security product is more likely than one website’s redirect rule.
Protect anything you may need to sign in again
Deleting cookies can sign you out and remove saved preferences for that site. Before removing them, make sure you know the account’s sign-in method and have access to any required verification device. Site-specific deletion limits this disruption compared with wiping every cookie in Chrome.
Fix the affected site’s cookies first
This is the narrowest and most directly recommended remedy. Google Chrome Help specifically advises deleting cookies when cookies are not working correctly.
Use Chrome’s settings
- Open Chrome’s three-dot menu and choose Settings.
- Open Privacy and security, then open the section for Third-party cookies or site data. Chrome’s wording can vary by version.
- Choose See all site data and permissions (or the equivalent list of stored site data).
- Search for the affected domain. Include the site’s main domain rather than searching for a complete page address.
- Delete the entries for that domain, confirm the removal, and close the settings tab.
- Return to the original tab and load the URL again.
Chrome also provides a site-data page through its settings address, chrome://settings/content/all. If that internal address is unavailable in your edition, use the menu path instead.
What this test tells you
If the page opens after site-specific cookies are removed, the previous browser state was involved. You may need to sign in again, and the site may forget choices such as language or consent settings. That is an expected side effect of deleting cookies, not evidence that the page itself was removed.
Why deleting cookies can stop a loop
Sites commonly use cookies to remember a session or a preference that affects where the browser is sent next. If a cookie is stale, malformed, or inconsistent with the site’s current session, the site can keep sending the browser to a page that sends it back. Removing the stored value lets the site create a fresh session on the next visit. This is why clearing only the affected domain is a better first move than erasing all browsing data.
Use Incognito to separate saved data from the website
Open an Incognito window from Chrome’s three-dot menu, then enter the URL manually or paste it into the new window. Incognito starts without the ordinary window’s saved cookies and site data. Extensions also do not normally run there unless you have explicitly allowed them.
- It works in Incognito: Saved cookies, other site data, or an extension in the regular profile is a strong suspect. Close Incognito, clear the affected site’s data in the regular profile, and continue with the extension test below.
- It fails in Incognito too: The cause is less likely to be a cookie held only in your normal profile. Continue by testing extensions, another browser, and another network.
Incognito is a diagnostic comparison, not a permanent repair. A site can still fail there if its own redirect instructions are wrong.
Temporarily disable extensions
An extension that modifies pages, cookies, headers, privacy settings, or network requests can interfere with a site’s redirect process. Disable extensions only long enough to test the failing URL.
- Open Chrome’s three-dot menu, choose Extensions, and open Manage extensions.
- Turn off every extension, or begin with extensions that alter privacy, scripts, shopping, authentication, or traffic.
- Reload the affected URL in a normal window.
- If the page now works, turn extensions on one at a time and reload after each change. The failure returning after one extension is enabled identifies a likely conflict.
- Leave the conflicting extension disabled, remove it, or check its own settings for a site-specific exception.
If disabling extensions changes nothing, turn them back on before moving to the next test. This keeps the browser in its normal state while you continue diagnosing.
Test another browser and another network
Another browser
Open the same URL in a different browser on the same computer. A successful load there points toward Chrome’s profile, cookies, cache, or extensions. A redirect loop in both browsers makes a website-side problem more likely, although a shared network or security filter can still affect both.
Recommended Free Tools
Another network
If practical, try a different connection, such as a phone hotspot instead of the usual Wi-Fi. This can reveal a network-specific login page, filtering rule, or DNS-related redirection. Do not assume that a network change proves the website is healthy: it only shows that the result differs between connections.
Best Value
Interpret the combinations
| Result | Most useful interpretation | Next action |
|---|---|---|
| Normal window fails; Incognito works | Saved site data or a regular-profile extension is implicated | Delete the affected site’s cookies, then test extensions individually |
| Both Chrome windows fail; another browser works | Chrome-specific state or configuration remains likely | Check extensions and site data; avoid erasing all browsing data first |
| Several browsers fail on one network | A website rule or network-specific redirection is possible | Try another network and gather the exact URL and symptoms |
| The URL fails in different browsers and networks | The website’s redirect configuration is the leading explanation | Contact the site owner or administrator |
When broader browser cleanup is justified
Do not repeatedly clear all browsing data as your first response. A full cookie purge signs you out of many services and removes unrelated preferences, while it provides less precise diagnostic information than deleting one site’s data.
Consider broader cleanup only after the affected-site deletion, Incognito test, and extension check have not isolated the cause, and only if multiple sites are showing related failures. Review Chrome’s deletion choices carefully so you understand which cookies, cached files, passwords, and other data will be removed. Preserve credentials before confirming. If the problem is limited to one domain, return to the site-specific method instead of expanding the deletion.
Recognize a server-side redirect problem
A loop that survives a clean Incognito session, another browser, and another network is usually outside your control. MDN describes most redirect-loop failures as server problems. The site may have conflicting HTTP/HTTPS rules, hostname aliases, login redirects, or a proxy configuration that sends every request back to an earlier step.
There is no Chrome setting that can correct a redirect rule delivered by the website. Contact the site’s owner, support team, or administrator and include:
- The complete URL, including the path where the loop begins.
- The date and approximate time of the failure.
- Whether the issue affects one page, the entire domain, or only the signed-in area.
- Whether site-specific cookie deletion changed anything.
- The results of Incognito, another browser, and another network tests.
- Whether you were signed in when the loop occurred.
Those details let the administrator distinguish a browser-session problem from a redirect rule that affects visitors generally. Avoid repeatedly retrying the same loop while waiting for a fix; use a known working page or ask the site for a current URL if one exists.
Quick Recap
Common mistakes that make diagnosis harder
- Deleting every cookie immediately: This creates unnecessary sign-outs and removes useful evidence about which site caused the problem.
- Testing only by refreshing: Refreshing does not change a server-side redirect chain.
- Changing several things at once: If you clear cookies, disable extensions, and switch networks simultaneously, you cannot tell which condition mattered.
- Assuming Incognito guarantees a fix: It removes much local state, but it cannot repair incorrect instructions from a website.
- Ignoring the exact URL: A bookmark or copied link can point to an obsolete path even when the domain itself works.
- Leaving extensions disabled indefinitely: Re-enable unaffected extensions after testing so your normal browser setup is restored.
A concise decision path
- Confirm the URL and reload once.
- Delete cookies and site data for that domain only, then retry.
- Test the same address in Incognito.
- If necessary, disable extensions and identify a conflict one at a time.
- Compare another browser and, where possible, another network.
- If the loop persists across clean sessions and different contexts, report it to the website owner with the test results.
As an optional shortcut after these manual checks, Outbyte PC Repair can look for common Windows issues, adjust selected system settings, clean temporary and cache files, and provide an app-crash log. It runs on Windows 11, 10, 8, and 7, offers a category-based free trial of at least two days, and then requires a subscription; it complements antivirus software rather than replacing it, and results vary.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
