SSL Issued but the Site Shows a Self-Signed or Wrong Certificate
The host made a certificate but the server is still serving another. Find where the mismatch is.
Reference guide. This guide is written from established practice and the official documentation of the tools involved. We have not yet tested every step on a live demo site. Back up your site before you change anything.
You see "Not secure" or a warning even though your host says SSL is active.
Causes
- Cache: the browser or CDN has the old certificate. Try a private window and another device.
- Pointing to the wrong place: the domain's DNS still points to another server, which serves its own default certificate. Check the A record. See DNS records.
- Certificate not attached: it exists but is not assigned to this domain or subdomain. In the hosting panel, check the SSL page for the right domain.
- www vs non-www: the certificate covers one but not the other.
- Proxy or CDN in front: check its SSL mode. See Cloudflare errors.
- Pending issue: new certificates need DNS to be correct first, and a CAA record can block issuing. See CAA guide.
What to do
- Click the padlock and read who issued the certificate and which names it covers.
- Re-run the host's SSL install or AutoSSL for the domain.
- Wait a short while, then test again.
- Redirect HTTP to HTTPS only after it works. See HTTPS redirect.
Also see name mismatch.
Related guides
- How to Move a WordPress Site to a New Host or Domain: Checklist
- Wix Domain Connection Error: Pointing vs Nameservers and Common Fixes
- Website Builder Support Not Resolving Your Problem: Escalation Steps
- Website Builder Renewal Price Jump and Hidden Costs: How to Plan
Did this solve it? If not, email hello@sitefixlab.org with the exact error text and we will look into it. Try the problem finder.