What the parentheses mean#
Chrome's Status column shows an HTTP code when a response arrived. Otherwise it shows CORS error, (blocked:…) with a reason, or (failed) followed by an error message. Network panel Status values A request that the page or the browser abandoned shows as (canceled).
The error codes come from Chromium's network stack, which defines each code with a one-line description. Chromium net error list
| Value | Chromium's definition | Usual explanation |
|---|---|---|
net::ERR_CONNECTION_REFUSED | A connection attempt was refused. | Nothing listens on that host and port, such as a stopped local server or a wrong port |
net::ERR_NAME_NOT_RESOLVED | The host name could not be resolved. | A typo in the host, a missing DNS record, or a private name used outside its network |
net::ERR_CONNECTION_RESET | A connection was reset (corresponding to a TCP RST). | A proxy, firewall or server closed the connection mid-request |
(blocked:other), with net::ERR_BLOCKED_BY_CLIENT in the Console | The client chose to block the request. | Usually a browser extension such as a content blocker |
net::ERR_ABORTED, shown as (canceled) | An operation was aborted (due to user action). | Navigation away, an AbortController, or the page replacing one request with another |
net::ERR_FAILED with CORS error | A generic failure occurred. | A response failed the CORS check; see the CORS guide |
Two causes to separate#
| Cause A: the browser or page stopped the request | Cause B: the connection to the server failed | |
|---|---|---|
| Typical values | (canceled), (blocked:…) | net::ERR_CONNECTION_REFUSED, net::ERR_NAME_NOT_RESOLVED, net::ERR_CONNECTION_RESET, certificate errors |
| Server logs | None for a blocked request; a canceled request may already have been received and processed | None for a refused, unresolved or certificate failure, which never reached the server; a reset can come after the server received and processed the request, so check its records before retrying a write |
| Who fixes it | Page code, an extension, or a browser policy | Network, DNS, TLS or the server's availability |
The deciding observation is the exact error text, plus the request's Initiator. For a canceled request, the initiator shows the script that started it, and the request's timing shows whether a newer request or a navigation began at the same moment. Initiator column
Reproduced: refused and aborted requests#
In a local reproduction with Chromium, a page called a port with no server, then started a slow request and aborted it after 100 milliseconds with an AbortController.
GET http://localhost:8199/api net::ERR_CONNECTION_REFUSED
fetch rejected: TypeError: Failed to fetch
GET http://localhost:8101/slow net::ERR_ABORTED (canceled)
fetch rejected: AbortError: signal is aborted without reason
Both rejections reach the page's catch block, but with different error names. A page that treats every rejection as "network error" hides which one happened. Log error.name in the client when you can, because AbortError marks a cancellation the page asked for. AbortController
Worked example: a report that names the extension#
This example is fictional. A support engineer reports that the analytics chart on a dashboard is empty for one customer. The customer's screen recording shows the chart frame with no data and no error message.
On a call, the customer opened the Network panel and filtered for metrics. The request to /api/metrics/pageviews showed (blocked:other) in the Status column, and the Console printed Failed to load resource: net::ERR_BLOCKED_BY_CLIENT. Every other API request showed 200. In a window with extensions turned off, the chart loaded.
The report said: a content-blocking extension blocks /api/metrics/pageviews, probably because of the word pageviews in the path. The server never receives the request. That turned a vague "empty chart" ticket into a choice between renaming the route and telling the customer which rule to allow. The incognito guide shows how to confirm an extension is involved.
What to put in the report#
- The Status value and the full error text, copied from the request's row.
- The request's URL, method and initiator.
- What happened in the same second: a navigation, another request to the same endpoint, a tab close.
- Whether it happens with extensions turned off or in another network, if you tried.
Questions#
Why does a canceled request appear when nothing is broken?
Pages often cancel requests on purpose: a search box drops the previous query's request, and a navigation abandons the old page's requests. A canceled request is a bug only when the page needed its result.
What does (blocked:mixed-content) mean?
The page was loaded over HTTPS and tried to load a resource over HTTP. Browsers block or upgrade such requests. Change the resource URL to HTTPS. MDN: mixed content
Is net::ERR_FAILED always CORS?
No. It is a generic failure code. Look at the Status column and the Console message next to it: CORS failures say so explicitly, while other failures carry their own message.
Return to the method for browser bug reports for the other symptoms in this collection.