ERR_TOO_MANY_REDIRECTS means the site sent your browser to another address, which sent it back, and that became an endless circle. The browser gives up after a few laps and shows the error. In the overwhelming majority of cases the culprit is an old cookie stored on your computer for that specific site: deleting only that cookie fixes it (Solution 2). Before that, open the same address in a private window (Solution 1) - if it works there, cookies or an extension are confirmed as the cause and you can skip the rest. If the site is not yours and the error shows up in every browser and on another device, the problem is on the server and there is nothing to do on your end but wait. If the site is yours, go straight to Solution 7, which covers the loop between HTTP, HTTPS and www.
What causes this problem
- An old or corrupted cookie for that site, stored in your browser, making the server send you back to the same page over and over.
- An expired login session: the site tries to send you to the login screen, the login thinks you are already authenticated and sends you back to the page, in a loop.
- A browser extension that rewrites addresses, forces HTTPS or blocks trackers, breaking the site's legitimate redirect.
- A misconfiguration on the site's server: an HTTP-to-HTTPS or www-to-non-www rule that points at itself.
- A proxy, VPN or CDN service in the middle serving a version of the page that asks for yet another redirect.
- Wrong date and time on the computer, which invalidates session cookies the moment they are created.
- Open the same address on your phone using mobile data rather than the home Wi-Fi. If it works there, the problem is your computer or your network; if it fails too, it is the site.
- Write down the exact address that fails, including whether you typed www or not, and http or https. That difference is usually the main clue.
- Check that the computer's date and time are correct. A wrong clock invalidates session cookies and creates loops no other fix will clear.
- Know in advance that deleting a site's cookies signs you out of your account there. Have the password ready before doing it.
- If the site is yours or your company's, have access to the hosting control panel ready - the last solutions depend on it.
Solutions, in the order to try them
1Test in a private window to confirm the cause
A private window opens with no cookies and, in most browsers, no extensions. It is the fastest way to separate a problem on your side from a problem on the site's side. It is not the fix itself, it is the diagnosis that decides where to go next.
- Open a private or incognito window from the three-dot or three-line menu in the top right corner of the browser.
- Paste the same address that was failing and load it.
- If the page opens normally, the cause is your cookies or an extension: go to Solution 2 and then Solution 3.
- If the error looks the same in the private window, jump to Solution 5 and, if the site is yours, to Solution 7.
2Delete the cookies for that one site
This is the fix that resolves most cases. Clearing everything works too, but it signs you out of every site and is unnecessary: you can remove the data for the problem address alone and leave the rest intact.
- With the error page open, click the padlock or the settings icon to the left of the address, in the address bar.
- Look for the cookies and site data option (the name varies: Cookies and site data, Site settings, Site information).
- Choose the option to delete or clear this site's data and confirm.
- Close the tab, open a new one and type the address again. You will have to sign in to your account once more.
3Turn off your extensions, then re-enable them one by one
If the private window worked but clearing cookies did not, an extension is the culprit. The ones most often involved in this error are those that force secure connections, block trackers or manage a VPN, because all of them touch the address before it reaches the site.
- Open the extensions page from the browser menu (usually under Extensions or More tools).
- Switch them all off at once and reload the failing page.
- If it works, turn the extensions back on one at a time, reloading the page after each one, until the error returns.
- The last one you enabled is the culprit. Remove it or add the site to its exceptions list.
4Sign out and clear the stuck session
When the error only shows up after you sign in, or only in one part of the site (the dashboard, the cart, the subscriber area), the loop is between the login page and the destination page. The site thinks you are not authenticated, sends you to the login, the login thinks you are, and sends you back.
- Try opening the site's sign-out or logout address directly, if you know what it is.
- If you do not, delete that site's cookies as in Solution 2 - that ends the session anyway.
- Close every tab for the site and open its main address, with nothing added after the domain.
- Sign in again starting from that home page, not from the old link that was failing.
5Test the address in all four possible forms
Many loops happen between the www and the non-www version, or between the secure and the plain one. Testing each combination tells you which one works and which one is broken, and that is half the diagnosis if you have to report the problem.
- Type the address with https:// and with www in front of the domain.
- Then with https:// and without the www.
- Repeat both forms with http:// instead of https://.
- If one of them opens, use that version and tell whoever runs the site. If none opens, the server is at fault.
6Turn off VPN and proxy, and try another network
Services that route your connection through another country make some sites redirect to the local version for that region - and if that version redirects too, you get a loop. It is worth testing even if you use the VPN all the time with no trouble on other sites.
- Turn off any VPN or proxy active on the computer and in the browser.
- In the system network settings, check that there is no proxy server configured that you do not recognise.
- Reload the page on the direct connection.
- If it persists, test the same address using your phone as a hotspot, on a different connection, to rule out your network.
7If the site is yours: fix the redirect rule on the server
This is the cause when the error appears for everyone, in every browser. Some rule sends the visitor to an address which in turn sends them back. The most common case is having the same rule set up in two places at once: in the hosting panel and inside the site's own system.
- In the hosting panel, check whether an automatic redirect to HTTPS is switched on.
- In your content management system, check whether another plugin or setting is doing the same thing. Keep it active in one place only.
- Check the main address registered in the site settings: if it is set with www while the server redirects to non-www, the loop is guaranteed.
- If you use a CDN or proxy service in front of the site, check its encryption mode. A mode that speaks HTTP to the server while the server demands HTTPS creates exactly this loop.
- Make one change at a time and always test in a private window, so the cache does not mislead you.
8Clear the browser cache as a last step
If nothing above worked and the site is back up for other people, your browser may be holding on to the old redirect. Some redirect types get memorised and keep being applied even after the server has been fixed.
- Open the browser settings and look for the option to clear browsing data.
- Tick cached images and files as well as cookies, and choose the all-time range.
- Confirm, close the browser completely and open it again.
- If the error persists only on your computer, test in another installed browser to confirm the problem is local.
Applies to
| System | Status |
|---|---|
| Google Chrome, Microsoft Edge, Brave and Opera (desktop and mobile) | Confirmed |
| Mozilla Firefox | The wording differs, something like 'the page is not redirecting properly', but the cause and the fixes are the same |
| Safari on Mac, iPhone and iPad | The message mentions 'too many redirects'; per-site cookies live in Safari's settings, under Privacy |
Menu names can change slightly between versions. If a step above does not match what you see on screen, the official support page from the manufacturer has the most current wording for your version.
Frequently asked questions
Last checked: Jul 17, 2026 · We review this guide whenever the manufacturer changes the process.