[SOLVED] Why the custom domain is not working

1. I bought a domain from godaddy
2. connected the nameservers of vercel to the godaddy nameserver
3. then added the cname appwrite fra.cloud.appwrite.io for setting custom domain in appwrite in vercel dns record
4. appwrite.codechirp.in then clicked verify, then it showed verifying I waited for a long time, but it still shows verifying then when I try to reverify it shows custom domain is verified
5. so I replaced the https://cloud.appwrite.io/v1 api endpoint to my custom domain https://appwrite.codechirp.in/v1
6. But it is not working I dont know if the ssl is not generated yet or something else
7. getting this >>

Requested host does not match any Subject Alternative Names (SANs) on TLS certificate [9861f98cac61d9a00d8d37ca547236b0071bf06b4d0f37a7b11bb3b370e256a0] in use with this connection.

Visit https://www.fastly.com/documentation/guides/concepts/errors/#routing-errors for more information.

Taking a look 🔎

Can't find any indicators yet, Ill involve other engineers, and escalate to Fastly if needed.

Please keep domain's configuration as is, so we can debug this further 🙏

As per the documentation the default api endpoint can be replaced with a custom domain so that it doesn't block third party cookies I did the same as mentioned in the doc but initially I was getting cors error then now this above error is coming

And appetite should give a verified badge if the custom domain gets verified

No worries Bappa, I checked your steps, and you did it exactly as it should be, to allow 1st party cookies on production setup.

What is hapenning here is likely some race condition, and I am commited to get to bottom of this. I saw this problem once, when adding domain twice, and once it doesnt get deleted properly. I can confirm this is not the case with yours, so we are investigaring further to understhand the cause

Ok thank you will wait for the solution

A quick update, Fastly is helping us look into this. If I dont get back to you before evening, Ill check this first thing in the morning tomorrow

Thank you 🙏

@Bappa Barik I got a followup-question; Did you set some CAA records configured for your domain? If so, you might need to add Certainly as well, as this is certificate provider we use to generate Appwrite's custom domain certificates

I bought the domain from GoDaddy added the vercel nameservers there and added the cname from appwrite in the vercel dns record

Hmm I see. Vercel might be adding Cloudflare's CAA as that's what they use, and that causes Appwrite to not pass CAA requirement.

Please try to add CAA record:

This might need to be added for @, so this DNS response include it:

Is it possible both vercel and appwrite generating SSL causing the issue

Very possible, but as far as I can tell, there can be multiple CAA records. So this should still work, fingers crossed 🤞

Ok let me check 🤞

These are current records

@Meldiron Thank you 👍 it worked everything is working smoothly now thank you for the support 🙏

Glad to hear! 🙌 Ill be noting this down in our support runbook, to have quick solution for future. Also, Ill be looking into making this experience better - I am thinking of adding CAA record check, so Appwrite can complain verification failed, when adding the domain

hi there, i'm having similar issue as this

can someone help urgently

@Meldiron

please don't:

• post in someone else's old thread
• tag people
• create duplicate posts for the same topic

[SOLVED] Why the custom domain is not working