Lovable Custom Domain Not Working? How to Fix It

You bought a domain, connected it in Lovable, and… it doesn't work. Maybe the status has said Verifying for hours. Maybe the browser shows a security warning, or Cloudflare shows an error page, or the domain still opens your old website.

Custom domain problems look scary, but they come down to a handful of DNS settings. This guide goes through them in the order that solves most cases fastest, using the setup described in Lovable's custom domain documentation.

Check these two things first

Before touching DNS, make sure the basics are right — they're the cause more often than you'd think.

1. You're on a paid plan. Lovable's hosting documentation says custom domains require a paid plan. On the free plan, your app is available only on its Lovable address.
2. The project is published. A custom domain shows your published site. If you never pressed Publish, or unpublished the project, the domain has nothing to show. Open the project, publish it, and check that the Lovable address (yourapp.lovable.app) works first.

Also glance at our Lovable status page: if Lovable's hosting is having an incident, domains can misbehave for everyone.

The DNS records Lovable needs

For the standard setup, Lovable's docs list two records for the address you connect. Lovable shows you the exact values when you add the domain (in your project, under the domain settings); copy them from there.

The A record sends visitors to Lovable. The TXT record proves the domain is yours.

What "Host" is called at your provider: it may be labeled Host, Name, Hostname or Record. For the root domain, most providers use @; some want the field left empty, and a few want the full domain. For the TXT record, enter _lovable — most providers add your domain to the end automatically, so _lovable.yourdomain.com typed in full would become _lovable.yourdomain.com.yourdomain.com. If the provider shows a preview of the full name, check that it reads _lovable.yourdomain.com.

Copy the TXT value in full. It's long, and a value cut off by one character won't verify. Paste it, then compare the end of what you saved with what Lovable shows.

Fix it by the status you see

Lovable shows a status for each connected domain. Here's what each one means, according to Lovable's docs, and what to do.

Action required

The setup was started but never finished. Click Complete setup in Lovable to reopen it, then add the records it shows.

Verifying / Unable to verify

Verifying means Lovable is waiting to see your DNS records. Unable to verify means verification didn't complete within an hour — usually because the records are wrong or still spreading.

1. Check both records at your provider against the table above: type, host and value.
2. Remove other A, AAAA or CNAME records for the same host (see "Your domain shows the old site" below).
3. On Cloudflare, make sure the A record is set to DNS only during verification.
4. Look the records up with a public DNS checker (search for "DNS lookup" and query the A record of your domain and the TXT record of _lovable.yourdomain.com). If the checker doesn't see them yet, wait.
5. Press Check status in Lovable.

Setting up, Stalled or Failed

These are about the SSL certificate (the padlock), after your ownership was verified.

• Setting up: Lovable is issuing the certificate. A browser security warning during this step is expected. Wait.
• Stalled: issuing is taking longer than expected. Click Retry — Lovable's docs say you don't need to remove and re-add the domain.
• Failed: ownership is verified, but the certificate couldn't be issued. Click Retry.

If a domain keeps returning to Setting up, Stalled or Failed, check for CAA records at your provider. A CAA record lists which certificate authorities may issue certificates for your domain. Lovable's docs say that if CAA records exist, they must allow the certificate authorities Lovable uses — otherwise the certificate is blocked. Either remove the CAA records or add the authorities listed in Lovable's custom-domain docs. Note that a subdomain without its own CAA records follows the root domain's.

Offline

The domain was live, but its DNS records are no longer valid, so it no longer points to your project. This usually happens after someone changed DNS — moving the domain to another provider, switching nameservers, or "cleaning up" records. Click Recover in Lovable, then update the records it shows at your DNS provider.

Connection issue

The domain is still attached in Lovable, but Lovable may not be able to serve your project on it. Check that the domain isn't connected to another project or another host, and that its records still point to Lovable.

Check failed

Lovable couldn't finish its check. Lovable's docs say this status doesn't by itself mean the domain stopped working, and that you shouldn't change DNS because of it alone. Open the domain in a browser; if it works, run the check again later.

Your domain shows the old site

If the domain still opens a previous website (or a parking page from your domain provider), old records are still answering. Lovable's docs say to remove the old records for the address you're connecting, so only Lovable's A record and verification TXT record remain.

Look for these at your provider, on the same host (@ or www):

• Other A records — for example the provider's parking page or your previous host. Two A records means visitors are sent to either one at random.
• AAAA records — the IPv6 version of an A record. If an old AAAA record exists, many visitors (and certificate checks) use it instead of Lovable's A record and end up at the old site. Delete it.
• A CNAME record on the same host — a host can't have both a CNAME and an A record. Delete the CNAME.

Old answers can be cached for a while after you delete them. Test in a private window or on your phone using mobile data.

Using Cloudflare

If your domain's DNS is on Cloudflare, every record has a cloud icon: orange means traffic goes through Cloudflare's proxy, grey means DNS only.

• Errors 1001 or 1003 on your domain come from Cloudflare's proxy, not from Lovable. For the standard setup, switch the A record Lovable gave you to DNS only (grey cloud), wait a few minutes, and try again.
• Verification and SSL: keep the A record on DNS only while Lovable verifies the domain and issues the certificate.
• If you want to keep Cloudflare's proxy: Lovable's docs describe a proxy setup in which a CNAME record (with the value Lovable shows you) replaces the A record, and no verification TXT record is needed. Choose that option when you connect the domain in Lovable, and don't combine it with the A-record setup.

www and root domain

yourdomain.com and www.yourdomain.com are two different addresses, and people type both. When you connect the root domain, Lovable's Redirect www.yourdomain.com → yourdomain.com option is on by default, so www is connected too and listed as its own domain.

1. Click Complete setup next to each of the two domains and add the records Lovable shows for it. The www one uses the hosts www (A record) and _lovable.www (TXT record).
2. If you turned the option off, www shows as Not connected once the root domain is live. Click Connect next to it.
3. Check both in a private window: https://yourdomain.com and https://www.yourdomain.com.

Login breaks on the new domain

If the site opens but signing in fails on the custom domain while it works on the Lovable address, the new domain is usually missing from the list of allowed redirect addresses.

• Lovable's built-in backend: Lovable's docs say it adds your custom domains to the redirect list automatically. If it still fails, ask Lovable in the project chat to update the redirect URLs for your domain.
• Your own Supabase project: in Supabase, open Authentication → URL Configuration. Set the Site URL to your custom domain and add it to Redirect URLs. Keep the Lovable address there too until everything works.

After it's live

Once the status says Live, open the domain in a private window, click through the main pages and sign in once. If something looks wrong on the page itself — a blank page, missing data — see the blank white screen guide.

Then think about what can break a working domain later:

• The domain registration expires. Domains are rented, usually per year. If auto-renew fails — an expired card, an old email address — the domain stops working, and someone else can register it.
• The SSL certificate stops being valid. Visitors then get a full-screen security warning, and most leave.
• Someone changes DNS. A "cleanup" or a provider change can send the domain to Offline.

Pingbuddy watches all three from outside. It checks your app every 5 minutes, warns you before your SSL certificate and your domain registration expire, and sends alerts on Telegram or by email. Our guide on how to monitor a Lovable app for free shows the full setup, and adding a status page lets your users see that everything works.

Want a quick look first? A free checkup shows whether your domain answers, how fast, and when its SSL certificate and registration expire.