An SSL certificate protects traffic between the visitor and the website. A valid certificate is only one part of a correct HTTPS setup: DNS, redirects, and page resources must also be correct.
### Check DNS first
The domain and `www` hostname must point to the server where the certificate is being issued. If DNS was recently changed, wait until the new destination is visible before retrying.
### Check AutoSSL in cPanel
1. Sign in to cPanel.
2. Open **SSL/TLS Status**.
3. Review the status of the domain and `www` hostname.
4. Run AutoSSL if the button is available.
5. Wait a few minutes, then test both hostnames over HTTPS.
### Common SSL symptoms
**Certificate name mismatch:** The certificate does not cover the hostname being opened.
**Too many redirects:** HTTPS is being forced in more than one layer with conflicting proxy or application settings.
**Mixed content:** The HTTPS page still loads images, scripts, or styles using `http://`. Update those resource URLs to HTTPS.
**Certificate expired:** Renew or reissue it, and verify that DNS-validation checks can reach the correct server.
### WordPress checks
Confirm that **WordPress Address** and **Site Address** use the intended HTTPS URL. Search-and-replace old HTTP URLs only after taking a database backup, and use a serialization-aware WordPress tool.
Do not disable browser certificate warnings as a “fix.” If the problem remains, send support the affected hostname and the exact browser error.
**Related articles:** How to Connect a Domain to HillHost; How to Secure WordPress After Installation