Skip to content
Glitchary
ERR_CONNECTION_REFUSED6 troubleshooting steps3 sources linked

ERR_CONNECTION_REFUSED: compare the site and server

Chrome reports that the connection was refused or blocked. Separate one failing address from a general browsing problem; for a local development URL, verify that the server is running at the actual port.

By Glitchary · Updated · 2 min read

The short version

  1. 01Check the exact URL, including the protocol and any explicit port.
  2. 02Open another website to establish whether the failure affects one address or general browsing.
  3. 03Compare the failing URL in another browser without changing the address.
  4. 04For localhost, start the intended service and use the URL and port reported by its startup output.
  5. 05Use Google's shared connection procedure when the failure follows Chrome or the network.
  6. 06Send persistent failures to the site owner with the URL and comparison results.

Raw message

ERR_CONNECTION_REFUSED

Likely causes

  • The requested connection is refused or blocked.
  • A local development service may not be running at the address and port being opened.
  • A browser or network control may require investigation through Chrome's shared connection procedure.

Compare one address with general browsing

Google explains ERR_CONNECTION_REFUSED as a connection that was not allowed or was blocked. Our first check is the exact URL, followed by another website and the same URL in another browser. Those comparisons help the owner separate the failing destination from a broader connection or browser problem.

Google Chrome: page-loading error meanings

Local development: verify the listening service and port

For a localhost URL, our recommendation is to check the intended server's startup output and open its actual address and port. Node's system-error reference explains that ECONNREFUSED commonly occurs when a target service is inactive. That is useful server-side context; Node's code is not a definition of every Chrome connection failure.

Node.js: connection-refused system errors

Use Chrome's shared connection procedure for the remaining branch

Google's connection guide covers connectivity, browser restart/update and Incognito or extension comparisons. Use that official procedure if the failure follows Chrome or the network. Our recommendation is to report persistent one-site failures with the exact address and test results instead of changing unrelated Windows servicing settings.

Google Chrome: shared connection troubleshooting

Sources and review notes

Checked on . Google supplies the browser error meaning and shared connection procedure. Node's ECONNREFUSED documentation is used only for the local-server example. The scope comparisons and checking startup output are editorial guidance. Glitchary is independent of Google.

Tags

chromebrowsererr-connection-refusedconnectionlocalhostportserverblocked