SSL certificate issue - unable to get local issuer certificate

We rotate our SSL certificates for Typesense Cloud annually as part of our standard operating procedure.We tested and deployed a new SSL cert for _new_ nodes on Typesense Cloud (provisioned either during new cluster creation or via config changes) at 3:30AM UTC on Jun 2, 2025.We also scheduled the new cert to be pushed live to existing nodes at 12:00AM UTC on Jun 3, 2025.

$12

We started getting sporadic reports of a few users running into SSL certificate issues when connecting to their Typesense Cloud clusters. On closer investigation, we found that they were trying to connect to Typesense from older operating systems or older runtimes that bundle their own root CAs (like Node.js), which hadn't updated their Root CA store recently. Updating their OS / runtime CA certificates, to the latest version fixed the issue for them.Our SSL provider started using a new Root CA certificate to sign our certificate this year, and this new root CA certificate wasn't available on older runtimes. So manually updating the root CA store on users' computers fixed the issue, so that the SSL cert presented by Typesense Cloud was able to be validated successfully.