Hey @Gustavo_Galvan Welcome to the n8n community!
And yes, that’s Neon’s proxy, and your setup is already right. n8n connects to Neon’s proxy, not straight to Postgres, and that’s where TLS ends. pg_stat_ssl describes the backend’s own connection, which comes from the proxy over Neon’s internal network, so ssl = false there says nothing about the hop from n8n Cloud.
That hop is encrypted, because Neon rejects any connection that doesn’t use TLS. You can see it for yourself: switch the credential’s SSL to Disable and the connection test fails. And with Ignore SSL Issues off, n8n doesn’t touch certificate checking (it only turns it off when that toggle is on), so the TLS handshake verifies Neon’s certificate chain and that it matches your Neon hostname. If either check failed, the connection would be refused, so a successful test with your current settings is the verification.
Deepankar’s explanation matches what I’ve seen with Neon. If you want an independent check outside n8n, you can connect from your own machine with psql using full certificate verification:
If that connects, Neon’s certificate is valid for your hostname and trusted by a public CA, which is the same check n8n Cloud does with Ignore SSL Issues off. If it fails with a certificate error, that would be worth reporting.
One important distinction here: pg_stat_ssl reports the TLS state of the PostgreSQL backend connection, not necessarily the client-to-Neon-proxy connection. If Neon terminates TLS at its proxy, ssl = false on the backend session does not by itself prove that the external connection from n8n Cloud is unencrypted.
Your SSL: Require and Ignore SSL Issues: OFF settings are the right starting point. However, encryption and certificate verification are separate properties, so I wouldn’t treat the query result alone as proof that certificate validation is working.
To verify this more confidently, check the TLS behavior of the actual client-to-Neon endpoint and confirm that the client rejects an untrusted or invalid server certificate. Since this is n8n Cloud, you may need confirmation from n8n support about the exact certificate-validation behavior of its managed PostgreSQL credential.
I’d avoid changing to Ignore SSL Issues: ON just to make the connection work.
Haven’t tested this exact n8n Cloud and Neon combo, but I’d bet on the proxy. Neon’s proxy terminates TLS on its side and then talks to the actual Postgres compute separately, so pg_stat_ssl only shows the backend’s own hop, which can read ssl = false even when your connection from n8n is encrypted. Neon also refuses non-TLS connections as far as I know, so if yours works with SSL on, it’s encrypted on the way in.
For the cert check, with Ignore SSL Issues OFF the node should reject a cert that doesn’t chain to a trusted CA, so a working connection already says something. To see it yourself, run openssl s_client -starttls postgres -connect your-host:5432 from your machine and look at the chain and verify return code, or try psql with sslmode=verify-full. Neon’s connection docs cover that mode too. I can’t see n8n Cloud’s side from here though, so worth confirming that part in the n8n docs, maybe also a quick test with a wrong hostname to see if it fails like it should
Hi @Gustavo_Galvan, I tested the two-leg case using the released n8n 2.44.4 PostgreSQL transport, a local TLS proxy and PostgreSQL 16. Your exact query returned false/null/null while the client-to-proxy connection was encrypted.
With Require and Ignore SSL Issues OFF, that transport also rejected an untrusted certificate, a trusted certificate for the wrong hostname, and a server that declined TLS. Seven local checks passed, including rejection followed by a successful valid connection.
This tests that source version, not your managed Cloud instance. Keep Ignore SSL Issues OFF. Which n8n version is your Cloud instance running? I can compare its transport without any credentials or connection URL.