Why custom domain not working - verification failed - even after 48 hours (68 hours now)
I have asked AI to suggest running terminal commands to check my current setup for the my custom domain - api.mydomainname.com - at Appwrite Cloud
Here is the comment / feedback from the AI analysis:
Perfect! The global DNS propagation check confirms all DNS servers worldwide see your CAA records correctly, including certainly.com.nslookup+1 Summary of Global DNS Results ✅ Google DNS (8.8.8.8): Shows certainly.com and sgp.cloud.appwrite.io ✅ Cloudflare DNS (1.1.1.1): Shows certainly.com and sgp.cloud.appwrite.io ✅ Quad9 DNS (9.9.9.9): Shows certainly.com and sgp.cloud.appwrite.io
All three major global DNS providers return the same results, confirming:
CAA record includes 0 issue "certainly.com" ✅
CNAME points to sgp.cloud.appwrite.io ✅
DNS is fully propagated worldwide ✅
Final Diagnostic Report for Appwrite Support You now have complete evidence that this is a Fastly/Certainly backend issue.
SSL Certificate Analysis OpenSSL Connection Test Results:
Current certificate being served:
Subject: CN=t.sni-820-default.ssl.fastly.net Issuer: C=US, O=Certainly, CN=Certainly Intermediate R1 Valid: Nov 3 16:02:04 2025 GMT - Dec 3 16:02:03 2025 GMT Problem Identified:
Fastly is serving default/fallback certificate (t.sni-820-default.ssl.fastly.net)
Certificate is NOT for api.mydomainname.com
Certainly IS the CA (correct), but certificate issuance failed despite valid CAA
Can you please assist - the issue i think is quite similar to https://discord.com/channels/564160730845151244/1395340182810787840 which require manual intervention from your side and contacting Fastly...
