Error map
.NET TLS The request was aborted: Could not create SSL/TLS secure channel (.NET Framework TLS 1.2 not enabled)
SSL / TLS · layer 2, Network
Centre: this error. First ring: errors it is linked with (10). 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 (10)
.NET: System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel
A .NET client could not validate the server certificate or negotiate TLS, so the HTTPS call failed.
curl (Windows Schannel): schannel: next InitializeSecurityContext failed: CRYPT_E_NO_REVOCATION_CHECK (0x80092012) - The revocation function was unable to check revocation for the certificate
Windows could not contact the CA's CRL/OCSP servers to check whether the certificate is revoked, so Schannel aborted.
curl: (35) schannel: next InitializeSecurityContext failed (SEC_E_UNTRUSTED_ROOT / SEC_E_ALGORITHM_MISMATCH)
curl on Windows (Schannel) couldn't complete the TLS handshake and shows the underlying SEC_E_ error code.
Cannot export or import the certificate with its private key (PFX/PKCS#12 has no private key)
The `.pfx` file contains only the certificate, so servers that need the private key fail.
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.
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.
Outlook error 0x800CCC0D: Cannot find the server — the host name of the mail server couldn't be resolved
Outlook can't resolve the incoming or outgoing server name.
System.Net.Mail.SmtpException: The SMTP server requires a secure connection or the client was not authenticated (5.7.0)
A .NET SmtpClient call hit a server that requires TLS and authentication.
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.
OpenSSL: Can't open openssl.cnf for reading / error loading config file
OpenSSL can't find or parse its configuration file, so `req`, `ca` or `x509` commands abort.
Two steps away (30)
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).
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.
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.
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.
curl: (77) error setting certificate verify locations: CAfile: /etc/ssl/certs/ca-certificates.crt CApath: none
curl cannot read the CA bundle file it is configured to use — missing file, wrong path or permissions.
Docker Desktop: WSL 2 installation is incomplete / WSL update required
Docker Desktop on Windows needs WSL 2 and its Linux kernel; they’re missing, outdated or disabled.
Windows/IIS: A specified logon session does not exist / The certificate does not have a private key associated with it
IIS cannot bind an HTTPS site because the imported certificate has no private key attached.
Networking: PING: transmit failed. General failure. / ping: sendmsg: Operation not permitted
The operating system could not even send the packet, so the problem is local (adapter, route or firewall), not the remote host.
Networking: Windows: Default gateway is not available / Diagnose Connection Problems: DHCP not enabled
The PC can't reach its router, so it has no path out of the local network.
Networking: Your Remote Desktop Services session has ended. Possibly the network connection was lost / Remote Desktop disconnected, error code 0x904
An established Remote Desktop session dropped because the network under it stalled or the session was reset.
Networking: Windows error 64: The specified network name is no longer available — SMB session dropped
A connection to a Windows file share was cut while in use.
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.
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.
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.
Schannel Event 36887: A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 46/48/40
A Windows TLS client or server logged that the peer sent a fatal alert, with a code that explains why.
SMTP: 550-5.7.25 The IP address sending this message does not have a PTR record setup, or the corresponding forward DNS entry does not point to the sending IP
Gmail (and others) require your sending IP to have a reverse DNS (PTR) record that resolves back to the same IP; yours has none o…
Postfix: status=deferred (Host or domain name not found. Name service error for name=example.com type=A: Host not found, try again)
Postfix could not resolve the destination domain through DNS — the resolver is down or unreachable, or the domain does not exist.
Networking: IPv4 address 169.254.x.x (Autoconfiguration / APIPA) — the PC couldn't get an address from DHCP
With no DHCP answer, the computer gave itself a link-local 169.254.x.x address, which only works on the local segment.
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: 534-5.7.9 Application-specific password required. Learn more at https://support.google.com/accounts/answer/185833
The Google account has 2-Step Verification on, so SMTP clients cannot use the normal password; they need an app password (or OAut…
SMTP: 535 5.7.139 Authentication unsuccessful, basic authentication is disabled / SmtpClientAuthentication is disabled for the Tenant
Microsoft 365 turned off password-based SMTP AUTH for your mailbox or tenant; your client must use OAuth or the setting must be r…
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…
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.
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…
Laravel: Symfony\Component\Mailer\Exception\TransportException: Connection could not be established with host "smtp.mailtrap.io:2525": stream_socket_client(): Unable to connect
Laravel's mailer could not connect to the SMTP host configured in `.env`.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError