Error map
weak ciphers Security scan: weak ciphers enabled (3DES / RC4 / EXPORT / NULL — SWEET32, CVE-2016-2183)
SSL / TLS · layer 2, Network
Centre: this error. First ring: errors it is linked with (11). 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 (11)
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.
Chrome: ERR_HTTP2_INADEQUATE_TRANSPORT_SECURITY — HTTP/2 requires a modern TLS cipher
The server speaks HTTP/2 but negotiated a TLS version or cipher that HTTP/2 forbids (blocklisted ciphers or TLS below 1.2).
nginx: [emerg] SSL_CTX_set_cipher_list("...") failed — invalid ssl_ciphers string
The `ssl_ciphers` value contains a cipher or syntax OpenSSL doesn't accept, so nginx won't load the config.
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.
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.
ROBOT attack (CVE-2017-13099): vulnerable RSA key exchange implementation
A scanner reports that the TLS stack leaks information through RSA PKCS#1 padding errors (Return Of Bleichenbacher's Oracle Threa…
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.
Security scan: HTTP TRACE / TRACK method enabled
The server answers TRACE requests, which a scanner flags as a cross-site tracing risk.
ERR_SSL_WEAK_SERVER_EPHEMERAL_DH_KEY — server's Diffie-Hellman key is too small
Browsers reject DHE cipher suites that use a DH key under 1024 bits (or 2048 on newer builds).
SSL Labs grade B/C: no forward secrecy / weak key exchange (RSA key exchange only)
The server's cipher order lets clients use non-ephemeral key exchange, which caps the SSL Labs grade.
Heartbleed (CVE-2014-0160): OpenSSL heartbeat extension vulnerable
A scanner reports the server leaks memory through the TLS heartbeat bug.
Two steps away (32)
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…
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.
connect: No route to host (EHOSTUNREACH)
The destination host isn’t reachable — it’s down, on another subnet without routing, or a firewall rejects with “host unreachable…
Chrome: This site can’t provide a secure connection — uses an unsupported protocol. ERR_SSL_VERSION_OR_CIPHER_MISMATCH
The browser and the server could not agree on a TLS version or cipher — the server is too old or misconfigured, or the browser is.
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…
Nginx: [emerg] no "ssl_certificate" is defined for the "listen ... ssl" directive in /etc/nginx/sites-enabled/default:3
A server block listens with `ssl` but has no `ssl_certificate` and `ssl_certificate_key`.
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
Nginx (or another server) can’t listen on the port because another process already holds it — often Apache, another Nginx, or a s…
Nginx: upstream timed out (110: Connection timed out) while reading response header from upstream
Nginx waited longer than proxy_read_timeout (60 s default) for the backend (app server, PHP-FPM) to respond, then returned 504.
Nginx: nginx: [emerg] unknown directive "x" in /etc/nginx/sites-enabled/x:12 — configuration file test failed
Nginx found a directive it doesn’t know — a typo, a missing semicolon on the previous line, a directive from a module that isn’t…
ACM certificate stuck in Pending validation
ACM is waiting to see the DNS (or email) validation record — it wasn’t created, was created in the wrong DNS zone, or has a typo.
CloudFront: 403 ERROR — The request could not be satisfied
CloudFront refused or couldn’t serve the request — wrong alternate domain/certificate, blocked by origin access settings, a WAF/g…
ERR_TOO_MANY_REDIRECTS with Cloudflare (Flexible SSL redirect loop)
The page redirects to itself forever — classic cause: Cloudflare SSL mode “Flexible” while the origin redirects HTTP to HTTPS.
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.
Java: SSLHandshakeException — TLSv1/TLSv1.1 or algorithm disabled by jdk.tls.disabledAlgorithms
A newer JDK refuses a TLS version, cipher or certificate algorithm listed in `java.security`.
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.
ECDSA certificate fails on old clients (no ECC cipher suites): serve an RSA certificate too
Legacy clients (Windows XP, Android 2.x, old Java) can't use an ECDSA-only certificate.
nginx dual RSA + ECDSA certificate setup fails (wrong order, unsupported ssl_certificate lines)
Serving both RSA and ECDSA certificates from one server block errors out or serves the wrong type.
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.
HTTP 405 Method Not Allowed
The URL exists, but it doesn’t accept the HTTP method you used (e.g. POST to a GET-only route).
HTTP 501 Not Implemented
The server doesn’t support the functionality (usually the HTTP method) needed to fulfil the request.
Webhook signature verification failed (Stripe, Razorpay, GitHub…)
Your endpoint computed a different HMAC signature than the one the provider sent, so the webhook is rejected.
Nginx: [emerg] SSL_CTX_set_tmp_dh("/etc/ssl/dhparam.pem") failed (SSL: error:1401E0A8:SSL routines:... dh key too small)
The Diffie-Hellman parameters file is too weak (e.g. 512 or 768 bit) for the current OpenSSL security level.
Chrome: ERR_SSL_KEY_USAGE_INCOMPATIBLE — the certificate's key usage doesn't allow the negotiated cipher
The server's certificate Key Usage extension does not permit the key exchange used (typically an RSA certificate missing `keyEnci…
NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED — certificate not logged in Certificate Transparency
Chrome requires publicly trusted certificates to have valid SCTs from CT logs, and this one doesn't.
Android: SSLHandshakeException: Trust anchor for certification path not found
The Android app doesn't trust the server's certificate chain (missing intermediate, private CA, or old device roots).
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.
HSTS includeSubDomains/preload breaks subdomains that only support HTTP
After adding `includeSubDomains` (or preload), subdomains without valid HTTPS become unreachable in browsers.
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…
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…
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError