Chrome network error · -159 · Connection

ERR_SSL_UNRECOGNIZED_NAME_ALERT

The server rejected the TLS handshake because it has no configuration for the host name Chrome asked for (the SNI name).

Chromium's description

The SSL server sent us a fatal unrecognized_name alert.

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

Common causes

  • The domain points to a server or CDN that is not set up to serve it, for example a new domain before its certificate exists.
  • A virtual host missing for this name in nginx or Apache.
  • A misconfigured load balancer listener.

How to fix ERR_SSL_UNRECOGNIZED_NAME_ALERT

  1. Site owners: add the host name to the server’s TLS configuration (server_name, virtual host, CDN custom domain) and issue a certificate for it.
  2. Check that the DNS record points to the right server.
  3. Visitors: try the other variant of the name (with or without www).

ERR_SSL_UNRECOGNIZED_NAME_ALERT in the screenshot API

When the page itself fails to load with ERR_SSL_UNRECOGNIZED_NAME_ALERT, the API answers 502 with the message The target website could not be loaded (ERR_SSL_UNRECOGNIZED_NAME_ALERT). (target_unreachable). Not billed.

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

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

Frequently asked questions

What does ERR_SSL_UNRECOGNIZED_NAME_ALERT mean?

The server rejected the TLS handshake because it has no configuration for the host name Chrome asked for (the SNI name).

How do I fix ERR_SSL_UNRECOGNIZED_NAME_ALERT?

Site owners: add the host name to the server’s TLS configuration (server_name, virtual host, CDN custom domain) and issue a certificate for it.

Is a screenshot that fails with ERR_SSL_UNRECOGNIZED_NAME_ALERT billed?

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

Other common errors

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

Start using our Screenshot API for free today!

Get 300 requests / month for free