Can’t connect to Postgres with SSL on n8n Cloud

Questions
1

When I set “Require SSL” in the n8n Cloud Postgres node (Settings) to connect to Supabase using the Transaction Pooler params, the connection fails with: “self-signed certificate in certificate chain.”

It works if SSL is disabled, and it also works if I toggle “Ignore SSL Issues (Insecure).” I need SSL enforced without ignoring errors.

How do I enable SSL without the self-signed certificate error?

Information on your n8n setup

  • **n8n version: latest

  • **Database (default: SQLite): Postgres / Supabase cloud

  • **n8n EXECUTIONS_PROCESS setting (default: own, main): default

  • **Running n8n via (Docker, npm, n8n cloud, desktop app): cloud

  • **Operating system: macOS

1 Like
2

You would need to configure your Postgres with a certificate that isn’t self-signed.
If by postgres you mean Supabase (since you mentioned it on the bottom) - you can’t. In short - because you cannot upload your own certificates to supabase, you can only download their self-signed one, and you also cannot configured trusted CA certificate in the node to trust that self-signed certificate.

3

So does this really mean there is no secure way to connect a supabase postgres DB to n8n cloud?

4

Any new leads on this?