Error map
plaintext Java: SSLException — Unrecognized SSL message, plaintext connection? (HTTPS client talking to an HTTP port)
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: 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.
Firefox: Secure Connection Failed — SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG
Firefox sent a TLS handshake but received plain HTTP back — you used `https://` on a port that serves HTTP.
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.
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).
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.
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…
Networking: ICMP Destination unreachable (Port unreachable) — UDP packet sent to a port where nothing is listening
A host answered a UDP packet with an ICMP message saying no program is listening on that port.
STARTTLS vs implicit TLS: wrong port/mode causes handshake errors (SMTP 465/587, IMAP 143/993, POP3 110/995)
A client uses implicit SSL on a STARTTLS port (or the reverse), so the TLS handshake fails or hangs.
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.
Node.js: write EPROTO ... SSL routines:ssl3_get_record:wrong version number (https:// to an HTTP port, or http agent for https)
The client attempted TLS against a server (or port) that doesn't speak TLS, or used the wrong HTTP agent.
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.
Java: SSLPeerUnverifiedException — Certificate for <host> doesn't match any of the subject alternative names
The TLS handshake worked, but Java's hostname verification found the certificate isn't valid for the requested host.
Two steps away (35)
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).
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…
ERR_SSL_PROTOCOL_ERROR (This site can't provide a secure connection)
The browser couldn’t negotiate TLS — the server sent an invalid response, often plain HTTP on the HTTPS port.
Firefox: Peer's Certificate has expired. Error code: SEC_ERROR_EXPIRED_CERTIFICATE
Firefox found an expired certificate in the chain presented by the server.
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 error 35: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to host:443
The TLS handshake failed — protocol/cipher mismatch, a proxy interfering, or the server closed the connection.
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…
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.
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.
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 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.
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.
SMTP: 450 4.7.1 <user@example.com>: Recipient address rejected: Greylisted, see http://postgrey.schweikert.ch/help/example.com.html
The recipient server deliberately rejected the first delivery attempt from an unknown sender (greylisting) and expects a legitima…
SMTP: 451 4.3.0 Error: queue file write error / 451 Requested action aborted: local error in processing
The server hit an internal problem (disk, database, content filter, DNS) while handling your message and asked you to retry later.
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.
Networking: ping — Destination Host Unreachable / Destination net unreachable (ICMP type 3)
A router (or your own PC) tells you it has no way to deliver the packet to that address.
Networking: ping — Request timed out / 100% packet loss (host drops or filters ICMP)
No echo reply arrived in time: the host is down, unreachable, or simply ignores ping.
Networking: TTL expired in transit — routing loop between routers
A packet ran out of hops before arriving, which usually means two routers keep sending it back and forth.
Error: listen EADDRINUSE: address already in use :::3000
Another process is already listening on that port.
Docker: Bind for 0.0.0.0:80 failed: port is already allocated
Another container or host process already publishes that host port.
Web server failed to start. Port 8080 was already in use.
Spring Boot couldn’t bind its embedded server port because another process uses it.
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.
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.
Node.js: UNABLE_TO_VERIFY_LEAF_SIGNATURE / SELF_SIGNED_CERT_IN_CHAIN behind a corporate proxy (NODE_EXTRA_CA_CERTS)
Node uses its own bundled CA list, so a corporate TLS-inspecting proxy's root isn't trusted.
CloudFront can't use my ACM certificate: it must be requested in us-east-1 (N. Virginia)
The certificate you want to attach to CloudFront isn't listed, because it was created in another region.
SSL routines: no shared cipher (client and server have no common cipher suite)
The handshake fails because no cipher suite is supported by both sides.
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.
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.
openssl verify error:num=62:Hostname mismatch / Verify return code: 62
The certificate is valid but not for the hostname you connected to or asked OpenSSL to check.
Go: x509: certificate relies on legacy Common Name field, use SANs instead
Go (1.15+) no longer accepts certificates that only have a CN and no Subject Alternative Name.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError