Your Lovable app won't deploy. Here is what usually breaks.

Your edits aren't showing on the live site

Lovable keeps the editor preview and the published site separate. Edits show in the preview right away, but the live site only changes after you publish again (the button reads Publish changes once an app is live).

If you published and still see the old version, hard refresh the page or open it in a private window to rule out a cached copy.

Your custom domain won't connect

Add the domain in the project's domain settings and copy the exact DNS records Lovable shows you into your registrar or DNS host. Typos and leftover records from an old host are the usual culprits.

If your DNS lives on Cloudflare with the orange-cloud proxy on, either switch the records to DNS only or turn on the Uses Cloudflare or similar proxy option under Advanced when you connect the domain. That option gives you a CNAME record instead of the usual A and TXT records.

If the domain sits in Setting up or Failed and you have CAA records, they may be blocking the SSL certificate. Lovable's docs list the certificate authorities to allow.

DNS changes can take up to 72 hours to spread. Check progress with a public DNS lookup tool before changing anything twice.

It works in Lovable but breaks on Vercel or Netlify

Lovable projects are Vite and React apps. When you move one to another host through GitHub, the build runs there, so every environment variable the app reads must be set in that host's dashboard. Vite only exposes variables that start with VITE_ to browser code, and it reads them at build time, so redeploy after you add them.

Run npm install and npm run build on your own machine first. If it fails locally, it will fail on the host too, and the error message is much easier to read.

npm install
npm run build

Pages 404 when you refresh or share a link

A single-page app handles routes like /dashboard in the browser. A static host looks for a real file at that path, finds none, and returns 404. Tell the host to serve index.html for every route.

# Netlify: public/_redirects
/*  /index.html  200

# Vercel: vercel.json
{ "rewrites": [{ "source": "/(.*)", "destination": "/" }] }

Login sends people back to the preview or to localhost

If the app uses Supabase Auth, open Authentication, then URL Configuration in Supabase. Set the Site URL to your live domain and add every domain you use (live, preview, custom) to the Redirect URLs list.

Questions people ask