
You open a website in Google Chrome and instead of the page you get a grey error screen that says “This page isn’t working” with the code ERR_TOO_MANY_REDIRECTS — the moment you start searching for a chrome err_too_many_redirects fix. This chrome err_too_many_redirects fix guide walks you through the exact cause of the error and eight proven ways to clear it.
In plain terms, a redirect happens when a website sends your browser from one address to another. When that chain loops back on itself — address A sends you to B, and B sends you back to A — Chrome gives up and shows this error. The loop can be caused by your browser’s stored cookies, a misconfigured site, an HTTPS redirect problem, or a faulty extension.
The good news is that most cases are fixed in under five minutes. The fixes below start with the simplest checks and move toward deeper causes, so work through them in order until the page loads.
Table of Contents
- Quick Checks for the chrome err_too_many_redirects fix
- Diagnose the Problem
- Fix 1: Hard Refresh the Page
- Fix 2: Clear Cookies for That Site
- Fix 3: Clear All Browsing Data
- Fix 4: Disable Extensions and Test in Incognito
- Fix 5: Check the URL and Try HTTP vs HTTPS
- Fix 6: Fix Your Computer’s Date and Time
- Fix 7: Reset Chrome Settings
- Fix 8: Clear the Host Resolver Cache
- What to Avoid
- Frequently Asked Questions
- Conclusion
- Helpful Resources
Quick Checks for the chrome err_too_many_redirects fix
- Press Ctrl + F5 (or Cmd + Shift + R on a Mac) for a hard refresh that skips the cache.
- Open the same link in an Incognito window (Ctrl + Shift + N) — if it works there, the problem is in your normal profile’s cookies or extensions.
- Check the address bar: a link starting with http:// on a site that forces https:// can trigger a loop.
- Try the site on your phone or another device to see if the problem is your browser or the site itself.
- Make sure your computer’s date and time are correct — a wrong clock breaks secure connections.
- If the problem started today, the site owner may have broken a redirect rule — check the site’s social media or status page.
Diagnose the Problem
| Symptom | Cause | Go to Fix |
|---|---|---|
| Error appears on one site only, worked yesterday | Corrupt or mismatched cookies for that site | Fix 2 |
| Error appears on many sites at once | Damaged browsing data or a bad extension | Fix 3, Fix 4 |
| Error appears in normal windows but not Incognito | Cookies or extensions in your main profile | Fix 2, Fix 4 |
| Error mentions redirecting between http and https versions | Site’s HTTPS redirect rule is looping | Fix 5 |
| Error started after installing a new extension | Extension interfering with navigation | Fix 4 |
| Error appears on sites with login pages | Session cookie conflicting with the site’s login redirect | Fix 2 |
| Error on every page plus certificate warnings | Wrong system date and time | Fix 6 |
| Error persists after clearing everything | Deep Chrome data corruption | Fix 7, Fix 8 |
Fix 1: Hard Refresh the Page
A normal refresh often reloads the page from memory. A hard refresh tells Chrome to fetch everything fresh from the server, which is sometimes enough to break a stuck redirect loop.
- Click inside the address bar and press Enter again.
- Or press Ctrl + F5 on Windows and Linux.
- On a Mac, press Cmd + Shift + R.
- Wait for the page to load fully before clicking anything else.
- If the error still appears, move on to Fix 2.

Fix 2: Clear Cookies for That Site
This is the single most effective chrome err_too_many_redirects fix. Websites use cookies to remember your session, and a redirect loop almost always involves a stale or conflicting cookie. Clearing cookies for just the affected site keeps you signed in everywhere else.
- Click the lock icon (or the tune icon) at the left of the address bar.
- Click Cookies and site data.
- Click Manage on-device site data.
- Select the site that shows the error and click the delete (trash) icon next to it.
- Click Done, then reload the page.
- If the error continues, repeat the steps and delete every entry that mentions the site’s domain.
An alternative route through settings:
- Open Chrome’s menu (three dots, top right) and go to Settings.
- Go to Privacy and security and click Third-party cookies.
- Click See all site data and permissions.
- Search for the site’s name, click the trash icon next to it, and confirm.
Fix 3: Clear All Browsing Data
If the error appears on several websites, the corruption may be wider than one site’s cookies. Clearing all browsing data resets cached files and cookies across the board.
- Press Ctrl + Shift + Delete to open the Clear browsing data window.
- Set the time range to All time.
- Tick Cookies and other site data and Cached images and files.
- Leave browsing history ticked or unticked as you prefer — it is not required for this fix.
- Click Clear data and wait for the process to finish.
- Close Chrome completely and reopen it, then test the site again.

Note that this signs you out of every website. Keep your important passwords saved in Chrome’s password manager (or another password manager) before you do this so signing back in is painless.
Fix 4: Disable Extensions and Test in Incognito
Extensions can rewrite web requests, force HTTPS upgrades, or inject scripts that confuse a site’s redirect logic. Testing in Incognito tells you whether an extension is the cause, because extensions are off by default there.
- Press Ctrl + Shift + N to open an Incognito window.
- Visit the same website in the Incognito window.
- If the page loads normally, an extension (or cached data) in your main profile is the problem.
- Go back to your normal window and type chrome://extensions in the address bar.
- Turn off all extensions using the toggle switches.
- Reload the problem site. If it works, turn extensions back on one at a time, reloading the page after each, until the error returns — the last one you enabled is the culprit.
- Remove the faulty extension or look for an update to it.
Pay special attention to ad blockers, VPN extensions, privacy tools, and HTTPS-forcing extensions, since these are the ones most likely to interfere with redirects.
Fix 5: Check the URL and Try HTTP vs HTTPS
Some redirect loops live in the link itself rather than your browser. A site might redirect its HTTP address to HTTPS and its HTTPS address back to HTTP, creating a loop no browser setting can fix from your side — but you can still confirm it and work around it.
- Look at the address bar and note whether the address starts with http:// or https://.
- Try typing the https:// version manually and press Enter.
- Then try the plain domain without www (for example, example.com instead of www.example.com).
- Try the www version as well.
- If the loop only happens in one combination, bookmark the working version.
- If every combination fails, the site’s server configuration is broken and you should contact the site owner or wait for them to fix it.

