ERR_CONNECTION_REFUSED in Chrome on Mac
ERR_CONNECTION_REFUSED is a Chrome network error. The Chromium source describes it as: “A connection attempt was refused.”
My Mac has this problem: ERR_CONNECTION_REFUSED in Chrome on Mac. Read https://kilobat.app/guides/err-connection-refused.md and work through it with me. Install the Kilobat CLI if it’s missing: brew install seifip/kilobat/kilobat. Run the guide’s Terminal and kilobat checks yourself and tell me what you find. List the steps only I can do. Ask before you change any setting.
Symptoms
- Chrome shows “This site can’t be reached” and ERR_CONNECTION_REFUSED.
- The address resolves, but nothing accepts the connection on that port.
- It often happens with
localhostand development servers.
Likely causes
- No service is listening. The server or app is not running, or it listens on another port.
- A firewall rejects the port. A firewall on the server or the network can refuse the connection.
- A wrong address or port. A typing error or an old bookmark points to a port that is closed.
- A VPN or proxy. Traffic goes through a VPN or proxy that refuses it.
How to check
Check the address and the port in the address bar.
Test the port from Terminal. “refused” confirms the cause.
nc -vz localhost 3000List what listens on the port.
lsof -nP -iTCP:3000 -sTCP:LISTENRun curl with details to see the refusal.
curl -v https://example.com
How to fix it
Start the server or app that should listen. Use the port it prints.
For a remote site, wait and retry. The service may be down.
Turn off the VPN for a short test. Turn it on again after.
If the port is busy with another app, see Port already in use on a Mac.
With Kilobat
Kilobat's connection doctor tests the address layer by layer: network, proxy, DNS, rules, IPv4, IPv6, TLS and the server. It names the layer that failed.
kilobat why https://example.comThese Kilobat checks are free. AI agents run them through MCP with
diagnose_connectionanddiagnose_network. See Find why one site or API won't connect.
Questions
Is ERR_CONNECTION_REFUSED a DNS problem?
No. The name resolved and the host answered with a refusal. For DNS errors see ERR_NAME_NOT_RESOLVED in Chrome on Mac.
Why does only Chrome fail?
Chrome may use a proxy or an IPv6 address that other tools skip. Compare with curl.
Sources
Checked on 29 October 2026.