Why a free certificate fails to issue, and how to fix "Not secure" and padlock warnings.
The certificate will not issue
When issuing fails, HostPanel shows the reason and a Try Again button. The usual causes are:
- The domain does not point to Twerple yet. Let's Encrypt checks the domain by visiting it, so the domain's A record must point to your server. Check with Pointing your domain to Twerple, wait for the DNS change to spread, and try again.
- The www version points somewhere else. Make sure
wwwpoints to the same server as the domain. - Cloudflare is in the way. If the domain is proxied through Cloudflare, let HostPanel manage Cloudflare during issuing, or switch the cloud to grey (DNS only) for a few minutes.
- A CAA record blocks Let's Encrypt. If your domain has a CAA record, it must include
letsencrypt.org. - Too many attempts. Let's Encrypt limits how many certificates can be issued for a domain in a short time. Wait an hour and try again.
The browser says "Not secure"
- Open the site with
https://at the start. If that works, turn on Force HTTPS. - If the padlock has a warning, the page loads some files over
http://(mixed content). Update those links tohttps://. - If the browser says the certificate is for a different name, the certificate does not cover the exact address you visited, for example a subdomain. Issue a certificate for that subdomain.
- If it says the certificate has expired, check that Auto-Renew is ticked and click Renew.
Still stuck? Open a support ticket with the domain name and a screenshot of the error, and we will sort it out.