Skip to content
Back

[SOLVED] Custom Domain TLS Certificate Not Applied — Still Getting Fastly Default Cert

  • 2
  • Resolved
  • 3
  • Cloud
Mazahir
13 May, 2025, 05:40

Added a custom domain, but gives me an error

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

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

Please Help

TL;DR
Custom domain TLS certificate not being applied due to conflicting CAA records with Fastly. Solution: either add correct CAA record for Fastly or remove conflicting records.
Mazahir
13 May, 2025, 05:41

I have tried to delete and re create multiple times. in console it says domain is verifed and certifcates are generated.

13 May, 2025, 15:15

whats your domain?

13 May, 2025, 16:05

api.ezmenu.store

13 May, 2025, 16:07

you have a CAA record on ezmenu.store, this only allows letsencrypt

13 May, 2025, 16:08

we use fastly with certainly.com as CAA, so you either need to add the record or delete all of them

15 May, 2025, 03:12

Thank you so much!! It works

15 May, 2025, 03:13

[SOLVED] Custom Domain TLS Certificate Not Applied — Still Getting Fastly Default Cert

16 Oct, 2025, 08:19

I have same issue sadly I can't even find any CAA record. I recently migrated to cloudflare and since then nothing works anymore, domain pending verification for weeks or even a month

Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more