Hello n8n community,
I’m experiencing an issue when trying to connect my PostgreSQL database hosted on Supabase, using the Connection Pooling (port 6543) and
scram-sha-256
authentication.The error I receive is:
**SASL: SCRAM-SERVER-FINAL-MESSAGE: server signature is missing**
Additional details:
- i´m connecting with (on port 6543).
- The authentication method on Supabase is confirmed to be
scram-sha-256
, as shown by runningSHOW password_encryption;
.- I’m using n8n Cloud, version 1.84.3.
It seems that the PostgreSQL client used in n8n Cloud may not be handling SCRAM authentication properly.
Could you please help me troubleshoot this issue? Is there a way to explicitly support
scram-sha-256
in the PostgreSQL node or use an alternative authentication method that works with Supabase?Thank you!!!
Hi,
You should set “Ignore SSL errors
”
as mentioned here : Error: SASL: SCRAM-SERVER-FINAL-MESSAGE: server signature is missing - #2 by n8n
Hi @jcuypers .
Tks for your answer !
I´m starting now with automation in n8n. where i do this? in supabase or in n8n?
I’m adapting and discovering the workspace! is in
thanks
Hi, the setting is a toggle on the postgres credentials used in the postgres node in n8n
Regards,
J.
I am running into the same problem. Did you find the root cause?