Red warning, "Your connection is not secure," browser back button. SSL certificate errors destroy user trust and conversions instantly. Here's how to diagnose and fix them.
Common SSL Errors
ERR_CERT_AUTHORITY_INVALID
Cause: Certificate not signed by trusted authority or self-signed.
Fix: Get certificate from trusted CA (Let's Encrypt is free).
ERR_CERT_COMMON_NAME_INVALID
Cause: Certificate domain doesn't match URL.
Example: Certificate for example.com, accessing example.co.uk.
Fix: Get wildcard cert or multi-domain cert.
ERR_CERT_DATE_INVALID (Expired)
Cause: Certificate validity period ended.
Fix: Renew certificate immediately.
ERR_SSL_PROTOCOL_ERROR
Cause: Server using outdated SSL/TLS version or misconfigured.
Fix: Update server configuration, upgrade TLS 1.2+.
ERR_CERT_REVOKED
Cause: Certificate was revoked (security issue or mistake).
Fix: Request new certificate from CA.
SSL vs TLS
SSL: Outdated (versions 1-3), deprecated.
TLS: Modern replacement (1.0, 1.1, 1.2, 1.3).
Modern sites use TLS 1.2 or 1.3 only. Servers still using TLS 1.0 are at risk.
Certificate Types
Single Domain (example.com)
Secures one domain only. Subdomains not included.
Wildcard (*.example.com)
Secures domain and all subdomains (api.example.com, blog.example.com, etc.).
Multi-Domain (SAN)
Secures multiple domains: example.com, example.net, mycompany.com.
Checking Your Certificate
1. Browser Inspector
Click padlock → Details → Certificate
2. Using Our SSL Checker
Use our SSL/TLS Checker:
- Enter your domain
- See certificate details
- Identify expiration date
- Check TLS versions supported
3. Command Line
openssl s_client -connect example.com:443 -showcerts
Fixing SSL Errors
1. Certificate Expired?
- Log into your hosting provider
- Find SSL/TLS section
- Renew certificate (often auto-renews with Let's Encrypt)
- Deploy new certificate
- Clear browser cache and reload
2. Domain Mismatch?
- Check which domain the cert covers
- If adding www subdomain, get wildcard or multi-domain cert
- Reissue certificate with correct domain
- Deploy and test
3. Wrong Server Configuration?
Common with reverse proxies, load balancers, or CDNs:
# Nginx check
openssl s_client -connect your-domain.com:443
# Apache check
apache2ctl -S | grep ssl
4. Mixed Content (HTTPS with HTTP)
Page loads over HTTPS but requests resources over HTTP:
<script src="http://example.com/script.js"></script> ✗ Warning
<script src="https://example.com/script.js"></script> ✓ Safe
Fix: Update all resource links to HTTPS.
Certificate Authority Issues
Self-Signed Certificates
You signed the certificate yourself (not a trusted CA). Browsers warn users.
Solution: Get cert from trusted CA (Let's Encrypt, DigiCert, Sectigo).
Untrusted CA
Certificate from lesser-known or untrusted authority.
Solution: Reissue from major CA.
Monitoring Certificate Health
Set up Alerts
Many hosting providers auto-alert before expiration. Set 30-day reminder as backup.
Automated Renewal
Let's Encrypt certificates auto-renew. Most hosting auto-enables this.
Monitoring Tools
- SSL Labs — Free SSL security assessment
- Comodo SSL Checker — Certificate validation
- Our SSL/TLS Checker — Quick diagnosis
Common Mistakes
1. Letting Certificate Expire
Browser immediately warns all visitors. Kills traffic and trust.
Prevention: Set calendar reminders, enable auto-renewal.
2. Using Different Certificate per Subdomain
Inefficient. Use wildcard cert instead.
3. Not Updating Old TLS Versions
TLS 1.0 is deprecated. Browsers drop support yearly.
4. Self-Signed Certs in Production
Users see security warnings. Kills trust and conversions.
Pro Tips
- Use Let's Encrypt (free, auto-renews)
- Set 60-day expiration reminders
- Enforce HTTPS site-wide (HTTP to HTTPS redirect)
- Add HSTS header to require HTTPS
- Monitor certificate health monthly
Conclusion
SSL certificate errors are fixable — usually within 30 minutes. Most are expiration (automatic renewal fixes this), domain mismatch (recertification), or server misconfiguration (hosting provider support). Regular monitoring keeps visitors secure and trusting.
Comments
Leave a Comment
No comments yet. Be the first to comment!