Guide · Lovable
Lovable custom domain not working: "Action required", "Verifying" or "Unable to verify"
Updated
You connected your own domain to a Lovable app, but visitors get a security warning, an old website or an error, and the domain page shows a status such as "Action required", "Verifying" or "Unable to verify".
Why it happens
A custom domain serves your app only when three things line up: the project is published, the DNS records point at Lovable, and an SSL certificate has been issued. Until then the domain shows a status instead of your site.
Possible causes
- The project is not published: a correctly set up domain shows "Ready" and starts serving only after you publish.
- The DNS records are missing or wrong: the address record or the verification record.
- Old address, AAAA or CNAME records from a previous host are still in place and send visitors to the wrong place.
- DNS has not finished spreading: Lovable says it can take up to 72 hours, though most updates are live within a few hours.
- The SSL certificate has not been issued yet, so the browser shows a warning.
- For a domain bought through Lovable, the registrant email has not been verified, so the domain is suspended.
You can't see it yourself
You're signed in, your customers aren't. Your own device may cache the old site or an old DNS answer, so what you see can differ from what visitors get.
Related: Base44 custom domain stuck on "Pending verification" or not loading · Google sign-in fails on my custom domain: "redirect_uri_mismatch" · My builder says the app is tested, but my customers hit problems
VibeFix is independent. Lovable, Bolt, Replit, Base44, v0, Supabase, Firebase, Stripe and Vercel are trademarks of their owners.
Want it fixed?
Our AI agent finds the cause, fixes it in your code and re-checks your live app. $79 for one bug, paid up front. If we can't complete your re-check, you get your money back.
It starts with a free check that confirms the problem on your live app, no account needed.