TLS_ERROR[01]

TLS_ERROR

The target site's TLS certificate or handshake failed, so Onto couldn't connect securely.

Code · HTTP status · Retryable?

TLS_ERROR[502][No]

What this means

[02]

TLS_ERROR means Onto couldn't set up a secure connection to the site. Usually the certificate is expired, self-signed, or issued for a different hostname. The problem is on the site's side, not in your request. Failed requests are refunded.

When you'll see it

[03]

HTTP 502. Body always includes code: "TLS_ERROR". Branch on code, never on the human-readable message — wording can change without notice; the code is the stable contract.

Example response

[04]

example response[json]

{
  "status": "error",
  "code": "TLS_ERROR",
  "message": "Target site has an invalid TLS certificate (CERT_HAS_EXPIRED)"
}

How to handle

[05]

Don't retry right away; a broken certificate won't fix itself in seconds. If you own the site, fix or renew the certificate. Otherwise skip the URL and tell your user the site's certificate is invalid.

Suggested handling in a Node client:

if (data.code === 'TLS_ERROR') {
  // The site's certificate is broken. Skip it.
  return null;
}

Code · Status · What it means

EXTRACTION_FAILED[HTTP 500]

The fetch or the parse failed: an origin error, an unreachable host, a redirect problem, or a page or PDF Onto couldn't parse.

TIMEOUT[HTTP 504]

The target site didn't respond within 15 seconds.

See the full error index for the complete catalog with the handling switch statement covering every code at once.