Supsabase SASL: SCRAM-SERVER-FINAL-MESSAGE: server signature is missing

Questions
1

Describe the problem/error/question

I am trying to connect to a Supabase Postgre database, but I cannot connect to it due to certificate error. How do I fix it?

What is the error message (if any)?

I consistently get the error SASL: SCRAM-SERVER-FINAL-MESSAGE: server signature is missing.

Please share your workflow

This is applicable to all workflows I try to create.

Information on your n8n setup

2

Hi,

I think this was a known error. Have you searched the forum?

first result

Maybe the ignore SSL errors will help.

Reg,
J.

3

I’ve searched the forums, and tried ignoring the SSL errors but without any results.

4

Do you have any special chars in the password?

Try changing it to a password with only upper/lowercase and numbers and try again.

Seems to be a new bug in n8n regarding this. Don’t know if it is only against the poolers or if it is also for direct database connection.

This has worked before, but sometime during the last updates it has changed, i guess n8n doesn’t do the percentage encoding correctly any more, since it is connected to special chars.

1 Like
5

hey thank you very much.

i’ve got the same issue and changing the database password without symbols/special chars is working for me

1 Like