Record the affected URL
Note the full public hostname, error text, browser and time. Check whether the issue affects the main name, www, one subdomain or several names.
SSL guides & resources
SSL certificate errors: what to check first
Identify the warning and the affected hostname before replacing a certificate or changing server settings.
Start with the evidence
Work from the exact warning, not just “SSL is not working”.
Check the served certificate
Inspect the certificate the live endpoint presents: names, expiry and issuer. Compare it with the intended installation.
Review installation checks 
Identify the deployment owner
Confirm the hosting platform, recent changes, and whether a CDN, proxy or load balancer serves the connection.
Match the symptom to the next check
Error wording varies by browser and platform. These checks narrow the cause; they do not replace a platform-specific diagnosis.
| What you see | What to check | Practical next step |
|---|---|---|
| Expired or not-yet-valid certificate | Check the certificate dates and the client clock. Confirm which certificate is being served. | Arrange an appropriate replacement, install it and verify the live site. |
| Name mismatch | Compare the requested hostname with the certificate’s covered names. Check server/SNI selection. | Correct the deployment or request coverage for the missing name. |
| Unknown issuer or incomplete chain | Check that the intended certificate and issuer-provided chain are installed. | Use the CA’s platform instructions; do not substitute an unrelated intermediate. |
| Mixed content | Look for HTTP images, scripts, styles or other requests on an HTTPS page. | Update the application’s resource URLs and verify those resources support HTTPS. |
| Old certificate still appears | Check each relevant server, gateway or CDN endpoint and its active certificate binding. | Have the administrator verify deployment across the affected endpoints. |
Keep the checks safe
Do not ask visitors to bypass certificate warnings or disable certificate validation. Share public URLs and error details; keep passwords, private keys and confidential files out of the initial support message.
Send a useful support request
Include an order reference for an existing SSLS purchase, the public URL, exact error, platform, recent changes and checks already performed.
Existing certificate order
Use the records and support options available in your account so the team can identify the correct certificate.
Open My Account Installation or replacement help
Describe the affected endpoints and what your administrator has checked. Confirm the work and any charges before proceeding.
Discuss installation support Common questions
Will buying another certificate fix every HTTPS warning?
No. First determine whether the issue is coverage, expiry, deployment, trust-chain configuration or application content. A new purchase may not address the cause.
Why does the warning affect only www or one subdomain?
That hostname may not be included, may reach another server or may use a different certificate binding. Check the exact name and endpoint.
What if the site uses a CDN?
The browser-facing edge and the origin can have separate TLS configurations. Have the administrator check both according to the provider’s instructions.
Why do I still see mixed content after installing a certificate?
An HTTPS page can still request some resources over HTTP. Fix those application references and check the browser console for remaining insecure requests.