Chrome network error · -200 · Certificate

ERR_CERT_COMMON_NAME_INVALID

The certificate the server presented was issued for a different host name than the one in the address bar, so Chrome cannot verify it belongs to this site.

Chromium's description

The server responded with a certificate whose common name did not match the host name. This could mean:

1. An attacker has redirected our traffic to their server and is presenting a certificate for which they know the private key.

2. The server is misconfigured and responding with the wrong cert.

3. The user is on a wireless network and is being redirected to the network's login page.

4. The OS has used a DNS search suffix and the server doesn't have a certificate for the abbreviated name in the address bar.

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

Common causes

  • The certificate covers example.com but not www.example.com, or the other way round.
  • A server or CDN that serves the default certificate of another site on the same IP.
  • An HTTPS-intercepting proxy or antivirus.
  • Opening a site by IP address instead of by its name.

How to fix ERR_CERT_COMMON_NAME_INVALID

  1. Use the exact host name the site normally uses (with or without www).
  2. Site owners: issue a certificate that lists every host name in its Subject Alternative Names, and check SNI on the server.
  3. Turn off HTTPS scanning of the antivirus.

ERR_CERT_COMMON_NAME_INVALID in the screenshot API

Certificate errors do not stop a render: the API's browser accepts the certificate and captures the page the server sends, so a screenshot of a site with this error works. It does not tell you whether the certificate is valid; use an SSL checker for that.

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_CERT_COMMON_NAME_INVALID mean?

The certificate the server presented was issued for a different host name than the one in the address bar, so Chrome cannot verify it belongs to this site.

How do I fix ERR_CERT_COMMON_NAME_INVALID?

Use the exact host name the site normally uses (with or without www).

Is a screenshot that fails with ERR_CERT_COMMON_NAME_INVALID billed?

The render is not stopped by this error: the API's browser accepts the certificate, and the screenshot counts like any other. Only requests the 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