Error map
unknown ca tlsv1 alert unknown ca — the other side doesn't trust the certificate's issuer
SSL / TLS · layer 2, Network
Centre: this error. First ring: errors it is linked with (8). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (8)
iOS: Error Domain=NSURLErrorDomain Code=-1202 "The certificate for this server is invalid. You might be connecting to a server that is pretending to be 'example.com'"
iOS rejected the server's certificate (untrusted issuer, name mismatch, expired, or weak).
Node.js: Error: unable to verify the first certificate (code: UNABLE_TO_VERIFY_LEAF_SIGNATURE)
Node could not verify the server's leaf certificate because the intermediate certificates were not provided by the server.
Schannel Event 36887: A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 46/48/40
A Windows TLS client or server logged that the peer sent a fatal alert, with a code that explains why.
Corporate proxy TLS inspection (Zscaler, Netskope, Palo Alto): certificate issued by an untrusted corporate root
Tools running outside the browser (git, pip, npm, curl, Java, Docker) don't trust the company's inspection root CA.
Django send_mail: ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] (EMAIL_USE_SSL vs EMAIL_USE_TLS on the wrong port)
Django's SMTP backend negotiates TLS in the wrong mode for the port.
sslv3 alert bad certificate — server rejected the client certificate (mutual TLS)
The server uses client authentication and didn't accept the certificate the client presented (or got none).
tlsv1 alert internal error — the TLS peer hit an internal problem during the handshake
The server sent alert 80, usually because its TLS configuration is broken or it can't pick a certificate.
tlsv1 alert insufficient security — server rejects the offered protocol/cipher/key strength
The server requires stronger parameters (TLS version, cipher, DH/key size) than the client offered.
Two steps away (24)
Safari: Safari Can’t Open the Page — A TLS error caused the secure connection to fail
Safari could not set up a secure TLS connection — an expired or untrusted certificate, an outdated server configuration or interf…
Apache: AH02240: Server should be SSL-aware but has no certificate configured / SSLCertificateFile: file '/etc/ssl/x.crt' does not exist or is empty
Apache cannot find the certificate or key file named in its configuration, or `SSLEngine on` is set without any certificate.
SSL Labs: Chain issues: Incomplete — Extra download (intermediate certificate missing)
The server sends only its own certificate and not the intermediate CA(s), so some clients cannot build a trusted chain.
npm ERR! code SELF_SIGNED_CERT_IN_CHAIN — request to https://registry.npmjs.org/ failed, reason: self signed certificate in certificate chain
A corporate proxy or antivirus is intercepting HTTPS, and npm doesn’t trust its certificate.
OpenSSL: error:num=20:unable to get local issuer certificate / SSL: CERTIFICATE_VERIFY_FAILED
The client could not build a chain from the server's certificate to a CA it trusts — the issuer is missing locally or the server…
Let's Encrypt: Fetching http://example.com/.well-known/acme-challenge/token: Timeout during connect (likely firewall problem)
The ACME validation server could not reach your server on port 80 within the timeout.
.NET: System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel
A .NET client could not validate the server certificate or negotiate TLS, so the HTTPS call failed.
curl (Windows Schannel): schannel: next InitializeSecurityContext failed: CRYPT_E_NO_REVOCATION_CHECK (0x80092012) - The revocation function was unable to check revocation for the certificate
Windows could not contact the CA's CRL/OCSP servers to check whether the certificate is revoked, so Schannel aborted.
tlsv1 alert inappropriate fallback (TLS_FALLBACK_SCSV downgrade protection)
A client retried with a lower protocol version, and the server detected a downgrade attempt.
HTTP 407 Proxy Authentication Required
A proxy between you and the server requires credentials before it will forward your request.
fatal: unable to access 'https://…': SSL certificate problem: unable to get local issuer certificate
Git doesn’t trust the HTTPS server’s certificate — corporate proxy, self-hosted Git with an internal CA, or outdated CA bundle.
Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded)
Docker couldn’t reach the registry in time — a network, DNS, proxy or firewall problem between your machine and the registry.
django.db.utils.OperationalError: no such table: app_model
Django queried a table that hasn’t been created — migrations missing or not applied.
django.core.exceptions.ImproperlyConfigured: settings are not configured / SECRET_KEY must not be empty
Django can’t load its settings — DJANGO_SETTINGS_MODULE unset, a required setting missing, or an environment variable not provide…
django.core.exceptions.DisallowedHost: Invalid HTTP_HOST header: 'x'. You may need to add 'x' to ALLOWED_HOSTS.
The request’s Host header isn’t listed in Django’s ALLOWED_HOSTS.
Nginx 400: The SSL certificate error (495 / 496 client certificate)
Nginx rejected the request because the client certificate was invalid (495) or missing (496) on a site that requires mutual TLS.
nginx 496 SSL Certificate Required
nginx requires a client certificate (mutual TLS) and the client didn't send one.
openssl verify error:num=26:unsupported certificate purpose
The certificate isn't valid for the use being checked (e.g. a client certificate used as a server cert).
Chrome: This page isn’t working — example.com didn’t send any data. ERR_EMPTY_RESPONSE
The server accepted the connection but closed it without sending any HTTP response — a crash, timeout or misconfigured proxy on t…
Chrome: This page isn’t working — example.com redirected you too many times. ERR_TOO_MANY_REDIRECTS
The page keeps redirecting to itself or in a loop, so the browser gives up after about 20 redirects.
Chrome: This page isn’t working — example.com is unable to handle this request. ERR_HTTP2_PROTOCOL_ERROR
The HTTP/2 connection broke a protocol rule — a server, proxy or CDN sent an invalid or oversized frame/header, or closed the str…
Error creating: pods is forbidden: violates PodSecurity "restricted:latest": allowPrivilegeEscalation != false ...
The namespace enforces a Pod Security Standard (baseline/restricted) and the pod spec breaks one of its rules.
WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! (ssh host key changed)
The server’s SSH host key differs from the one saved in ~/.ssh/known_hosts — usually because the server was rebuilt or the IP was…
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY
apt can’t verify a repository’s signature because the repo’s signing key isn’t installed (or has expired/rotated).
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError