Error map
HTTPS scanning Antivirus HTTPS/SSL scanning breaks certificates (Avast, Kaspersky, ESET, Bitdefender)
SSL / TLS · layer 2, Network
Centre: this error. First ring: errors it is linked with (9). 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 (9)
Certificate expired unexpectedly — manual renewal missed or automation failing silently
Production HTTPS broke because a certificate expired and nobody noticed.
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.
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.
SMTP TLS certificate verification failed: hostname mismatch / unable to get local issuer (mail client or library)
The client verified the mail server's certificate and it didn't match the host name or wasn't trusted.
NET::ERR_SSL_PINNED_KEY_NOT_IN_CERT_CHAIN — HPKP or built-in public key pinning mismatch
The certificate's public key doesn't match a pinned key, so the browser refuses it (often a MITM proxy or a new key).
ERR_SSL_VERSION_INTERFERENCE — something on the network is interfering with TLS version negotiation
Chrome detected that a proxy, antivirus or firewall tampered with the TLS handshake versions.
Certificate error caused by a wrong device clock (NET::ERR_CERT_DATE_INVALID, "your clock is ahead/behind")
The site's certificate is valid, but the computer's date or time is wrong, so the browser thinks it is expired or not yet valid.
NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM — certificate signed with SHA-1 or MD5
The browser rejects a certificate (or a chain certificate) signed with a weak hash like SHA-1.
Firefox: MOZILLA_PKIX_ERROR_MITM_DETECTED — something on your computer or network is intercepting HTTPS
Firefox noticed that a proxy or antivirus is replacing certificates in a way that breaks Firefox's own checks.
Two steps away (27)
Firefox: Peer's Certificate has expired. Error code: SEC_ERROR_EXPIRED_CERTIFICATE
Firefox found an expired certificate in the chain presented by the server.
OpenSSL: verify error:num=10:certificate has expired — notAfter=Jan 1 00:00:00 2025 GMT
OpenSSL's verification found a certificate in the chain whose validity period has ended.
HEAD request returns a different status or headers than GET
Monitors and link checkers using HEAD see errors (405, 404, different length), while GET works in the browser.
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.
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.
SMTP: 530 5.7.0 Must issue a STARTTLS command first / 530 5.7.1 Authentication required
The server will not accept mail until you encrypt the connection (STARTTLS) and/or authenticate, and your client did neither.
SMTP: [SSL: WRONG_VERSION_NUMBER] wrong version number — SMTP over SSL on a STARTTLS port
Your client tried to start TLS immediately on a port where the server speaks plain SMTP first (or the reverse), so the handshake…
Nodemailer: Error: Greeting never received (code: 'ETIMEDOUT', command: 'CONN')
The TCP connection was made but the server never sent its SMTP `220` banner — usually a TLS mode mismatch or a firewall/proxy swa…
Android/OkHttp: javax.net.ssl.SSLPeerUnverifiedException: Certificate pinning failure! Peer certificate chain: sha256/... Pinned certificates for api.example.com
The app's pinned certificate/public-key hash does not match the one the server presented, so OkHttp blocked the request.
Chrome: ERR_SSL_KEY_USAGE_INCOMPATIBLE — the certificate's key usage doesn't allow the negotiated cipher
The server's certificate Key Usage extension does not permit the key exchange used (typically an RSA certificate missing `keyEnci…
NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED — certificate not logged in Certificate Transparency
Chrome requires publicly trusted certificates to have valid SCTs from CT logs, and this one doesn't.
Cloudflare Error 525: SSL Handshake Failed
Cloudflare couldn’t complete a TLS handshake with your origin (SSL mode Full / Full strict).
Cloudflare Error 526: Invalid SSL Certificate
With SSL mode Full (strict), the origin’s certificate is expired, self-signed, or doesn’t match the hostname.
Chrome: This site can’t be reached — example.com unexpectedly closed the connection. ERR_CONNECTION_CLOSED
The server closed the connection before finishing the TLS handshake or sending a response — typical for HTTP/HTTPS port mix-ups,…
NET::ERR_CERT_DATE_INVALID (certificate expired)
The site’s certificate has expired (or isn’t valid yet) — or the device clock is wrong.
Cookie expires immediately or never because of clock skew or a wrong Expires date
A cookie vanishes right after login, or stays when it shouldn't, because the browser and server clocks disagree.
openssl verify error:num=9:certificate is not yet valid
The certificate's notBefore date is in the future from the verifier's point of view.
NET::ERR_CERT_COMMON_NAME_INVALID: Your connection is not private (certificate is for a different domain)
The certificate presented doesn’t include the hostname you visited — e.g. visiting www.example.com with a certificate only for ex…
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.
OpenSSL: error:0A00018E:SSL routines::ca md too weak / error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small
OpenSSL's security level rejected a certificate signed with a weak hash (MD5/SHA-1) or with a small key (RSA < 2048).
Firefox: Warning: Potential Security Risk Ahead — SEC_ERROR_UNKNOWN_ISSUER (certificate not trusted)
Firefox does not trust the authority that issued the site's certificate — a self-signed certificate, a missing intermediate, or a…
Firefox: Secure Connection Failed — SSL_ERROR_NO_CYPHER_OVERLAP (no common cipher)
Firefox and the server share no TLS cipher suite, so the secure handshake cannot even start.
Firefox: The page isn’t redirecting properly — Firefox has detected that the server is redirecting the request in a way that will never complete
Firefox's wording for a redirect loop (Chrome calls it ERR_TOO_MANY_REDIRECTS).
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError