ERR_SSL_KEY_USAGE_INCOMPATIBLE means the certificate does not include TLS Web Server Authentication (OID 1.3.6.1.5.5.7.3.1) in extKeyUsage. Chrome considers such a cert unfit for HTTPS. Causes: cert issued for S/MIME, code signing, client auth. Fix: request a cert with the correct extKeyUsage from your CA, or reissue via Let's Encrypt.
This error blocks HTTPS access. Below: causes, fixes, working config, FAQ.
openssl x509 -in cert.pem -text | grep -A1 "Extended Key Usage"TLS Web Server Authenticationserver {
listen 443 ssl http2;
server_name example.com;
ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
ssl_protocols TLSv1.2 TLSv1.3;
ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256;
ssl_prefer_server_ciphers off;
ssl_stapling on;
ssl_stapling_verify on;
}SSL/TLS is the encryption protocol that protects data between the browser and server. Our tool analyzes the certificate, chain of trust, TLS version, and knownvulnerabilities.
Issuer, validity period, signature algorithm, covered domains (SAN), and validation type (DV/OV/EV).
Full chain verification: from leaf certificate through intermediates to root CA.
Protocol version (TLS 1.2/1.3), cipher suites, Perfect Forward Secrecy (PFS) support.
Set up a monitor — get Telegram and email alerts 30/14/7 days before expiration.
SSL certificate monitoring
TLS config audit
HTTPS as ranking factor
customer trust
www and subdomains.Strict-Transport-Security header forces browsers to always use HTTPS.SSL certificate monitoring, check history and alerts 30 days before expiry.
Sign up freeExtended Key Usage — an X.509 extension listing what the cert is for: serverAuth, clientAuth, codeSigning, emailProtection. Browsers require serverAuth for HTTPS.
Old browsers did not enforce extKeyUsage strictly. Chrome 82+ requires serverAuth explicitly. A cert that worked 5 years ago is now blocked.
No — the cert is signed by the CA. Changing its structure invalidates the signature. Only a reissue fixes it.
Yes. All ACME certs are issued with <code>serverAuth,clientAuth</code> in extKeyUsage. Universal format.