Lovable custom domain not working — DNS and Vercel fix guide
Lovable custom domain not working — DNS and Vercel fix guide
Lovable deploys to Vercel by default. Adding a custom domain requires adding DNS records at your registrar pointing to Vercel, then configuring the domain in your Vercel project settings. Three things commonly go wrong: wrong DNS record type (A vs CNAME), DNS propagation delay (up to 48h), and SSL certificate not provisioningbecause the domain isn’t fully pointed yet.
Quick fix for Lovable custom domain not working —
Step 1 — Add domain in Vercel
Vercel Dashboard → your project → Settings → Domains → Add Domain. Enter your domain (without https://). Vercel shows you the DNS records to add.
Deeper fixes when the quick fix fails
- 02
Step 2 — Add DNS records at your registrar
At your domain registrar (Namecheap, Cloudflare, GoDaddy), add the records Vercel provided. For apex domains (
yoursite.com): add an A record pointing to76.76.21.21. For www subdomains: add a CNAME pointing tocname.vercel-dns.com.Note:if using Cloudflare, set DNS-only (grey cloud), not proxied (orange cloud). Proxied records block Vercel’s automatic certificate issuance.
- 03
Step 3 — Wait for DNS propagation
DNS changes take 15 minutes to 48 hours to propagate. Check progress at dnschecker.org — search for your domain and verify the A or CNAME record is showing correctly globally. Vercel will auto-provision SSL once DNS is propagated.
- 04
Step 4 — Force SSL in Vercel
In Vercel project → Settings → Domains, verify your domain shows “Valid Configuration”. If SSL shows “Pending”, click Refresh. If it still fails after 48h, remove the domain and re-add it — this forces a new SSL certificate request.
After it works
Test both yourdomain.com and www.yourdomain.comin a fresh browser and in incognito. If one redirects and the other doesn’t, fix the redirect rule in Vercel’s domain settings. Update any environment variable (Site URL, OAuth redirect URL) that still references the old Vercel preview URL.
Why AI-built apps hit Lovable custom domain not working —
Lovable uses Vercel for hosting. Vercel manages SSL certificates automatically — but only after your DNS is correctly pointed. Until then, your domain shows an SSL error or “site can’t be reached”.
The most common misconfiguration is a Cloudflare-proxied record (orange cloud) blocking Vercel’s automatic certificate issuance, or an A record pointed at the wrong IP for an apex domain.
“Added my domain 3 days ago, still getting 'Site can't be reached'”
Diagnose Lovable custom domain not working — by failure mode
Match your symptom to the most likely cause before applying a fix.
| Symptom | Cause | Fix |
|---|---|---|
| Domain shows SSL / certificate error | DNS records not yet propagated, cert not issued | Wait + Step 3 |
| Site can't be reached / DNS_PROBE_FINISHED_NXDOMAIN | Wrong record type (A vs CNAME) or typo at registrar | Step 2 |
| Vercel says 'Invalid Configuration' next to the domain | Cloudflare proxying (orange cloud) or wrong apex IP | Step 2 + Step 4 |
Related errors we fix
Still stuck with Lovable custom domain not working —?
If your domain has been pending for days, or you need launch-day certainty, we handle the DNS and Vercel configuration end-to-end:
- →Your domain has been stuck on 'Pending' for more than 48 hours
- →You're on Cloudflare and can't figure out proxy vs DNS-only
- →You have a launch deadline and need this working today
- →You want a hardened production setup, not just a domain pointed
Lovable custom domain not working — questions
How long does a Lovable custom domain take to work?+
Do I use an A record or CNAME for a Lovable custom domain?+
Why is my Lovable domain stuck on 'Invalid Configuration' in Vercel?+
Can I use Cloudflare with a Lovable app?+
My SSL certificate keeps failing. What do I do?+
How much does a deployment fix cost?+
Ship the fix. Keep the fix.
Emergency Triage restores service in 48 hours. Break the Fix Loop rebuilds CI so this error cannot ship again.
Hyder Shah leads Afterbuild Labs, shipping production rescues for apps built in Lovable, Bolt.new, Cursor, Replit, v0, and Base44. our rescue methodology.
Lovable custom domain not working — experts
If this problem keeps coming back, you probably need ongoing expertise in the underlying stack.