Error map
disabledAlgorithms Java: SSLHandshakeException — TLSv1/TLSv1.1 or algorithm disabled by jdk.tls.disabledAlgorithms
SSL / TLS · layer 2, Network
Centre: this error. First ring: errors it is linked with (12). 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 (12)
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.
javax.net.ssl.SSLHandshakeException: PKIX path building failed: unable to find valid certification path to requested target
Java doesn’t trust the server’s certificate chain (self-signed, corporate proxy CA, or missing intermediate).
Java: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
The server rejected the Java client's TLS offer — no shared protocol/cipher, SNI issue or a required client certificate.
Java: javax.net.ssl.SSLHandshakeException: No subject alternative names matching IP address 10.0.0.5 found
Java checks the hostname against the certificate's SANs and found no matching entry (for DNS names or IPs).
Go: tls: first record does not look like a TLS handshake (HTTP server spoken to with HTTPS)
A Go TLS client or server received plain HTTP bytes instead of a TLS handshake.
javax.mail.MessagingException: Could not connect to SMTP host: smtp.example.com, port: 587 (JavaMail)
JavaMail couldn't open a connection to the SMTP server.
Java: SSLHandshakeException — no cipher suites in common (server side)
The Java server has no cipher suite in common with the client, often because of its keystore key type or enabled suites.
Security scan finding: TLS 1.0 and TLS 1.1 are enabled (deprecated protocols, PCI DSS)
A vulnerability or PCI scan flags the server for still accepting TLS 1.0/1.1.
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.
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.
SSL routines: unsupported protocol (TLS 1.0/1.1 disabled by the server or OpenSSL security level)
Client and server have no common TLS version, usually because a legacy version is disabled on one side.
SSL error: bad record mac (decryption failed or corrupted TLS record)
A TLS record failed its integrity check, so the connection is dropped.
Two steps away (32)
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.
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.
java.lang.OutOfMemoryError: Java heap space
The JVM ran out of heap memory and garbage collection couldn’t free enough.
SSL: CERTIFICATE_VERIFY_FAILED / unable to get local issuer certificate
The client couldn’t verify the server’s TLS certificate chain, so it refused the HTTPS connection.
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.
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: SSL alert number 112 — tlsv1 unrecognized name
The server did not recognise the hostname sent in SNI and rejected the handshake (or an alert/warning is logged).
Firefox: Websites prove their identity via certificates — the certificate is only valid for other names. Error code: SSL_ERROR_BAD_CERT_DOMAIN
The certificate does not include the hostname you typed.
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.
Apache: [ssl:warn] AH01909: example.com:443:0 server certificate does NOT include an ID which matches the server name
Apache's SSL virtual host name does not match any name inside the certificate it loads.
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,…
SMTP: 421 4.7.0 Our system has detected an unusual rate of unsolicited mail originating from your IP address. Mail sent from your IP address has been temporarily rate limited
The receiving server (often Gmail or Outlook) is temporarily throttling your mail because the volume or reputation of your sendin…
Python: ConnectionRefusedError: [Errno 111] Connection refused — smtplib connect to localhost:25
Nothing is listening on the SMTP host and port your script connected to — often `localhost:25` because no host was given and no l…
Nodemailer: Error: connect ETIMEDOUT 142.250.27.108:465 (code: 'ETIMEDOUT', command: 'CONN')
Nodemailer could not open a connection to the SMTP server before the timeout — a blocked port, wrong host, or network issue.
Java: SSLException — Unrecognized SSL message, plaintext connection? (HTTPS client talking to an HTTP port)
The client expects TLS, but the server answered with plain text, so the handshake can't start.
Schannel Event 36874: An TLS connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server
A Windows server (IIS, RDP, SQL) rejected a client because there's no cipher suite or protocol in common.
Security scan: HTTP TRACE / TRACK method enabled
The server answers TRACE requests, which a scanner flags as a cross-site tracing risk.
Security scan: weak ciphers enabled (3DES / RC4 / EXPORT / NULL — SWEET32, CVE-2016-2183)
The server still offers legacy cipher suites with known attacks.
MTA-STS policy fetch failed / no valid TLS (mta-sts.txt not reachable or certificate invalid)
Senders can't retrieve or trust your MTA-STS policy, so TLS enforcement isn't applied (or mail is deferred in enforce mode).
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.
IIS serves the wrong certificate: SNI not enabled on the HTTPS binding (multiple sites on one IP)
Several IIS sites share port 443 on the same IP, and visitors get the first site's certificate.
HTTP 505 HTTP Version Not Supported
The server doesn’t support the HTTP protocol version used in the request.
HTTP 100 Continue
An interim response telling the client to go ahead and send the request body — normal when the client sent Expect: 100-continue.
HTTP 103 Early Hints
An interim response that sends Link headers early so the browser can preload CSS, fonts or scripts while the server is still buil…
Console: Failed to find a valid digest in the 'integrity' attribute for resource … with computed SHA-256 integrity
A `` or `` with an `integrity` hash was blocked because the downloaded file does not match that hash.
Python: ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:2396)
The server closed the TLS connection abruptly without a proper shutdown, usually because it rejected the handshake or dropped the…
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError