Our Postgres credential connects to Supabase’s session pooler on port 5432. With SSL Require and certificate validation enabled, it fails with “self-signed certificate in certificate chain.” How can we configure the trusted CA on n8n Cloud without disabling certificate verification?
Hey @James_K, while you wait for a response, here are some things that might help:
Suggested resources
Automatically matched to your question.
Docs:
Forum:
@A_A4, @barn4k, @tamy.santos - you’ve helped with similar issues before, can you take a look?
Automatically suggested by n8n’s community bot. It’s a pilot - please share feedback here.
Hi @James_K Welcome!
Not possible on Cloud today. The Postgres credential has no CA field, its SSL setting offers only Allow, Disable and Require, and n8n’s custom certificate authority mechanism lives in the self-hosting configuration, so there is nowhere on Cloud to put Supabase’s root CA. n8n has carried this internally as GHC-966 since February 2025, and the only answer on the issue was to turn on Ignore SSL Issues, which leaves the connection encrypted but stops n8n checking who is on the other end.
If verified TLS is a requirement rather than a preference, reach Supabase over its REST API with the Supabase node or an HTTP Request node, which is HTTPS against a publicly trusted certificate, so verification stays on and there is no CA to install. If your queries need real SQL rather than what the REST API exposes, the CA route only opens up self-hosted.
Thank you, much appreciated
Please consider marking it as a solution. 