Arvish Doshi
03/24/2026, 11:45 AMrd1q5ixj7pe2anz4p.a2.typesense.net
We created a CNAME record for a custom domain: which maps to the above value.
However, when accessing the service via the custom domain, we get the following error:This is due to an SSL certificate mismatch, since the Typesense cluster presents a certificate fornet::ERR_CERT_COMMON_NAME_INVALID
*.typesense.net and not for our custom domain.
Is there a supported way in Typesense Cloud to configure a custom domain and provision the required SSL certificate?
Our goal is to avoid exposing the underlying search service / provider in our platform.Alan Martini
03/24/2026, 12:01 PMArvish Doshi
03/26/2026, 6:04 AM