SSL not working
Symptoms
- The site opens on
http://but not onhttps://. - The browser reports a certificate error, an expired certificate or a name mismatch.
- The padlock is missing, or the site loads mixed content warnings.
Common causes
- The certificate was not installed, or was installed on a different account or server.
- The certificate has expired, or does not cover the exact name you visit, such as
www. - The DNS record points to a server other than the one holding the certificate.
- Redirects or mixed content send some requests back to
http://.
Safe initial checks
- Open the address directly with
https://in a private window. - Check the expiry date and names on the certificate, using the browser's certificate details.
- Confirm the DNS with
dig A yourdomain.com +short, and compare the answer with the server that holds the certificate.
These checks only read information. They do not change the certificate or the server.
Step-by-step solutions
- Certificate missing or on the wrong server. Install it on the correct hosting account. See Install on APNCloud Hosting Panel or Install on VPS.
- Expired or wrong name. Renew the certificate, or request one that covers both the bare domain and
www. See Certificate lifecycle. - DNS mismatch. Update the A record to the correct address. See A and AAAA records.
- Mixed content or forced redirect. Change links and assets to
https://, and check the redirect rules. See SSL and HTTPS settings.
How to confirm the issue is fixed
https://yourdomain.comopens with a padlock in a private window.- The certificate details show the correct names and a future expiry date.
When to contact support
Contact support if the certificate is installed correctly, DNS points to the right server, and the browser still reports an error.
Information to include in a support ticket
- The domain name and the exact browser error text.
- The result of
dig A yourdomain.com +short. - The expiry date shown on the certificate, and when you installed it.
Related articles
Last reviewed
2026-10-27