Error map
weak DH ERR_SSL_WEAK_SERVER_EPHEMERAL_DH_KEY — server's Diffie-Hellman key is too small
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)
Nginx: [emerg] SSL_CTX_set_tmp_dh("/etc/ssl/dhparam.pem") failed (SSL: error:1401E0A8:SSL routines:... dh key too small)
The Diffie-Hellman parameters file is too weak (e.g. 512 or 768 bit) for the current OpenSSL security level.
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…
Security scan: weak ciphers enabled (3DES / RC4 / EXPORT / NULL — SWEET32, CVE-2016-2183)
The server still offers legacy cipher suites with known attacks.
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.
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.
NET::ERR_CERT_NAME_CONSTRAINT_VIOLATION — CA name constraints exclude this hostname
The issuing CA is restricted by name constraints, and the certificate's name falls outside them.
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.
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)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Nginx (or another server) can’t listen on the port because another process already holds it — often Apache, another Nginx, or a s…
Nginx: upstream timed out (110: Connection timed out) while reading response header from upstream
Nginx waited longer than proxy_read_timeout (60 s default) for the backend (app server, PHP-FPM) to respond, then returned 504.
Nginx: [emerg] SSL_CTX_use_PrivateKey_file("/etc/ssl/server.key") failed (SSL: error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch)
The private key does not belong to the certificate configured in the server.
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.
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.
Let's Encrypt/CA: CAA record for example.com prevents issuance
The domain's DNS CAA records do not list the certificate authority you asked, so the CA must refuse.
Chrome: ERR_HTTP2_INADEQUATE_TRANSPORT_SECURITY — HTTP/2 requires a modern TLS cipher
The server speaks HTTP/2 but negotiated a TLS version or cipher that HTTP/2 forbids (blocklisted ciphers or TLS below 1.2).
Security scan: HTTP TRACE / TRACK method enabled
The server answers TRACE requests, which a scanner flags as a cross-site tracing risk.
nginx: [emerg] SSL_CTX_set_cipher_list("...") failed — invalid ssl_ciphers string
The `ssl_ciphers` value contains a cipher or syntax OpenSSL doesn't accept, so nginx won't load the config.
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.
Chrome: Your connection is not private — NET::ERR_CERT_REVOKED (the certificate was revoked)
The site’s TLS certificate has been revoked by the certificate authority, so browsers refuse to trust it.
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.
CORS: Private Network Access preflight blocked (public site calling localhost/intranet)
Chrome blocks a public website from reaching a private IP, localhost or intranet service without explicit permission.
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…
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.
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).
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.
Antivirus HTTPS/SSL scanning breaks certificates (Avast, Kaspersky, ESET, Bitdefender)
Security software intercepts HTTPS by re-signing certificates with its own root, which some apps and browsers reject.
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