Error map
bad decrypt openssl: bad decrypt / Could not read private key — wrong passphrase or cipher
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)
OpenSSL/Nginx/Apache: error:0909006C:PEM routines:get_name:no start line / unable to load Private Key
The server or tool cannot read the private key file — wrong format, encrypted with a passphrase, wrong path, or a certificate pas…
OpenSSL: Error outputting keys and certificates — Mac verify error: invalid password?
A `.p12`/`.pfx` file could not be opened because the password is wrong, or its encryption is unsupported by your OpenSSL version.
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…
nginx: [emerg] cannot load certificate key: BIO_new_file() failed (Permission denied) / open() failed (13: Permission denied)
nginx can't read the private key or certificate file, so it refuses to start or reload.
curl: (58) unable to set private key file / could not load PEM client certificate
curl couldn't load the client certificate or its private key for mutual TLS.
HAProxy: unable to load SSL private key from PEM file / no certificate found (crt bundle format)
HAProxy needs the certificate chain and private key concatenated in one PEM, and it can't read yours.
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.
OpenSSL 3: Error outputting keys and certificates ... unsupported (PKCS#12 uses legacy RC2/3DES)
OpenSSL 3 can't open a .p12/.pfx made with old algorithms (RC2-40, 3DES) unless you load the legacy provider.
Heartbleed (CVE-2014-0160): OpenSSL heartbeat extension vulnerable
A scanner reports the server leaks memory through the TLS heartbeat bug.
Two steps away (27)
OpenSSL: unable to load certificate / PEM routines:get_name:no start line (key values mismatch)
OpenSSL (or Nginx/Apache) couldn’t read the certificate or key — wrong file format, wrong file, or the key doesn’t match the cert…
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.
OpenSSL: error:1408F10B:SSL routines:ssl3_get_record:wrong version number
The peer did not answer with a TLS record — you spoke TLS to a plain HTTP/SMTP port (or the reverse), or a proxy intervened.
Error: error:0308010C:digital envelope routines::unsupported
An old build tool (webpack 4, old react-scripts) uses a hash algorithm that OpenSSL 3 in Node 17+ disables.
Java keytool: java.io.IOException: Keystore was tampered with, or password was incorrect
keytool or the JVM could not open the keystore — wrong password, wrong file type, or damaged file.
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).
Dart: HandshakeException: Handshake error in client (OS Error: CERTIFICATE_VERIFY_FAILED: unable to get local issuer certificate)
The app refused the server's TLS certificate because it is self-signed, expired, missing intermediates, or the device clock/CA st…
Go: x509: certificate signed by unknown authority
The Go TLS client does not trust the CA that signed the server's certificate.
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.
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
The docker CLI can’t talk to the Docker engine — it isn’t running, or your user can’t access the socket.
HTTP 403 Forbidden
The server understood the request but refuses to authorize it — you (or the server process) are not allowed to access this resour…
Windows Error 0x80070005 (E_ACCESSDENIED): Access is denied
Windows refused an operation because the account or process lacks permission — seen in Windows Update, installers, Task Scheduler…
curl: (60) SSL certificate problem: unable to get local issuer certificate
curl could not verify the server's certificate — missing CA, incomplete chain, self-signed or expired certificate.
curl: (51) SSL: no alternative certificate subject name matches target host name 'example.com'
The certificate's names (SANs) don't include the host curl connected to.
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.
PROXY protocol error: broken header / unexpected data from the load balancer
A server expecting the PROXY protocol header received plain HTTP (or vice versa), so the connection is rejected.
Certificate chain in the wrong order: PEM bundle must start with the leaf, then intermediates
Servers or clients choke because the certificates in the file are in the wrong order or the root was included first.
PEM routines: bad end line / no start line — Windows CRLF line endings or truncated PEM file
OpenSSL can't parse a PEM file because it has Windows line endings, missing newlines or a damaged BEGIN/END line.
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.
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.
Old clients fail with certificate mismatch: no SNI support (Java 6, Android 2.x, Windows XP IE)
Very old clients can't send SNI, so they only see the default certificate of a shared IP.
unsafe legacy renegotiation disabled (OpenSSL 3) when connecting to an old server
OpenSSL 3 refuses to connect to servers that lack RFC 5746 secure renegotiation support.
OpenSSL: error:14094410 / SSL alert number 70 — tlsv1 alert protocol version
The server rejected the TLS version your client offered, because it requires a newer (or older) protocol.
OpenSSL: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure (SSL alert number 40)
The server aborted the handshake with alert 40 — no acceptable parameters (cipher, signature algorithm, client certificate or SNI…
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).
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError