Lovable custom domain not working
If your Lovable domain is stuck, open Project, Settings, Domains and read the status. Setting up means SSL is still issuing, a Cloudflare 1001 or 1003 means the orange cloud is on, www stays dark when that hostname was not added, and Offline means the DNS records no longer point at the project. The checks below are from Lovable's custom domain docs.
Short answer: If your Lovable custom domain isn't working, it's almost always one of four things: SSL still pending, Cloudflare's orange cloud (proxy) switched on, a missing www record, or the domain showing Offline. Each has a fix below. If you'd rather not deal with DNS at all, you can publish the built app on DropTheHassle and buy the .com with the site: then there are no DNS settings to edit. A .com is €19 / $19 a year, including VAT in the EU, the same every year.
Your AI can publish. It can never spend your money.
Built it with ChatGPT, Claude, Gemini, Cursor, Replit, v0, Windsurf or by hand? Same steps.
Last updated: 26 October 2026. Steps were checked against Lovable's custom domain page on 27 September 2026.
SSL pending, stalled, or failed
- Status Setting up: verification is done and the certificate is being issued. Lovable says the browser can show a security warning until then. Wait for Live before you send people there.
- Status Stalled or Failed: click Retry. You do not have to remove the domain and add it again.
- If the domain has CAA records, those records must allow Lovable to issue the certificate. Lovable's page names the issuers to allow, including
ssl.com. - Do not upload a certificate at your registrar. Lovable issues its own. If it still has not been issued after 72 hours, Lovable says to contact Lovable Support.
While status is Verifying, leave the A record and the TXT record exactly as Lovable showed them. The docs say that changing the A record before verification finishes blocks the certificate. The A record they document points at 185.158.133.1. The TXT host is _lovable, and the value starts with lovable_verify=. An old AAAA record can send traffic elsewhere. Remove it for the hostname you are connecting.
Cloudflare error, orange cloud
Lovable says errors 1001 and 1003 come from Cloudflare's proxy, not from Lovable. In the DNS settings for that hostname, set the record to DNS only (gray cloud), not Proxied (orange cloud). Wait a few minutes and open the site again.
Use the orange cloud only if you meant to. Lovable has a separate option, Uses Cloudflare or similar proxy. In that mode Lovable gives you a CNAME to your lovable.app URL instead of the A record, and it does not ask for the verification TXT. You maintain that proxy yourself. The docs are on the same custom domain page.
www was not added
- A domain bought through Lovable gets the root and
wwwset up automatically. Both show as their own rows. - A domain you bought somewhere else connects
wwwonly when Redirect www to the root stays on. That is the default. Lovable then listswwwseparately. - If you turned that option off,
wwwshows as Not connected after the root is Live. Click Connect next to it.
The domain says Offline
Lovable's status table says Offline means the domain was Live and the DNS records are no longer valid. The name is not pointing at the project. Click Recover, read the records on the screen, and put those records back at your DNS host.
Removed is different. Lovable says the domain was removed because it was added to another project, or DNS verification never finished. Click Reconnect.
Custom domains on Lovable are on paid plans, from the same docs. Connecting the name is a separate job from publishing the project: the domain will not serve the app until the project is published.
Entri or manual records
Lovable offers two ways to connect a domain that you did not buy there. Both still ask you to prove you own it.
- Automatic setup with Entri. Lovable detects the DNS host. You log in and let Entri write the records.
- Manual setup. Pick the host from the list, or choose manual setup if it is missing. Copy the A record and the TXT record and paste them at the registrar yourself.
The host name on the A record depends on the registrar. Lovable says it may be @, blank, the domain name, or the subdomain label. DNS can take a while. Lovable says up to 72 hours, and that most updates show within a few hours.
If you would rather not debug DNS
Publish the built folder on DropTheHassle instead. You get a free yourname.dropthehassle.app link on HTTPS, with no card. A domain you already own connects for free after one A record, to the address shown on your screen. A .com bought in the dashboard is €19 / $19 a year, including VAT in the EU, the same every year, and that purchase needs no DNS edit. A mailbox is optional: €5 / $5 a month, including VAT in the EU, for the first inbox, €3 / $3 a month per extra inbox.
The how-to, including the Lovable export, is Put your Lovable app on your own domain, step by step. Your AI can publish the folder. It can never spend your money.
Questions
Why is my Lovable domain not working?
Usually SSL is still pending, Cloudflare's proxy (orange cloud) is on, the www record is missing, or the domain shows Offline. Fix the one that matches, or publish the built folder elsewhere and skip DNS.
Why is SSL stuck?
Setting up means the certificate is still being issued. Stalled or Failed means click Retry. If CAA records are in the way, allow the issuers Lovable lists. After 72 hours, contact Lovable Support. Source: Lovable custom domains.
What is Cloudflare error 1001 or 1003?
Lovable says it is the proxy. Set the record to DNS only, the gray cloud.
Why does www not load?
For a domain bought outside Lovable, www is a second hostname. Leave the redirect on, or click Connect next to www after the root is Live.
What does Offline mean?
The DNS records stopped pointing at the project. Click Recover and put them back.
Entri or manual?
Entri writes the records after you log into the DNS host. Manual means you paste the A record and the TXT record yourself.
Can I skip this?
Yes. Publish the built folder here. Press Upload (free), then Drop your folder. You do not sign in first. A .com is €19 / $19 a year, including VAT in the EU, the same every year, with no DNS edit. Connecting a domain you already own is free.
Custom domain not secure, not loading, or login redirect breaks
My custom domain says not secure. Why?
The browser warns until the domain has a valid HTTPS certificate, and a certificate can only be issued once the domain points at the right server. A .com bought on DropTheHassle is set up for you: the A record and www are added and HTTPS follows. For a domain you already own, add the A record shown on your screen, remove other A and AAAA records for that name, and add the TXT record shown, which proves you own it. DropTheHassle issues the certificate once the domain checks out. The live check on your site shows whether the domain points here, is secure, and loads.
My custom domain is not loading. What now?
Usually the DNS record is not there yet or points somewhere else. Check that the A record points at the address on your screen, that no old A or AAAA record is left, that you used an A record and not a CNAME for the bare name, and that the record is DNS only (no proxy, such as an orange cloud). DNS changes can take a while to reach everyone. DropTheHassle keeps checking; press Check now to check again. Your site stays reachable on its free yourname.dropthehassle.app link in the meantime.
Login redirect breaks after I moved to my custom domain. How do I fix it?
Sign-in providers only send people back to addresses on their allowed list, so a login set up for the old address fails on the new one. DropTheHassle doesn't run your login. Add https://yourdomain.com (and the www address if you use it) to the redirect URLs in your auth provider, for Supabase the Site URL and Redirect URLs, and to the authorized redirect URIs of any Google or GitHub sign-in app. Replace the old address in your .env if it is there, then build and publish again.