Lovable custom domain stuck on Setting up, Stalled, or Failed (SSL)

Not sure which status you have? Start at Lovable custom domain not working.

What it means in plain English

These three statuses come after Lovable has verified that you own the domain. The problem is the SSL certificate that serves your site over https. Lovable defines them like this:

• Setting up: "Verification is complete. SSL certificates are being issued." Until the certificate is ready, "the browser shows a security warning instead of your site."
• Stalled: "SSL certificate provisioning is taking longer than expected."
• Failed: "Ownership verified, but SSL certificate could not be provisioned."

Lovable issues and installs the certificate itself. It says you do not need to install, upload, or reissue one from your registrar, such as Namecheap or GoDaddy, and that any certificate at your registrar is not used by Lovable's hosting.

Likely causes

• Your DNS has CAA records that don't allow any of the certificate authorities Lovable uses. Lovable says CAA records "restrict which certificate authorities can issue certificates for your domain."
• A subdomain inherits CAA records from its parent. Lovable's example: app.example.com inherits them from example.com if it has none of its own.
• Setup is still in progress. Setting up needs no action until the domain moves to Live or Failed.

How to fix it, step by step

1. If the status is Setting up, wait. Lovable says "No action required. Wait for Live before you open the site." Opening it earlier shows a certificate warning.
2. Check whether your domain has CAA records at your DNS provider. Check the parent domain too if you are connecting a subdomain.
3. Add CAA records that allow Lovable's certificate authorities: Google Trust Services, Let's Encrypt, and SSL.com. Lovable recommends allowing all three. If your provider asks for separate fields, Lovable says to use flag 0, tag issue, and the issuer domain as the value, without quotation marks.

0 issue "pki.goog"
0 issue "letsencrypt.org"
0 issue "ssl.com"

4. If you can't change the parent domain's records, add the CAA records on the subdomain you are connecting. Lovable says records at app.example.com take precedence over the ones at example.com. You can also remove the CAA records if you no longer need them.
5. After the DNS change takes effect, go to Project → Settings → Domains and click Retry next to the domain. For Stalled, Lovable says "You do not need to remove and re-add the domain."
6. If no certificate has been issued after 72 hours, Lovable says to contact Lovable Support.

How to check it worked

• The domain shows Live in Project → Settings → Domains.
• The site opens at https://yourdomain.com with no certificate warning.
• If the domain loads but shows your old site, see Lovable custom domain not working.

Questions people ask

Do I need to buy an SSL certificate for my Lovable domain?

No. Lovable issues and installs the certificate itself. A certificate at your registrar, such as Namecheap or GoDaddy, is not used by Lovable's hosting.

Why is my Lovable domain verified but showing a security warning?

The certificate is still being issued (Setting up) or could not be issued (Stalled or Failed). Wait for Live, or fix CAA records and click Retry.

How long should the Lovable SSL certificate take?

Lovable says to contact Lovable Support if no certificate has been issued after 72 hours.

Sources

• https://docs.lovable.dev/features/custom-domain (opens in a new tab)