On n8n Cloud 2.43.5, I am trying to connect the built-in Postgres credential to a Supabase session pooler with SSL set to Require and Ignore SSL Issues disabled. The credential has no custom CA field.
Is there a supported way on n8n Cloud to trust the Supabase CA while preserving both certificate-chain and hostname validation? If this requires a Cloud-side feature or support configuration, what is the supported route? I want to keep Ignore SSL Issues disabled.
What is the error message?
self-signed certificate in certificate chain
Information on your n8n setup
n8n version: 2.43.5
Hosting: n8n Cloud
Connection: built-in Postgres credential to Supabase session pooler
Hi @tommy_fu, the built-in Postgres credential in 2.43.5 has no custom CA input. The documented custom-CA setup requires mounting certificates into the n8n container, so it isn’t a configuration you can apply yourself on Cloud.
For an official Cloud-side answer, contact help@n8n.io and ask whether your managed instance can trust the Supabase CA while retaining both certificate-chain and hostname validation. Include your instance URL, n8n version, pooler hostname/port, error, and the public CA certificate downloaded from Supabase’s Database Settings.
Support would need to confirm whether that configuration is available. There isn’t a documented Cloud procedure I can point you to, and I wouldn’t promise that support can install it.
The PR adding Postgres certificate fields is still open and unmerged: