Error map
SCSV tlsv1 alert inappropriate fallback (TLS_FALLBACK_SCSV downgrade protection)
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)
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.
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.
sslv3 alert bad certificate — server rejected the client certificate (mutual TLS)
The server uses client authentication and didn't accept the certificate the client presented (or got none).
tlsv1 alert internal error — the TLS peer hit an internal problem during the handshake
The server sent alert 80, usually because its TLS configuration is broken or it can't pick a certificate.
TLS 1.3 handshake fails behind a firewall/proxy (middlebox doesn't understand TLS 1.3)
Connections succeed with TLS 1.2 but fail or reset when TLS 1.3 is negotiated.
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.
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.
POODLE (CVE-2014-3566): SSLv3 is enabled on the server
A scanner flags SSLv3 as supported, which enables the POODLE downgrade attack.
Two steps away (24)
.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.
tlsv1 alert unknown ca — the other side doesn't trust the certificate's issuer
A TLS alert 48: the peer received a certificate chain whose CA it doesn't know.
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.
Nginx 400: The SSL certificate error (495 / 496 client certificate)
Nginx rejected the request because the client certificate was invalid (495) or missing (496) on a site that requires mutual TLS.
nginx 496 SSL Certificate Required
nginx requires a client certificate (mutual TLS) and the client didn't send one.
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).
Chrome: This page isn’t working — example.com didn’t send any data. ERR_EMPTY_RESPONSE
The server accepted the connection but closed it without sending any HTTP response — a crash, timeout or misconfigured proxy on t…
Chrome: This page isn’t working — example.com redirected you too many times. ERR_TOO_MANY_REDIRECTS
The page keeps redirecting to itself or in a loop, so the browser gives up after about 20 redirects.
Chrome: This page isn’t working — example.com is unable to handle this request. ERR_HTTP2_PROTOCOL_ERROR
The HTTP/2 connection broke a protocol rule — a server, proxy or CDN sent an invalid or oversized frame/header, or closed the str…
Cloudflare Error 1020: Access Denied
A Cloudflare firewall/WAF custom rule blocked the request — the visitor’s IP, country, user agent or request pattern matched a bl…
driver failed programming external connectivity on endpoint: iptables: No chain/target/match by that name
Docker’s iptables rules were wiped (firewalld/ufw reload, iptables flush) while Docker was running, so it can’t publish ports.
ssh: connect to host x port 22: Connection timed out
SSH packets get no reply — a firewall/security group drops them, the server is off, or the IP is wrong.
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).
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,…
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.
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.
ALB HTTPS listener: CertificateNotFound / default certificate missing or SNI certificate list incomplete
An Application Load Balancer HTTPS listener can't be created or serves the wrong certificate.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError