Chrome network error · -113 · Connection

ERR_SSL_VERSION_OR_CIPHER_MISMATCH

Chrome and the server have no TLS version or cipher in common, so the secure connection cannot start. The server usually offers only outdated protocols.

Chromium's description

The client and server don't support a common SSL protocol version or cipher suite.

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

Common causes

  • The server supports only TLS 1.0/1.1 or old ciphers (RC4, 3DES), which Chrome no longer accepts.
  • The certificate or TLS setup for this host name is missing, e.g. a CDN that has not issued a certificate for a new domain or subdomain yet.
  • A proxy or antivirus that intercepts HTTPS with an outdated configuration.

How to fix ERR_SSL_VERSION_OR_CIPHER_MISMATCH

  1. Site owners: enable TLS 1.2 and 1.3 with modern ciphers and test with an SSL checker.
  2. On a CDN, check that the certificate covers this exact host name (deep subdomains are often not covered).
  3. Visitors: turn off HTTPS scanning of the antivirus and update the browser.

ERR_SSL_VERSION_OR_CIPHER_MISMATCH in the screenshot API

When the page itself fails to load with ERR_SSL_VERSION_OR_CIPHER_MISMATCH, the API answers 502 with the message The target website could not be loaded (ERR_SSL_VERSION_OR_CIPHER_MISMATCH). (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_VERSION_OR_CIPHER_MISMATCH mean?

Chrome and the server have no TLS version or cipher in common, so the secure connection cannot start. The server usually offers only outdated protocols.

How do I fix ERR_SSL_VERSION_OR_CIPHER_MISMATCH?

Site owners: enable TLS 1.2 and 1.3 with modern ciphers and test with an SSL checker.

Is a screenshot that fails with ERR_SSL_VERSION_OR_CIPHER_MISMATCH 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