Browse by category

Browser & network errors

Chrome and Edge codes like ERR_CONNECTION_RESET, TLS failures, and redirect loops.

• Axios network error (browser)Axios could not reach the server—no response object; often CORS, TLS, or offline.
• ERR_CONNECTION_RESETThe TCP connection was reset before a complete HTTP response—often network paths, proxies, or firewalls.
• ERR_SSL_PROTOCOL_ERRORThe TLS handshake failed or spoke the wrong protocol—often cert, cipher, or version mismatch.
• ERR_TOO_MANY_REDIRECTSThe client stopped after too many redirects—usually a loop between HTTP/HTTPS or www/non-www rules.
• Mixed content (HTTPS page, HTTP resource)A secure page tried to load scripts, images, or XHR over insecure HTTP—browsers block or downgrade.
• NET::ERR_CERT_AUTHORITY_INVALIDThe browser does not trust the certificate chain—self-signed, wrong hostname, or missing intermediate.
• Next.js middleware redirect loopMiddleware keeps issuing redirects—often auth checks on public paths that bounce forever.
• React hydration mismatchServer HTML and client render differ—often dates, random IDs, or browser-only APIs during SSR.
• Service worker fetch failedA service worker intercepted a request and the network failed—offline, CORS, or bad SW scope.