net::ERR_FAILED Browser Origin: On your device Last updated 15 Oct 2026

Chrome DevTools: net::ERR_FAILED — a request failed with no specific reason (CORS, extension, mixed content or network)

ERR_FAILED is Chrome’s catch-all for a failed request. In DevTools it very often hides a CORS rejection, an extension, or a blocked mixed-content request.

Exact message you may see Failed to load resource: net::ERR_FAILEDnet::ERR_FAILED 200
Explore the map of this error Full error map →
Seen on: Chrome Edge JavaScript

Meaning

The console line gives no cause. Look at the Network tab (the Status column and the red request), open the request's headers, and read the console message just above it — a CORS or mixed-content explanation is usually printed separately. Also test with extensions disabled and from curl.

Common causes

  • CORS failure (missing Access-Control-Allow-Origin, redirect or error response without CORS headers)
  • Mixed content: HTTP resource requested from an HTTPS page
  • Browser extension (ad blocker, security tool) cancelling the request
  • Server closing the connection or returning an invalid response
  • File opened from file:// or a blocked scheme

⚡ Quick fix

  1. Read the full console error and the Network tab entry
  2. Try an incognito window with extensions disabled
  3. Reproduce the request with curl -v to see the real server behaviour

Detailed fix by platform

JavaScript

  1. fetch(url).catch(e => console.error(e)) — a bare TypeError: Failed to fetch is the JS view of ERR_FAILED
  2. Add CORS headers on the server for cross-origin calls

Chrome

  1. DevTools → Network → right-click the failed request → Copy → Copy as cURL, and run it in a terminal

How to diagnose

  1. Console — Is there a CORS or mixed-content message above?
  2. Extensions — Fails in incognito?
  3. Server — Does curl work?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: On your device. Errors that are often confused with or caused by this one (click to open):

captive portal — Browser: This network requires you to sign in — captive portal (hotel, airport, café Wi-Fi) blocking HTTPS sites (Browser)captive portalCORS — CORS Error: No 'Access-Control-Allow-Origin' header is present (API)CORSDevTools failed to load source map — DevTools: Failed to load source map — Could not load content for https://…/app.js.map: HTTP error: status code 404 (Browser)DevTools failed to lo…DNS_PROBE_FINISHED_NO_INTERNET — Chrome: No internet — DNS_PROBE_FINISHED_NO_INTERNET (DNS probe finished, no internet) (Browser)DNS_PROBE_FINISHED_NO…ERR_BLOCKED_BY_CLIENT — net::ERR_BLOCKED_BY_CLIENT (JavaScript)ERR_BLOCKED_BY_CLIENTFailed to fetch — TypeError: Failed to fetch / NetworkError when attempting to fetch resource (JavaScript)Failed to fetchMixed Content — Mixed Content: The page was loaded over HTTPS, but requested an insecure resource (API)Mixed ContentThe canvas has been tainted by cross-origin data — Console: SecurityError: Failed to execute 'toDataURL' / 'getImageData' on 'HTMLCanvasElement': Tainted canvases may not be exported (Browser)The canvas has been t…net::ERR_…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.