Errors / Network errors
net::ERR_CONNECTION_REFUSED
The server at that address exists but refused to take the connection.
Everything served from that address fails.
Why it happens
- Nothing is listening on that port: the server or the app behind it is down, or crashed.
- A URL with a port that only works on a developer's machine (
localhost:3000) left in production. - A firewall rejecting the connection.
How to fix it
- Check the server or service is running and listening on the port in the URL.
- Search the site's code and settings for
localhostand development ports. curl -von the exact URL, from outside your network, says within a second whether the port is closed (Connection refused) or unreachable (a timeout), which is the difference between a stopped service and a firewall. If only one asset fails, look at its host and port in DevTools' Network panel: a leftover development address is the usual answer.
Whose problem it is
Usually the server that answers the request.
Does your site have it?
Free, no account. We open your page and four more in a clean Chrome and list every error like this one, with the page and the click that caused it. How the free page check works.
Often seen with
- ERR_CONNECTION_TIMED_OUT / ERR_TIMED_OUTThe server took too long to answer, and the browser gave up.
- ERR_CONNECTION_RESETThe connection to the server was cut in the middle.