Troubleshoot custom domain and SSL issues
Diagnose stuck DNS records, domain statuses, and SSL setup for your SAMI OS agent website.
If your custom domain is stuck on a pending status or your SSL certificate isn't issuing, the Domain section tells you exactly what's missing. This guide explains how to read those signals and fix the most common snags.
Read the record badges
After you click Check now in the Domain section of the website builder, each DNS record gets a badge that compares what SAMI found at your provider against the value it expects. Match the badge to the fix:
- Record found — the record is live and correct. Nothing to do.
- Found but value doesn't match — the record exists, but the value is wrong. Re-copy the Value field with the copy button and overwrite the existing record. Watch for an extra space, a trailing period, or your provider auto-appending your base domain to the Name.
- Not found — add this record — SAMI can't see the record yet. Either it hasn't been created, or DNS hasn't propagated. Confirm the Type, Name, and Value match, then wait and re-check.
The Name field is where most setups go wrong. Providers like Squarespace, Namecheap, GoDaddy, and Route 53 auto-append your base domain — enter only the short subdomain portion SAMI shows. If your provider doubles the zone (for example _acme-challenge.www.example.com.example.com), switch the picker to Other / not sure and use the full form instead.
What each domain status means
The status card walks your domain through stages. Knowing where it's parked tells you whether to wait or act:
- Connecting to Cloudflare — SAMI is provisioning the domain. This clears on its own.
- Waiting on ownership verification — add the ownership TXT record so Cloudflare can confirm the domain is yours.
- Waiting on DNS to propagate — your records are in; SAMI is waiting for them to spread across the internet.
- Issuing SSL certificate — all records are found and Cloudflare is minting your certificate. No action needed.
- Needs attention — setup is stuck. The card highlights in yellow and shows what Cloudflare reports. Re-check your records against the badges.
- Setup failed — something blocked provisioning. Use Remove and try again to start over.
Use Check now and expected timing
SAMI rechecks on its own about every 30 seconds while a domain is pending, so the status often advances without you. To force a check, click Check now — but it's rate-limited to once every 30 seconds, and checking sooner shows "Checked recently — please wait 30 seconds between checks." That's expected, not an error.
DNS typically propagates within 5–15 minutes, and the SSL certificate usually goes active within another few minutes after all records are found. SAMI emails you when your site is live. If a record still reads Not found after 30 minutes, it almost always means the Name or Value at your provider doesn't match.
On Cloudflare, set Proxy status to DNS only (the gray cloud) for every record. The orange cloud breaks routing and prevents the certificate from validating — a common cause of a domain that's stuck on Issuing SSL certificate.
Remove and re-add a domain
When a setup is hopelessly stuck or shows Setup failed, the cleanest fix is to start fresh. In the Domain section, click Remove Custom Domain (or Remove and try again on a failed card) and confirm. Your free yoursite.sami-os.com address keeps serving the site the whole time. Then re-enter the domain to regenerate fresh records and work through the badges again.
Once you're live, surface the site across your workspace — link it from Messages, and route the leads it captures into Contacts and your Pipeline.
Related articles
Last updated 2026-06-21