For website owners reading this: check your server or CDN redirect rules so that HTTP-to-HTTPS happens exactly once and never points back to HTTP.
Fix 6: Fix Your Computer’s Date and Time
Secure websites check your computer’s clock when setting up an encrypted connection. If your clock is hours, days, or months off, the security handshake fails and Chrome can show a redirect error — or get stuck mid-redirect — especially on login pages.
- On Windows, right-click the clock in the taskbar and choose Adjust date and time.
- Turn on Set time automatically and Set time zone automatically.
- Click Sync now to force an immediate update.
- On a Mac, open System Settings, go to General, then Date & Time, and turn on Set time and date automatically.
- Close and reopen Chrome, then reload the problem site.
- If the clock keeps drifting after every restart, your computer’s CMOS battery may need replacing — a hardware shop can swap it cheaply.
Fix 7: Reset Chrome Settings
If none of the targeted fixes worked, your Chrome profile may hold a broken setting deep in its configuration. Resetting restores Chrome’s defaults without deleting your bookmarks, history, or saved passwords.
- Open the Chrome menu and go to Settings.
- Click Reset settings in the left sidebar.
- Click Restore settings to their original defaults.
- Read the confirmation — it lists exactly what will change — and click Reset settings.
- Restart Chrome and test the problem site.
- If the error is gone, reconfigure any settings you had customized, one section at a time.

Fix 8: Clear the Host Resolver Cache
Chrome keeps its own internal DNS cache, separate from your operating system’s. A stale entry here can keep sending you to a server address that no longer answers correctly, sustaining a redirect loop.
- Type chrome://net-internals/#dns in the address bar and press Enter.
- Click the Clear host cache button.
- Next, type chrome://net-internals/#sockets and press Enter.
- Click Close idle sockets and then Flush socket pools.
- Close Chrome completely and reopen it.
- Visit the problem site again to confirm the loop is gone.
This fix is safe: it only clears temporary network data, not your bookmarks, passwords, or history.
What to Avoid
- Do not install “redirect fixer” extensions from unknown developers — many are adware in disguise and official Chrome needs none of them.
- Do not download registry cleaners or “PC optimizers” that promise to fix browser errors; they cannot fix a redirect loop and often cause new problems.
- Do not disable your antivirus as a troubleshooting step — it is unrelated to this error and leaves you exposed.
- Do not keep reloading the page hundreds of times hoping it resolves; it will not, and on some sites it can trigger rate limiting.
- Do not edit the Windows registry based on random forum advice — this error never requires registry changes.
- Do not share your screen or passwords with anyone who contacts you claiming they can fix the error remotely.
Frequently Asked Questions
What does ERR_TOO_MANY_REDIRECTS mean?
It means the website sent your browser in a circle: page A redirected to page B, which redirected back to page A, over and over. Chrome stops after a set number of hops and shows this error instead of looping forever.
Is ERR_TOO_MANY_REDIRECTS caused by a virus?
No. It is caused by redirect logic — usually a bad cookie, a misconfigured site, or an interfering extension. It is not a sign of malware, and you do not need a special removal tool for it.
Why does the error appear on only one website?
That website’s cookies or its server redirect rules are the cause. Clearing that site’s cookies (Fix 2) resolves most single-site cases without affecting anything else.
Why does the site work in Incognito but not in a normal window?
Incognito starts with no stored cookies and most extensions disabled. The difference proves the problem lives in your main profile’s cookies or extensions, which is why Fix 2 and Fix 4 target exactly those.
Will clearing cookies delete my saved passwords?
No. Cookies and saved passwords are stored separately. Clearing cookies signs you out of websites, but your saved passwords in Chrome’s password manager stay intact.
Can my VPN cause ERR_TOO_MANY_REDIRECTS?
It can contribute. Some VPNs and VPN extensions rewrite requests or change your location mid-session, which confuses sites that redirect based on region. Try disabling the VPN temporarily to test.
The error is on my own WordPress site. What should I check?
Check your site address settings (WordPress Address and Site Address must match and use the same protocol), your SSL plugin’s redirect settings, and any CDN page rules. Redirecting HTTP to HTTPS must happen exactly once.
How do I know whether the problem is the site or my browser?
Open the site on a different device or in Incognito. If it fails everywhere, the site’s server is misconfigured and only the site owner can fix it. If it works elsewhere, the fixes in this guide will sort it out.
Conclusion
The chrome err_too_many_redirects fix is usually quick: a hard refresh, clearing the site’s cookies, or disabling a faulty extension solves the vast majority of cases. When the loop is caused by the website’s own server rules, the diagnosis steps above help you confirm that nothing on your side is wrong, so you can contact the site owner with confidence. Work through the fixes in order, and keep your browser updated so future redirect handling stays reliable.

[…] a site traps you in a loop of redirects when you navigate forward, our guide to Chrome ERR_TOO_MANY_REDIRECTS fix covers that separate […]