Chrome network error · -104 · Connection

ERR_CONNECTION_FAILED

A connection attempt failed for a reason Chrome does not name more precisely: the server could not be reached on the address and port of the URL.

Chromium's description

A connection attempt failed.

Chrome shows it as net::ERR_CONNECTION_FAILED, error -104. puppeteer and Playwright report the same name when a page fails to load in Chromium.

Common causes

The server is down or not listening on the port.
A firewall drops or rejects the connection.
A proxy in between could not connect to the site.
A network problem on the way.

How to fix ERR_CONNECTION_FAILED

Retry later, and check whether the site loads from another network.
Turn off VPN and proxy settings.
Site owners: check that the server listens on ports 80 and 443 of its public address and that the firewall allows them.

ERR_CONNECTION_FAILED in the screenshot API

This is what the API reports for every connection to the website that could not be opened (refused, timed out or unreachable): the renderer connects through its own egress proxy, which reports them alike. Status 502, message The target website could not be loaded (ERR_CONNECTION_FAILED). Not billed; check that the site is up and reachable from the internet.

Only the page's own load can fail a render. An image, script or frame of the page that fails with a network error does not: the page is captured as the browser shows it without that resource.

Check whether a website loads

Device

Format

Full page Block ads

Rendered in a real browser with cookie banners hidden. Takes 5–30 seconds.

Frequently asked questions

What does ERR_CONNECTION_FAILED mean?

A connection attempt failed for a reason Chrome does not name more precisely: the server could not be reached on the address and port of the URL.

How do I fix ERR_CONNECTION_FAILED?

Retry later, and check whether the site loads from another network.

Is a screenshot that fails with ERR_CONNECTION_FAILED billed?

No. Requests the screenshot API answers with an error are not billed.

Other common errors

ERR_CONNECTION_RESET ERR_CONNECTION_REFUSED ERR_CONNECTION_TIMED_OUT ERR_CACHE_MISS ERR_ADDRESS_UNREACHABLE ERR_TIMED_OUT ERR_SSL_PROTOCOL_ERROR ERR_CONNECTION_CLOSED ERR_QUIC_PROTOCOL_ERROR ERR_NAME_NOT_RESOLVED ERR_TOO_MANY_REDIRECTS ERR_NETWORK_CHANGED

All 249 Chrome network errors · Screenshot API errors

Screenshot API

Take screenshots from your code

screenshotbase renders any website in a real browser and returns the image: full page or viewport, any device size, retina, from 100+ countries, with cookie banners and ads hidden.

/v1/take documentation Screenshot API All documentation

300 free screenshots every month. No credit card required.

GET https://api.screenshotbase.com/v1/take?url=https://example.com&full_page=true

# Response: the image (PNG, JPG, WebP or GIF)
curl -G "https://api.screenshotbase.com/v1/take" \
  --data-urlencode "url=https://example.com" \
  -d viewport_width=1280 -d viewport_height=800 \
  -d format=png \
  -H "apikey: YOUR-API-KEY" \
  -o screenshot.png

More free tools

Website screenshot Capture any page as an image. Full page screenshot Capture a whole page, top to bottom. Mobile website screenshot See a site on iPhone, Android and iPad. URL to PDF Save any web page as a PDF. URL to markdown Turn a web page into markdown. HTML to PDF Print your own HTML as a PDF. HTML to image Render HTML and CSS as a PNG, JPG or WebP. HTML to markdown Turn HTML into clean markdown. URL to PNG Save a web page as a PNG image. URL to JPG Save a web page as a JPG image. Scrolling screenshot One long image of a page, no stitching. HTML to PNG Render HTML as a lossless PNG. HTML to JPG Render HTML as a compact JPG. Viewport sizesScreen sizes and pixel ratios of 46 devices. ErrorsChrome network errors and screenshot API errors, with fixes.