Hey <@U076GF3T0HY> <@U08Q5JL9F5G> I wanted to disc...
# community-help
a
Hey @Fanis Tharropoulos @Alan Martini I wanted to discuss a concern regarding our Typesense setup. We've set up a cluster (HA with 3 nodes & SDN enabled) on Typesense Cloud. Cluster ID: rd1q5ixj7pe2anz4p Account: Redex And we're currently using the geo load-balanced endpoint:
rd1q5ixj7pe2anz4p.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:
net::ERR_CERT_COMMON_NAME_INVALID
This is due to an SSL certificate mismatch, since the Typesense cluster presents a certificate for
*.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.
a
Hey @Arvish Doshi A simple DNS CNAME will not work for this exact reason. You need to have a proxy in front, and then have that proxy forward requests to your Typesense Cloud hostnames. Plus if you're using an SDN that proxy should also be spread across geos (like a CDN), so that the Typesense geo-balanced hostname see the requests coming from different geo locations. Cloudflare has a way to set this up, which we describe here: [https://typesense.org/docs/guide/data-access-control.html#ddos-protection\ ](https://typesense.org/docs/guide/data-access-control.html#ddos-protectionThe)\ The section says "DDoS protection", but that's a side benefit you also get when using Cloudflare this way.
🙌 1
a
Thanks much @Alan Martini