Question 1

You are signed into a different registrar account

Accepted Answer

The automatic connect flow checks the account you are currently logged into. If the domain sits in another account — an older email address, a company account, a reseller account — that check fails even though you own the domain. Log out of the registrar and sign back in with the email address the domain renewal invoices are sent to. Search the domain in that account's domain list to confirm it is there. Retry the connect flow, or skip it and add the records manually as shown above.

Question 2

Nameservers point somewhere else (Cloudflare, another host)

Accepted Answer

Whoever holds the nameservers holds the DNS. If the nameservers were switched to Cloudflare or a hosting provider, the registrar can no longer write records for the domain — so its automatic flow refuses. Check the domain's nameservers at the registrar. Create the A and TXT records in whichever DNS provider the nameservers point to. When connecting the domain, open the Advanced section and tick "Domain uses Cloudflare or a similar proxy" so verification uses CNAME instead of A records. In Cloudflare, set the records to DNS only (grey cloud) until the domain is verified and SSL is issued.

Question 3

Delegate or sub-account access without DNS permission

Accepted Answer

Registrars let owners share limited access. A delegate can often manage renewals or products without holding DNS-edit rights, which is exactly what the connect flow needs. Ask the account owner to grant full access, or to add the records for you. Alternatively, transfer the domain into your own account and retry.

Question 4

Domain is locked or mid-transfer

Accepted Answer

During a registrar transfer, and for 60 days after one, DNS management may be frozen or split between the old and new registrar. Wait for the transfer to complete, then confirm which registrar now controls DNS. Add the records at the registrar that currently answers for the domain.

Question 5

Old A, CNAME or ALIAS records still on @ or www

Accepted Answer

A leftover record from a previous host competes with the new one. A CNAME on the root also conflicts with an A record on the same name and most providers reject the pair. Delete every existing A, AAAA, CNAME and ALIAS record on @ and www. Add only the two A records listed above. Leave MX, SPF, DKIM and DMARC records untouched — removing those breaks email.

Question 6

Domain is already attached to another project

Accepted Answer

A domain can only serve one project at a time. Adding it elsewhere detaches it from the first project. Remove the domain from the other project. Re-add it here and complete ownership verification again with a fresh TXT value.

Question 7

CAA records block certificate issuance

Accepted Answer

A CAA record is an allow-list of certificate authorities. If one exists and does not include Let's Encrypt, no certificate can be issued for the domain. Check for CAA records on the root domain. Either delete them, or add issue "letsencrypt.org". Hit Retry on the domain once the change has propagated.

Question 8

DNS simply has not propagated yet

Accepted Answer

New records take time to spread across resolvers worldwide — usually minutes, occasionally up to 72 hours. Confirm the records are correct with a public DNS checker. Wait it out. Do not delete and re-add the records repeatedly, that restarts the clock.

Type	Name	Value
A	@	185.158.133.1
A	www	185.158.133.1
TXT	_lovable	value shown in the Connect Domain dialog

Domain access troubleshooting

Your setup at a glance

Recommended fix for this setup

Common causes

What each status means

Still stuck?

We value your privacy