Futurista Soft Book a call (opens in a new tab)
Founder guide

Lovable app not deploying? How to fix publishing and domain problems

Last reviewed 21 November 2026

It works in the editor, but the live site is out of date, broken, or won’t publish at all. Most of these problems have a known cause. Find out which one you have before you spend credits on prompts.

Short answer

First check that you clicked Publish changes: the live site keeps the version you last published until you publish again. If publishing fails, the button Lovable offers tells you what kind of problem it is: Try again for a temporary one, Try to fix for an error in the app. For a custom domain, check your DNS records, give them time to update, and remove old records left at your DNS provider.

Is it published, or only saved?

This catches out a lot of people. According to Lovable’s publishing guide, the live site keeps showing the version you published, and later changes stay off it until you publish again.

When publishing fails

What you seeWhat it meansTry first
Fix build errorsThe latest change has a code error, so there’s nothing that can be publishedUse Try to fix once. If the error comes back, revert to the last working version
Publishing failed, with Try againA temporary problemWait a moment and try again. Check Lovable’s status page
Publishing failed, with Try to fixAn error in the app or its settingsTry to fix, then read what it changed before you publish
Publishing failed, with Ask LovableA database change conflicts with data that’s already thereExport a backup first if real customers use the app. This is where data gets lost
Review security findingsThe security scan found serious problemsReview them. Don’t choose Publish anyway if the app holds other people’s data
Approval needed or Publishing blockedA rule set by your workspace adminAsk the admin. It isn’t a fault in the app
Fails after it worked beforeA service the app depends on has disconnected, such as an expired Supabase connectionReconnect it in settings, then Try again

Lovable gives each account 10 free uses of Try to fix, and each one comes back 24 hours after you use it. After that, fixes use credits, so don’t press it over and over on the same error.

Custom domain won’t connect

Custom domains need a paid Lovable plan, and the domain shows nothing until the app is published. You connect one under Project settings → Domains, and Lovable shows the exact records to add at your DNS provider. DNS changes can take up to 72 hours. Until the domain shows Active, your app stays on its lovable.app address.

Stuck on Setting up, showing an old site, no padlock or a Cloudflare error? Our custom domain troubleshooting guide covers each one, including which old records to delete and which to keep for your email.

Works in preview, broken on the live site

The most common version of this is sign-in. You log in fine in the editor, then it fails on the live site or your own domain. The address is usually missing from the list of allowed sign-in addresses.

Sign-up or password reset emails not arriving at all? That’s a separate problem: see Lovable emails not sending.

One more check while you’re there: anything named VITE_ is sent to every visitor’s browser. A secret key there isn’t secret. Our security checklist covers what to look for.

When to get help

If the app itself keeps breaking, start with what to do when your Lovable app stops working.

Questions founders ask

Why don’t I see my latest changes on the live site?

Because publishing copies the app as it was at that moment. Open the publish dialog and click Publish changes. A dot on the Publish button means there are changes that aren’t live yet.

How long does a custom domain take to work?

Lovable says DNS changes can take up to 72 hours, though most are live within a few hours. If it’s still not working, see our custom domain guide.

Does pushing to GitHub update my live app?

No. GitHub keeps your code in sync, but the live Lovable site only changes when you publish from Lovable. If you host the app somewhere else, that host deploys from GitHub instead.

Read next