Device-specific

    ERR_TOO_MANY_REDIRECTS on Chrome

    Why it happens on Chrome

    The loop is usually stored in a cookie, so Chrome keeps redirecting even after the server-side rule is fixed.

    The fix on Chrome

    Click the padlock → Cookies and site data → Manage on-device data → Delete the domain's cookies, then reload. If a fresh incognito window works, cookies were the cause.

    Is ERR_TOO_MANY_REDIRECTS happening on your domain?

    The uptime probe returns the full redirect chain, so you can see the exact two URLs bouncing off each other instead of inferring it from behaviour.

    Free, no signup. Runs from outside your network, which is the only way to tell a server fault from a local one.

    If that didn't fix it

    Chrome has its own failure mode, but ERR_TOO_MANY_REDIRECTS has a wider set of causes that apply everywhere. The most common one overall is: the cdn forwards to the origin over http while the origin redirects all http to https — an infinite loop.

    All causes and fixes for ERR_TOO_MANY_REDIRECTS

    ERR_TOO_MANY_REDIRECTS on other platforms and devices

    Monitor this continuously with LemWatch

    A one-off err_too_many_redirects monitoring shows you today. LemWatch re-runs the same checks around the clock and alerts you the moment something breaks — free for up to 10 sites, no card needed.

    Last verified: by the Lemwatch research team.