Fix guide · updated 2026-11-11
Lovable custom domain not working: DNS, SSL and Cloudflare fixes
Looking for your DNS records · Issuing certificate · Error 1034: Edge IP Restricted · Error 1001: DNS resolution error
You connected your domain in Lovable and it doesn't work. It's stuck on Looking for your DNS records or Issuing certificate, it still shows your old website, the browser shows a security error, or you get a Cloudflare error page. Almost every time, the problem is in the DNS records at the company that manages your domain, not in your app. Here's how to find which one and fix it.
First, two quick checks
- Is the project published? A custom domain shows nothing until you publish the project. Custom domains also need a paid Lovable plan.
- What does Lovable say? Open Project → Settings → Domains and read the line under your domain:
- Looking for your DNS records, or Some DNS records for this domain are missing or wrong: sections 1 to 3.
- DNS records found, waiting for them to take effect: nothing is wrong. Other networks are catching up. Most do within a few hours; Lovable says to allow up to 72.
- Issuing certificate for hours: section 4.
- Active, but the site is wrong or doesn't load for everyone: section 5.
- Domain unavailable or Domain already in use: another project has the domain. Disconnect it there first.
1. Make sure you're editing the right place
DNS records only count at the company that runs your domain's DNS. That's usually where you bought the domain, unless it was moved to a service such as Cloudflare or a website builder you used before. Records added anywhere else are simply ignored, with no error.
To find the right place, look up your domain's NS records on dnschecker.org, or in a terminal:
dig +short NS yourdomain.com
The names that come back (for example …ns.cloudflare.com) tell you which company to log in to. Lovable's automatic setup finds it for you.
2. Stuck on "Looking for your DNS records"
Lovable can't see the records it asked for yet. Open Setup instructions from the three dots menu next to your domain and compare each record, letter for letter, with what's at your DNS provider:
- A record: name
@(the root domain), value = the IP address Lovable shows for your domain. Copy it from your own setup window, not from a tutorial or a forum post: Lovable gives the address for each domain, and it can ask you to change yours later. - AAAA record: only if Lovable lists one. Add it the same way, with the IPv6 address shown.
- TXT record: name
_lovable, value starting withlovable_verify=. Copy the whole value: it's unique to your domain. - www: if you kept the Redirect www option,
wwwneeds its own pair, an A record namedwwwand a TXT record named_lovable.www. It's easy to add the root's records and miss these.
Three traps catch most people:
- The Name field. Most providers want only the part before your domain:
_lovable, not_lovable.yourdomain.com. If yours doesn't accept@, leave the name blank or enter the full domain. Amazon Route 53 works that way. - Old records at the same name. Delete every other
A,AAAAorCNAMErecord at@and atwww, whether it's from a parking page, a previous host or a website builder. A name can't have aCNAMEand other records at the same time, so a leftoverCNAMEonwwwmust go. Keep yourMXrecords: they carry your email. - A proxy is turned on. If your DNS is on Cloudflare, read section 3.
Then check what the rest of the internet sees:
dig +short A yourdomain.com
dig +short AAAA yourdomain.com
dig +short TXT _lovable.yourdomain.com
On Windows, use nslookup -type=TXT _lovable.yourdomain.com, or look up the same names on dnschecker.org. The A answer must be exactly the address Lovable shows, with nothing else listed. When everything matches, open the three dots menu and select Check again.
3. Your DNS is on Cloudflare
In Cloudflare, each DNS record has a cloud icon. An orange cloud (Proxied) means Cloudflare answers with its own addresses instead of the one you typed. So Lovable can't find its A record, and visitors get a Cloudflare error page instead of your app.
We tested it with a spare subdomain of our own: an A record pointing to Lovable's address, set to Proxied. Public DNS answered with a Cloudflare address instead of Lovable's, and the page showed Error 1034: Edge IP Restricted. Lovable's docs mention errors 1001 and 1003 for the same mistake, and Cloudflare's docs list this setup under Error 1000: DNS points to prohibited IP. The reason: Lovable's own addresses also run on Cloudflare's network (we checked the public IP registry). Cloudflare only lets your domain through once Lovable has set it up, and Lovable can't set it up while the proxy hides its records.
Two ways out:
- Simplest: in Cloudflare → DNS, click the orange cloud on your Lovable records (
@andwww) so it turns grey (DNS only). Wait a few minutes, then select Check again in Lovable. - To keep Cloudflare's proxy: disconnect the domain in Lovable, connect it again, and under Advanced turn on Uses Cloudflare or similar proxy. Lovable then asks for one
CNAMErecord per address, pointing to your project'slovable.appaddress, and no TXT record. In Cloudflare, set SSL/TLS encryption to Full or Full (strict), never Flexible: Lovable redirects plainhttptohttps(we checked), and Cloudflare's docs warn that Flexible plus that redirect gives an endless loop,ERR_TOO_MANY_REDIRECTS.
4. Stuck on "Issuing certificate"
Lovable creates the HTTPS certificate for you once your records are right. You don't need to buy one, and a certificate from your registrar isn't used. Until the domain is Active, opening it over https fails with a security or connection error, and that's expected: we checked, and a domain that points at Lovable but isn't set up yet gets no certificate at all. Don't judge your setup by it before Lovable says Active.
If it stays on Issuing certificate, look for CAA records. They list which companies may issue certificates for your domain, and they can lock Lovable out:
dig +short CAA yourdomain.com
If that prints nothing, CAA isn't your problem. If it prints anything, add these three records at your DNS provider (type CAA, flag 0, tag issue):
0 issue "pki.goog"
0 issue "letsencrypt.org"
0 issue "ssl.com"
Connecting a subdomain like app.yourdomain.com? Check the root domain too: a subdomain with no CAA records of its own follows the root's. Then select Check again. If there's still no certificate after 72 hours, contact Lovable support.
5. Active, but it shows your old site or only works for some people
Lovable says Active, yet some visitors see your previous website, a parking page, or nothing at all. A leftover record is sending them elsewhere:
- An extra
Arecord from your old host: each visitor gets one address or the other. - An
AAAA(IPv6) record your provider added on its own: phones and networks that prefer IPv6 go there instead of to Lovable.
Run the dig lines from section 2 and delete every A, AAAA or CNAME at that name that Lovable didn't give you. Then test in a private window: your browser may still have the old site cached.
6. The site loads, but login fails on the new domain
Sign-in worked in preview and breaks on your domain? Your new address isn't on the list of addresses your login may send people back to. On Lovable's built-in backend, Lovable adds the domain itself once it's Active; if login still fails, ask Lovable in the project chat to add it. With your own Supabase project, add it yourself under Authentication → URL Configuration: see Supabase login redirects to localhost. With your own Google sign-in keys, also add the new redirect URL in Google Cloud Console.
Still stuck?
Ask Lovable about your domain in the project chat. It tells you the domain's state, how long it has been there, which records it expects and whether it can see them. Compare that with your dig results: the difference is your fix.
Other Lovable app problems? See Fix a Lovable app.