ERROR-A / Search

Start with a symptom, message or error code.

Explore
Menu
Error messageERR_CONNECTION_REFUSED describes a refused connection attempt, not a single cause. The site, an intermediary or local configuration can lead to different branches. Compare the same address and failure scope before modifying Chrome or the network.

ERR_CONNECTION_REFUSED in Chrome

ERR_CONNECTION_REFUSED

The connection was refused. Separate one site that will not accept a connection from a failure across many sites.

Try this first

1 quick checks · ~3 min

  1. Check the exact message and addressSeparate refusal, an incorrect address and the failure’s scope.

Find your situation

See all the clues. Choose the one that matches what you observe.

Only one public website fails

Compare the same address in another browser or device before changing the network.

Several websites fail or only Chrome fails

Separate browser, device and network; each comparison leads to a different check.

The address is localhost or a local service

First check the application expected to serve that address and port. Changing public DNS does not start it.

Diagnostic signals

ObservationAnother browser opens the same URL
The site is reachable from that device in this test. Investigate Chrome or its connection path; this alone does not identify a faulty extension.
ObservationFails on one network but works elsewhere
The network or route to that site becomes more relevant. It does not prove the router is broken or DNS is the cause.

Step-by-step solutions

01

Check the exact message and address

  • Estimated time: 3 min
  • Easy
  • Low risk

Separate refusal, an incorrect address and the failure’s scope.

  1. Confirm that Chrome shows ERR_CONNECTION_REFUSED. It means the attempt to establish a connection was refused; this differs from waiting without a response, losing an established connection or failing to resolve a name. The code alone does not identify who refused it.

  2. Compare the URL with the official link: hostname, https/http and any port number. A port identifies where an application expects connections. Do not switch to HTTP or invent another port to bypass the error.

  3. Open another familiar website. If it works, choose the one-site branch; if several fail, choose browser/network. If the address says localhost or 127.0.0.1, it refers to the device running Chrome: use the local branch.

Sources:
02

Compare the same site without changing its address

  • Estimated time: 8 min
  • Easy
  • Low risk

  1. Open the same URL in another available browser. If it works, move to the Chrome check. If it also fails, compare on another device on the same network when possible; use a public page without copying private links or access tokens.

  2. If the second device works, that website is reachable through this network and the affected device’s configuration becomes more relevant. Check its connection, proxy or protection using the several-sites branch; do not change the router yet.

  3. If both fail, try another trusted, authorized network if available, considering data costs. If it works, give that comparison to the original network’s administrator or provider. If it also fails while other websites work, check the site’s status or support: a restriction or service not accepting connections is more plausible than a general internet failure.

  4. An intranet may require the organization’s VPN; a test outside that network is not equivalent. Use authorized access and contact IT. Do not repeat Chrome reinstallations when the failure also occurs outside the browser.

Sources:
03

Separate Chrome, device and network

  • Estimated time: 8 min
  • Easy
  • Low risk

  1. Compare two familiar sites in Chrome and another browser. If only Chrome fails, follow the profile branch. If both browsers fail but another device works on the same network, check the affected device’s configuration; that is not enough to blame the provider.

  2. A proxy is an intermediary carrying the connection. Check whether your system or organization configures one and whether it belongs to this network. Keep its values; do not erase them or remove a work VPN. An unreachable proxy or protection rule requires checking its state or block log with the administrator.

  3. If several websites fail on several devices on the same network, check an authorized alternative network. If they work there, contact the provider with those results. If other apps also lack internet access, the scope is general connectivity rather than a Chrome-specific repair.

  4. Do not change DNS because of this code alone: DNS translates names into addresses, whereas REFUSED describes the connection attempt. If ERR_NAME_NOT_RESOLVED appears or a diagnosis identifies incorrect DNS, address that new evidence with the relevant guide.

Sources:
04

Check which application should listen on that port

  • Estimated time: 10 min
  • Intermediate
  • Low risk

  1. Use this branch for an installed tool or your own local environment. Localhost and 127.0.0.1 point to the current device: opening the same URL on a phone tests the phone itself, not the PC’s server.

  2. Find the tool’s status and the address it reports at startup. If it is not running, start it through its normal procedure with ordinary permissions. If it reports another port, use the URL documented by that tool; do not explore random ports.

  3. If its process exits or reports a startup error, resolve that message before retrying Chrome. An open application does not guarantee its web service is listening; look for startup and port confirmation in its log or console.

  4. If the service reports ready but refuses the correct URL, give its support the address, port and startup message. For containers or virtual machines, port publishing may matter, but it must be checked in that environment’s documentation. Do not expose the service to the internet or disable the firewall to make it reachable.

Sources:
Advanced

Advanced checks

Continue if the earlier steps did not help. Read each procedure’s precautions first.

05

Test the Chrome profile reversibly

  • Estimated time: 10 min
  • Intermediate
  • Moderate risk
  • Restart required
  • Data loss: Possible

  1. Use this branch if another browser works with the same URL. Open an Incognito window and compare an equivalent public page. If it requires a different session, the result does not isolate the profile: do not confuse account access with connection refusal.

  2. If it works in Incognito, an extension or profile-data difference becomes relevant, but the test does not identify which one. In chrome://extensions, record the state and disable one nonessential extension you installed, test the URL and restore it if nothing changes. Do not modify managed extensions or security controls.

  3. If disabling a particular extension resolves the failure and enabling it reproduces it in a safe test, leave it disabled and check for an update or contact its support. If none is isolated, do not reflexively erase all history, cookies and passwords.

  4. If Incognito also fails, check Help > About Google Chrome and update when available, saving work before restarting. If it persists, give support the browser comparison and proxy/protection configuration. Do not reinstall or reset the profile without a more specific hypothesis.

Sources:
Next step

Still not working?

Report the public URL without tokens, time, exact code, Chrome version and results by browser, device and network. For a local service, add its port and startup message. Mention managed proxies or VPNs without sharing credentials. This comparison helps choose site, local-tool, browser or network support without repeating resets.

Sources

Documentation behind this guide. Editorial recommendations are identified separately.

Source review: . A documentation review, not a physical hardware test.