ERR_CONNECTION_REFUSED: what it means and how to fix it

What does the error actually mean?

Google Chrome describes ERR_CONNECTION_REFUSED as a case where the page does not allow Chrome to connect or the connection is blocked. In practice, the browser did not receive the website's normal HTTP response. Causes include an offline service, wrong address or port, firewall, proxy, VPN, local settings or a network-path problem.

First determine the scope

1. Open a few other known websites. If those fail too, investigate your device or connection.
2. If only one domain fails, try it on another device or network, such as mobile data.
3. Verify the exact URL. Especially for local services and development environments, the port matters as well.

This comparison is more useful than randomly clearing all browser data: it quickly distinguishes a local issue from a wider one.

If you are a visitor

• Check whether your internet connection otherwise works.
• Temporarily disable your VPN or proxy as a test if you use one.
• Try another browser or private window, particularly if an extension may be interfering.
• Reconnect your network or restart the router if several websites are affected.
• Do not permanently disable security software or your firewall; a temporary test is appropriate only if you know how to restore protection immediately.

If the same website fails on another device and network, the owner is much more likely to need to act.

If you manage the website

Check each layer in sequence: DNS must point to the correct destination, the web service must listen on the expected port, firewall rules must permit the traffic, and the reverse proxy or CDN must reach the origin.

• Check A and AAAA records with DNS lookup. A wrong or outdated IPv6 address can behave differently from IPv4.
• Verify the process listens on port 80 or 443 and the correct network interface.
• Inspect firewall, security group, WAF and hosting-provider rules.
• For a reverse proxy or CDN, also test connectivity from the proxy to the origin.
• Review logs and the latest deployment or network-configuration change.

REFUSED vs. NXDOMAIN vs. timeout

DNS_PROBE_FINISHED_NXDOMAIN means the domain name did not resolve successfully. ERR_CONNECTION_REFUSED means the connection to the destination was not established or accepted. With a timeout, a connection or response simply takes too long. Distinguishing these symptoms points to the correct area of investigation.

How can splet.me help?

When a public URL is reachable, the website checker can show the final URL, HTTP status and redirect chain. If no connection can be established, it cannot prove the precise reason; use the steps above to separate domain, network and server causes.

Back to top ↑