ERROR CODES / ENGLISH

SSL certificate verification failed: CERTIFICATE_VERIFY_FAILED

Causes of certificate verification failures, from self-signed certificates to proxy interception, and the checks for each.

Reviewed 2026-11-13 · ERROR CODES / 495 · Chinese detail: 完整中文页

What it means

The certificate check did not pass. The site may be using a self-signed certificate, or a proxy on your side may be intercepting the connection.

SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed

The client reached the TLS layer but refused to trust the certificate presented by the server.

Common causes

Share	Cause
40%	Configuration problem (key, base URL, variable name)
30%	Provider status (rate limiting, overload, outage)
20%	Request content (parameters, structure, length)
10%	Network path (DNS, proxy, certificate)

The error text names a certificate, so start with the network-path row. The generic ranking treats it as the least common category, which means configuration and provider problems should still be ruled out if the certificate checks come back clean.

How to confirm

Make a request with verification temporarily disabled. If it succeeds, the certificate chain is the problem; leave verification disabled only long enough to confirm. Check the system time: an incorrect clock can make a valid certificate look expired. Then check whether a proxy is intercepting TLS.

Fix

Temporarily disable verification to locate the problem. Do not leave it off long-term.
Check the system time.
Update the CA certificates.

If it still fails

Symptom	Responsible party
Still fails after changing request content	Configuration or provider
Switching site or network fixes it	That side
Only triggered under specific conditions	Your request

If disabling verification does not help, the failure is not the certificate chain. Re-check the Base URL and the proxy path, then test another network.

General guidance, not a statement about any specific provider. For measured data, see the relay directory and method.