UrgisoftAI-built apps

AI-built apps · November 2026

Lovable custom domain not working: four checks, and seven causes with the fix for each

Short answer: a domain that will not go live is almost always one of three things: the records that point your domain at Lovable are missing or were entered in the wrong place, old records from your previous website are still there, or something sits in between (Cloudflare's proxy, or a rule about who may issue your security certificate). Lovable tells you which step it is stuck on; four free checks, about ten minutes, show you the rest. Then find your case in the seven causes below.

Four checks: where is it stuck?

A few words first. Your domain's DNS records are the public entries that say where the domain points. An A record points a name at a server, a TXT record proves the domain is yours, and the SSL certificate is what makes https:// work.

  1. Read what Lovable says. Open Project → Settings → Domains. Under the domain there is a status and a progress line. The table below says what each one means. You can also ask Lovable in the project chat about the domain: by its own documentation it reports the state, how long it has been there, which records it expects and whether it can see them, and whether the project is published.
  2. Find out who answers for your domain. Search for "NS lookup" and enter your domain. The nameservers it shows (for example ones with "cloudflare", "godaddy" or "namecheap" in the name) tell you where the records must be changed. That is not always the company you bought the domain from.
  3. Compare the records the world sees with the ones Lovable asks for. In Lovable, open the three dots menu next to the domain and choose "Setup instructions". Then look your domain up at dnschecker.org and compare the A, AAAA and TXT results line by line. Anything extra counts as much as anything missing.
  4. Open three addresses in a private window: yourdomain.com, www.yourdomain.com and the app's your-app.lovable.app address. If the lovable.app address is broken too, the domain is not your problem: a blank page after publishing has six usual causes.

What Lovable's messages mean

What you seeWhat it meansWhat to do
Setting up domainLovable is preparing the connection, checking records or issuing the certificate.Read the progress line under it. If "Set up DNS" appears, the records are not there yet.
Looking for your DNS recordsLovable cannot find the records it asked for.Causes 2, 3 and 4.
DNS records found, waiting for them to take effectThe records are right; other networks have not caught up.Wait. Lovable says most changes are live within a few hours and it can take up to 72.
Finishing up, for a long timeThe last step is the SSL certificate.Cause 5.
Active, but the site is not thereThe connection is done. The app still has to be published, and stray records can still send visitors elsewhere.Causes 1 and 3.
Needs attention, or a warning under the domainLovable found a connection problem; the warning names it.Follow the warning, then "Check again" in the three dots menu.
Domain Service ErrorThe setup window (a service called Entri) did not load. No record was changed.Turn off the ad or script blocker for Lovable, or choose "Setup instructions" and enter the records yourself.

Seven causes, and the fix for each

  1. The app is not published, or the plan does not include a custom domain. Lovable's documentation says custom domains are available on paid plans, and that an Active domain still shows nothing until the project is published. While a domain is still being set up, Lovable keeps publishing the app to its lovable.app address.
    Fix: publish the project. If the domain shows the app but an old version of it, that is the same thing in another form: the live site keeps the last published version until you choose Publish, then "Publish changes".
  2. The records are missing, incomplete, or entered in the wrong place. Three slips cause most of this. The records were added at the company that sold the domain while another company's nameservers answer for it (check 2). The name field was filled in the wrong way: depending on the provider, the root domain is written as @, left blank, or typed out in full; Lovable's page names Amazon Route 53 as one that wants it blank or typed out. Or the proof record was cut short: it is a TXT record on the name _lovable (for a subdomain, _lovable.blog) whose value starts with lovable_verify=, and the whole value has to be there.
    Fix: copy every record from "Setup instructions" again, at the provider your nameservers point to. The root domain and www each have their own records; if Lovable lists an AAAA record, add that too. Then choose "Check again".
  3. Old records from your previous website are still there. Visitors land on the old site, a parking page, or the right app only some of the time. Lovable's page warns that an extra A or AAAA record can send visitors to the wrong place even when the domain shows Active, and that some providers add an AAAA record to a new domain by themselves; visitors whose devices prefer that newer kind of address then reach it instead of your app. "It works on my laptop and not on my phone" is a reason to look here first.
    Fix: at your DNS provider, keep the records Lovable gave you for that name and remove every other A, AAAA or CNAME record on the same name. Leave everything else alone, above all the MX records: those carry your email.
  4. Cloudflare's proxy is switched on (the orange cloud). The page shows "Error 1001" or "Error 1003", or Lovable keeps looking for records that you can see are there. Lovable's page says these two errors come from Cloudflare's proxy, not from Lovable.
    Fix: in Cloudflare's DNS settings, set the records for this domain to "DNS only" (the gray cloud), wait a few minutes and choose "Check again". If you want Cloudflare in front of the app on purpose, connect the domain again with Advanced → "Uses Cloudflare or similar proxy" switched on. Lovable then gives you a CNAME record that points at the app's published address, so publish first. In that setup, by Lovable's own words, the proxy is yours to configure and Lovable does not check it.
  5. The security certificate cannot be issued. The domain sits at "Finishing up", or the browser says the connection is not private. One cause Lovable documents: the domain has CAA records, a list of which certificate companies may issue certificates for it, and none of the ones Lovable uses is on the list. A subdomain inherits the list of the domain above it.
    Fix: look up the CAA records of your domain (the same lookup site shows them). If there are any, add the three Lovable names, or at least one: 0 issue "pki.goog", 0 issue "letsencrypt.org", 0 issue "ssl.com". If you cannot change the main domain's list, add the records on the subdomain you are connecting. Then "Check again". No CAA records at all is fine: then any company may issue.
  6. One address works and the other does not. yourdomain.com opens and www.yourdomain.com does not, or the other way round. They are two separate names with their own records. When you connect a root domain, Lovable offers to connect www as well and send its visitors on; if that was switched off, or only one set of records was entered, some of your visitors get an error.
    Fix: connect both, enter both sets of records, and set the one you want people to see as the primary domain. Lovable then sends the other addresses on to it. One thing to know for search: Lovable says it uses temporary redirects (302) between a project's domains, not permanent ones (301). More on Lovable apps and Google.
  7. The domain works, but sign-in or payment now fails. The page loads on your own domain, and then "Sign in with Google" lands on an error, the confirmation email links to the old lovable.app address, or the customer comes back from Stripe to the old address. Nothing is wrong with the domain here: other services still have the old address written down. This one is from our own engineering practice, not from Lovable's domain page.
    Fix: add the new address wherever the old one is listed. If the app uses its own Supabase project: Authentication → URL Configuration, the Site URL and the list of redirect URLs. For Google sign-in: the allowed addresses of the sign-in client in Google's console. For Stripe: the addresses the customer is sent back to after paying. Then search the app's code for the old address. Login and Supabase errors: seven causes. Stripe payments not working: seven causes.

Before you change the records again

  1. Write down what is there first. Take a screenshot of your provider's whole record list before you delete anything. A removed email record is easy to put back when you know what it said.
  2. Change, then wait, then check. A record change is not instant. Changing it three times in an hour leaves you unable to tell which version the world is looking at. Lovable says most changes show within a few hours and some take up to 72.
  3. Removing and adding the domain again is a last step, not a first one. Lovable lists it as something to try, but when the cause is a wrong or extra record at your provider, adding the domain again leaves that record where it was.
  4. If Lovable manages the records (you bought the domain through Lovable, or moved it there), there is nothing for you to correct: its page says to choose "Check again" and write to Lovable's support if the status does not change.

Sources, read November 22, 2026: Lovable's documentation, Set up a custom domain, Connect a domain from another provider and Publish, for the statuses, the records, the Cloudflare and certificate notes, the waiting times and the redirects. Lovable changes these pages; check them for your own case. Cause 7 and the advice under "Before you change the records again" are from engineering practice. This is a checklist, not a study: we have not counted how often each cause happens. Other pages on this site: not sure what is broken? A ten-minute check. Moving a Lovable or Bolt app to Vercel or Netlify. Six security checks. Lovable to WordPress. Convert a Lovable app to iOS. Slow on phones? Our demo shop, measured before and after. Urgisoft is not affiliated with Lovable, Cloudflare, Supabase, Stripe or Google.

Want it fixed for you?

We find which record or setting is stopping your domain and give you the exact records to enter at your provider, and in the app's own code we fix what still names the old address: sign-in, emails, payment return pages. Then we show you the domain answering, with and without www. Fixed prices on Fiverr: one bug from $40, up to five bugs with the app working live from $150. No fix, no charge. We work through GitHub or as a collaborator you invite; we never ask for your password, not for Lovable and not for your domain provider.

See the gig on Fiverr