- Software and digital services
- Web browsers
ERR_CONNECTION_REFUSED
ERR_CONNECTION_REFUSED in Google Chrome: the server refuses the connection
Risk level
Low
Usually safe to check without specialist tools.
Urgency
Medium
Quick answer
Chrome tried to connect and the attempt was refused: the page did not let Chrome connect or something blocks it. Check the address, try other sites and another network, and make sure your firewall or antivirus is not blocking it.
Safety first
Stop and check this first
- Turning the antivirus off to test leaves the device unprotected; turn it back on as soon as the test is done.
Safe checks you can perform
- Full address, including the port
- The same site from another device or network
- Device firewall and antivirus
- Service and inbound rules on the server
Leave these tasks to a qualified professional
- Do not attempt this professional task: Find out what refuses the connection
- Do not attempt this professional task: Review filtering on a company network
What a technician must be able to justify
Technician visit
These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.
These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.
Find out what refuses the connection
What they doThe operator checks the service status and the server and firewall logs for the visitor's time and IP.
They must show youthe log entry or rule that refused the connection.
In writingthe responsible component and the change applied.
Review filtering on a company network
What they doThe network administrator checks whether the corporate firewall or device filtering blocks that destination.
They must show youthe block rule or entry.
In writingwhether an exception is created and for which destination.
Before accepting a part or repair
Nothing has been shown yet. Do not accept a part swap based on the code alone.
Follow these steps
Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.
Full address, including the port
- Who:
- you.
- How:
- look at the whole address; if it has a colon and a number after the name (a port), compare it with the official one.
- Result that matters:
- whether you are using the exact address the site publishes.
- If the address had a different port or subdomain:
- use the official one; if it opens, that was the cause.
- If it is the official one:
- rule out a typo and continue.
- Evidence to keep:
- the failing address, exactly as typed.
Evidence: Google Chrome Help - Fix connection and loading errors in Chrome
The same site from another device or network
- Who:
- you.
- How:
- open the site on your phone using mobile data and, separately, from another computer on your network.
- Result that matters:
- where the refusal happens.
- If it opens on another device on your network but not on this one:
- it indicates a block on this device; check its firewall and antivirus.
- If it fails on every device and network:
- it points to the site; tell its operator.
- Evidence to keep:
- list of devices and networks tried, with the time of each attempt.
Evidence: Google Chrome Help - Get help with common error messages in Chrome · Google Chrome Help - Fix connection and loading errors in Chrome
Device firewall and antivirus
- Who:
- you, on your own device; on a company device, the administrator.
- How:
- open your firewall or antivirus block log or history and look for the site's name at the time of the failure.
- Result that matters:
- whether a block appears for that site.
- If it shows as blocked:
- that is the cause; add an exception only if you trust the site.
- If there is no trace:
- rule out your security software and go back to the other-network result.
- Evidence to keep:
- a screenshot of the block entry or of the empty list.
Do not switch protection off permanently. On a work computer, stop here and ask your administrator to check.
Evidence: Google Chrome Help - Fix connection and loading errors in Chrome
Service and inbound rules on the server
- Who:
- the site operator or server administrator.
- How:
- check that the web service is running and listening on the public port, and review the server firewall rules at the time of the failure.
- Result that matters:
- whether the service accepts connections from outside.
- If the service is stopped or not listening on that port:
- that causes the refusal.
- If it is listening and no rule blocks it:
- look for the refusal at a load balancer or firewall in between.
- Evidence to keep:
- service status and a firewall log extract with the time.
Only the site operator with server access. If you do not run it, do not tamper with anything: send the operator the time and the address.
Evidence: Chromium source - net/base/net_error_list.h (network error list)
Still not solved
If the error persists, stop here. See what the technician must do and show you.
Where this code applies
A code is meaningful only inside the right product and version context.
Primary scope
- System
- Software and digital services
- Brand
- Google Chrome
- Product type
- Web browsers
Known code variants
- ERR_CONNECTION_REFUSED
- ERR_CONNECTION_REFUSED (-102)
- ERR_CONNECTION_REFUSED Chrome
- net::ERR_CONNECTION_REFUSED
What it means
In Chromium's network error list, ERR_CONNECTION_REFUSED (-102) belongs to the connection errors and means a connection attempt was refused. Chrome Help summarises it as the page not letting Chrome connect, or the page being blocked. The refusal can happen at the site's server or at something in between, such as a firewall or antivirus on your device. The code does not say which: you separate them by trying another network and checking the server logs.
Warnings and stop conditions
- Loweditorial warning
Turning the antivirus off to test leaves the device unprotected; turn it back on as soon as the test is done.
Evidence: Google Chrome Help - Get help with common error messages in Chrome
Symptoms and causes
Probable causes · in order
- Blocked on your devicePossible
A firewall or antivirus can block the connection. Suspect it if the site opens from another device on the same network but not from this one.
Evidence: Google Chrome Help - Fix connection and loading errors in Chrome
- The server does not accept the connectionPossible
If the site fails from several devices and networks, the refusal is on the site's side. Only its operator can see why in the logs.
Evidence: Chromium source - net/base/net_error_list.h (network error list) · Google Chrome Help - Get help with common error messages in Chrome
- Wrong address or portPossible
An address with a port or subdomain other than the official one can point to a service that does not accept connections.
Evidence: Google Chrome Help - Fix connection and loading errors in Chrome
Virtual technician
Does ERR_CONNECTION_REFUSED still appear after these checks?
Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.
Sources and technical references
- 1
Chromium source - net/base/net_error_list.h (network error list)
The Chromium Authors · 2026 · official_doc
- 2
Google Chrome Help - Get help with common error messages in Chrome
Google · 2026 · official_doc
- 3
Google Chrome Help - Fix connection and loading errors in Chrome
Google · 2026 · official_doc
Was this entry useful?