Chrome, Edge
ERR_TOO_MANY_REDIRECTS
The browser followed redirect after redirect until it gave up. Two rules are almost certainly pointing at each other.
What causes it
- HTTPS redirecting to HTTP which redirects back to HTTPS — classic behind a proxy or CDN that terminates TLS.
- A www rule and a non-www rule in opposition.
- A CMS setting a canonical URL that conflicts with a server rewrite.
- A stale cookie that keeps triggering a login redirect.
If you are the visitor
- Clear cookies for that site — this fixes it surprisingly often.
- Try a private window.
If it is your website
- Trace the chain with a redirect checker and remove the rule closing the loop.
- Behind a CDN, honour X-Forwarded-Proto rather than the local scheme when deciding whether to redirect.
Find out whether the site is down for everyone
A live check from our server shares nothing with your network — it settles the question in seconds.
Other connection errors
ERR_CONNECTION_REFUSED
DNS_PROBE_FINISHED_NXDOMAIN
ERR_NAME_NOT_RESOLVED
ERR_CONNECTION_TIMED_OUT
ERR_SSL_PROTOCOL_ERROR
NET::ERR_CERT_AUTHORITY_INVALID
NET::ERR_CERT_DATE_INVALID
NET::ERR_CERT_COMMON_NAME_INVALID
ERR_EMPTY_RESPONSE
ERR_CONNECTION_RESET
503 Service Unavailable
502 Bad Gateway
This site can't be reached