Most SSL warnings come from installation or configuration, not a faulty certificate. Here are the errors you're most likely to see and how to fix each one.
Name mismatch (ERR_CERT_COMMON_NAME_INVALID)
The certificate doesn't cover the exact hostname in the address bar - for example it secures yourdomain.in but the visitor is on www.yourdomain.in, or a subdomain isn't covered. Fix it with a certificate that includes the right names: a wildcard for subdomains, or a multi-domain (SAN) certificate, then reissue.
Incomplete certificate chain
The most common install mistake: the server sends your certificate but not the intermediate CA certificates, so some browsers and mobile devices don't trust it. Install the full chain - our download kit already bundles the certificate and its chain together for this reason.
Expired certificate
The validity period has ended. Renew it, or if it's part of a multi-year plan, reactivate it. Renew early - HTTPS goes down the moment a certificate expires.
Mixed content warning
Your page loads over HTTPS but pulls some images, scripts or styles over plain http://. Update those references to https:// (or protocol-relative URLs) so the whole page is secure.
Not trusted / self-signed
A self-signed certificate (or one from an untrusted source) triggers a hard warning. Replace it with a certificate from a globally trusted CA - which is exactly what we issue.
Still stuck?
Clear your browser cache, test with an online SSL checker to see the chain, and if it persists open a support ticket with your domain and we'll look.
Want to see exactly what a site is serving - issuer, expiry and covered names? Run it through the SSL Certificate Checker.