ERR_CONNECTION_REFUSED
Nothing accepted the connection on that port
Seen in Chrome, Edge, Brave ("This site can't be reached")
The browser reached the host, but it actively refused the connection because nothing is listening on that port or a firewall rejected it.
Common causes
- The web server or local dev server is not running, or is listening on a different port.
- The service listens only on 127.0.0.1, so other devices or containers cannot reach it.
- A firewall is rejecting connections to the port.
- A broken proxy setting sends the browser to a proxy that is not running.
How to fix it
- Start the server and check the port it uses (e.g. "ss -ltnp" on Linux, "netstat -ano" on Windows).
- Bind the service to 0.0.0.0 or the right interface if it must be reached from other machines.
- Open the port in the host firewall or cloud security group.
- Check the browser or system proxy settings.
Got a different message? Paste it into the error explainer.
Related errors
- ERR_CONNECTION_RESET · The connection was cut off mid-way
- 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