Fix Tech Errors — Windows, Chrome & Software

Fix ERR_TOO_MANY_REDIRECTS in Chrome

ERR_TOO_MANY_REDIRECTS is Chrome’s redirect safety valve. When a site sends Chrome bouncing between URLs more than a set number of

ERR_CERT_COMMON_NAME_INVALID is Chrome’s way of saying: “This certificate exists and looks legitimate, but it wasn’t issued for the domain you’re

“Your connection is not private” is Chrome doing its job. When you see this error, Chrome detected a problem with

ERR_NETWORK_CHANGED has an unusually honest error message — Chrome detected that the network connection changed while a page was loading,

Connection refused is one of the most definitive network messages a browser can receive. Unlike a timeout — where Chrome

ERR_NAME_NOT_RESOLVED is Chrome’s way of telling you the DNS lookup for the site you’re trying to reach came back completely

Chrome’s ERR_TIMED_OUT error looks like a connection problem — but in most cases the website is fine. The real culprit

ERR_CONNECTION_RESET in Chrome is one of the trickier network errors because the connection was actually established — the TCP handshake

DNS_PROBE_FINISHED_NXDOMAIN is one of the more informative Chrome error codes — if you know how to read it. NXDOMAIN is

“This site can’t be reached” is Chrome’s catch-all network error — it covers everything from a simple DNS lookup failure