ERR_CONNECTION_TIMED_OUT
The server never answered the connection attempt
Seen in Chrome, Edge (Firefox: "The connection has timed out")
The browser sent connection requests but got no reply at all, so it gave up.
Common causes
- A firewall or cloud security group silently drops traffic to the port.
- The server is down, overloaded, or DNS points at an old or wrong IP address.
- A local proxy, VPN or network filter is blocking the route.
How to fix it
- Check DNS returns the right IP address for the site.
- Allow inbound 443 and 80 in the server firewall and security group.
- Confirm the server is up and listening, and test from another network.
Got a different message? Paste it into the error explainer.
Related errors
- NET::ERR_CERT_DATE_INVALID · The certificate has expired or is not yet valid
- NET::ERR_CERT_AUTHORITY_INVALID · The certificate isn't issued by a trusted authority
- SEC_ERROR_UNKNOWN_ISSUER · Firefox doesn't recognise the certificate's issuer
- NET::ERR_CERT_COMMON_NAME_INVALID · The certificate doesn't cover this name
- ERR_SSL_PROTOCOL_ERROR · The secure connection failed during the handshake
- ERR_SSL_VERSION_OR_CIPHER_MISMATCH · No TLS version or cipher in common
- ERR_TOO_MANY_REDIRECTS · The page redirects in a loop
- You cannot visit this site right now because the website uses HSTS · HSTS blocks the bypass of a certificate error
- NET::ERR_CERT_REVOKED · The certificate has been revoked by its issuer
- NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM · The certificate is signed with an insecure algorithm
- NET::ERR_CERT_INVALID · The certificate is malformed or breaks platform rules
- NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED · The certificate is not logged in Certificate Transparency