Error SASL: SCRAM-SERVER-FINAL-MESSAGE: server signature is missing on Postgres Node

Questions
1

Hello n8n community!

I am encountering an issue when trying to configure my chatbot workflow that uses the Postgres Node to store and retrieve information from the database. Despite everything appearing to be correctly set up, I get the following error when the workflow reaches the Postgres node:

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

I have already configured the Postgres Node with the correct credentials, and I also chose the option to ignore SSL validation. However, the issue persists, and I cannot establish a connection between n8n and my database.

My Environment Setup

  1. n8n Version:

• Version: 1.72.0 (Self Hosted)

  1. Database:

• Database: Postgres

• Connection Method: SASL/SCRAM Authentication (username/password).

  1. Hosting Environment:

• Platform: [Render]

• Operating System: [macOS]

  1. Workflow Setup:

• The workflow includes an AI Agent Node that connects to a Postgres Node.

• The Postgres Node is supposed to retrieve or store data in the database.

Steps I’ve Tried

  1. Verified Postgres Credentials:

• Database name, username, password, and host are correct.

• I can connect to the database manually using external tools (e.g., DBeaver, psql).

  1. Checked SASL Configuration:

• The database is configured to use SASL with SCRAM authentication.

• Connections using these credentials work outside of n8n.

  1. Checked Postgres Server Logs:

• Reviewed the database server logs but didn’t find any apparent issues.

  1. Tested the Postgres Node in n8n:

• The Postgres Node is configured as follows:

• Host: [My Host]

• Port: 5432

• User: [My Username]

• Password: [My Password]

• Database: [My Database]

• Authentication is set to SASL/SCRAM

Questions and Desired Solutions

• What could be causing this specific error (server signature is missing) in the context of n8n?

• Is there anything I can adjust in my database setup or the Postgres Node in n8n to fix this?

• Are there additional settings required to use SASL/SCRAM authentication with the Postgres Node in n8n?

Any help would be greatly appreciated! I’ve tried multiple solutions, but I am still stuck with this issue.

Thanks in advance!

Lucas Viana

Screenshot 2024-12-29 at 12.05.30
Screenshot 2024-12-29 at 12.05.302306×1234 289 KB

2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

hi @LucasViana

welcome to the community! Sorry about the late response here. Have you been able to sort this out? Are you using postgres and n8n via docker? Are you able to set up a different type of authentication?