This message was deleted.
# community-help
s
This message was deleted.
k
Is this cluster on Typesense Cloud or you self host it?
j
It's on Typesense Cloud (sorry, I should have say it)
f
This seems like an SSL error. Are all requests coming from the browser resolving? Is it throwing only when querying from your GCloud instance?
k
Please share the cluster ID, we can check.
j
I sent you in private message my cluster ID, thank you
k
Thanks, checking
j
All requests from browser seems to resolve yes, it's only throwing from Gcloud instance
k
I think your gcloud instance's local certificate chain might be old and may not support a newer SSL cert that Typesense server uses. To fix it, please run:
Copy code
sudo apt update && sudo apt install ca-certificates
f
There's also a guide for updating CA certs that I found from a Google search: https://cloud.google.com/certificate-authority-service/docs/updating-certificate-authorities#console
j
Thank you very much for your answers, I will try those solutions and will keep you informed.
👍 1
So, I tried to update our image build with your command
sudo apt update && sudo apt install ca-certificates
but I still had the error. Sorry, I didn't tried your solution about Updating Certificate Authorities with Google, since I was able to reproduce the error in local (from our back-end API). I think it may be because of our node version (we are still using node 16), so as a temporary fix, i had disabled the tls check. Thank you very much for your help !
👍 2
j
To add more context to this: we rotate our SSL certs annually (as required by SSL cert providers). It looks like the most recent set of certificates they issued us, use a newer Root Certificate Authority called "Sectigo Public Server Authentication Root R46". This Root CA needs to be in your OS' or platform's certificate store for the SSL connection to be successfully established. So updating your OS and/or runtime platform (like Node.js which bundles it's own root CA store) is the solution to this, to fetch the latest root certs. With Node.js specifically, instead of skipping SSL verification, there's an option to ask node to use the OS cert store: https://stackoverflow.com/a/67618741
Oh although looks like that
--use-system-ca
option in Node.js wasn't added until recent Node versions, but that SO thread discusses other options
j
Thank you for this additional information 🙏
👍 1
j
Quick update: we received more reports about this new SSL root CA cert not being recognized on older runtimes. So we've decided to roll back to the previous cert for now. If you run into this issue, if you do a rolling restart that should resolve it. Alternatively, the certs should be rolled back in the next 24 hours automatically as well.