HTTPS not secure
Your domain loads, but the browser says Not secure, Your connection is not private, or shows a certificate warning. Certificates are automatic, so this means one was not issued, not renewed, or does not cover the name.
Start in the SSL Manager
Go to Connectivity → My Domains and click the SSL badge on the domain's card. Click Refresh (data can be up to 15 minutes old), then Troubleshoot. Its findings name the problem and the fix — the table below covers the usual ones.
Symptom and fix
| What you see | Cause | Fix |
|---|---|---|
| Status not issued yet | The domain was attached but the lab has not been redeployed since, or the request has not run yet | Redeploy the lab and wait a few minutes |
| Warning appeared right after attaching a new domain | Issuance takes a little time after the deploy | Wait a few minutes, then Refresh |
| Status issuance failing on a custom domain | Its A record does not point at the labs, so the certificate authority cannot reach it | Fix the A record at your DNS provider (the address is under ? on My Domains), wait for DNS to update, then redeploy |
| Status renewal failing or expired | Something that used to be true stopped being true — usually a custom domain's DNS was changed or the domain lapsed | Run Troubleshoot, fix what it names, then Request Re-issue |
| Card is blocked, a domain marked blocker in View Details | One dead domain on the lab stops the whole shared certificate from renewing | Remove that domain from the lab's Preferences and redeploy, or fix its DNS. Then request a re-issue. |
| The domain card says unverified | DNS does not currently point at the labs | Fix the A record for a custom domain. Platform subdomains fix themselves. |
| The warning is on the VS Code in the browser link | Same causes, on the editor's domain | If you chose your own domain under Domain for VS Code Web, check that domain in the SSL Manager; otherwise redeploy |
| The certificate is for a different name | The domain is not attached to this lab, or is attached to another | Check the lab's Domains tab and Preferences |
Requesting a re-issue
Request Re-issue is in the certificate's menu, only on expired or renewal failing certificates. It checks first, and refuses — listing the blocking domains — if the cause is still there. Fix the cause before asking.
An administrator approves each re-issue. Meanwhile the card shows a pending badge; Cancel Request withdraws it.
Certificate authorities limit how many certificates a name can get in a period. Repeated attempts on a broken domain can lock it out for days. Fix the cause once, then request the re-issue.
Custom domain checklist
- An A record for the exact name (for example
www) points at the labs' public address. - No other A or AAAA record for that name points elsewhere.
- The domain has not expired at your registrar.
- The domain is chosen in the lab's Preferences, and the lab was redeployed afterwards.
- The lab is running — a stopped lab cannot renew.
Do it with an AI assistant
You can also do this by asking an AI assistant connected to your account — see Connect an AI assistant to set one up.
| Ask | What the assistant does |
|---|---|
| “My site shows Not Secure — why?” | ssl_troubleshoot |
| “Is my domain attached to a running lab?” | list_domains, then list_labs |
| “Request a new certificate for it” | request_ssl_reissue |
A DNS finding has to be fixed at your domain registrar. A finding the platform is already cleaning up needs nothing from you. If the check finds nothing, the certificate is fine — look at whether the lab is running and the domain is attached.
Next
- HTTPS certificates — how the SSL Manager works
- Domains