Troubleshooting SSL and domain verification issues

Fix common problems that prevent your custom domain from verifying or getting an SSL certificate.

·

The most common causes of verification failure

1. DNS hasn't propagated yet

After creating a DNS record, wait at least 30 minutes (up to 48 hours in rare cases) before clicking Verify. You can check propagation at dnschecker.org.

2. Cloudflare proxy is enabled (orange cloud)

If your CNAME record is set to Proxied in Cloudflare (orange cloud icon), disable it and set it to DNS Only (grey cloud). Proxied records hide the real CNAME target and cause SSL verification to fail.

3. The CNAME value is wrong

Copy the value from Settings → Domain exactly. Don't add extra characters or spaces. Make sure you're editing the correct DNS zone.

4. An existing A record conflicts

If you have an A record for the same host, delete it before creating the CNAME. A host can have either a CNAME or an A record, not both.

SSL certificate not issuing after verification

SSL certificates are issued automatically once DNS verification passes. Allow up to 15 minutes after verification. If it hasn't appeared after an hour, try removing the domain and re-adding it to trigger a fresh SSL request.

Was this article helpful?

Didn't solve it? Log in to Local Directory AI and ask the support chat — it can see your account.