ERR_CONNECTION_REFUSED in Chrome
ERR_CONNECTION_REFUSEDThe 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
Find your situation
See all the clues. Choose the one that matches what you observe.
Step-by-step solutions
Check the address and another site
Leave network settings alone for now.
Check that the address is the one you intended, particularly when using an old bookmark. Try another unrelated site.
Note whether the refusal affects that address alone or several pages. That distinction determines the next step.
Follow up on the affected site
An isolated failure does not justify resetting your network.
If available, compare the same address on another device or trusted connection. Record which result changes.
If refusal persists for that site, give its operator the address and error without sharing links containing private tokens.
Keep evidence of the wider scope
Do not disable protection as a test.
If several sites fail, compare another app and another device on that network. Give support or IT the result if the connection is managed.
Do not disable firewall or antivirus protection or change DNS based on this message alone. First identify which part of the comparison fails.
Still not working?
Report the URL, time and whether one or several sites fail. Repeated refusal needs investigation of that context, not an assumed server outage or repeated resets.
Sources
Documentation behind this guide. Editorial recommendations are identified separately.
Source review: . A documentation review, not a physical hardware test.