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

Hi, I am trying to self host n8n using supabase as the postgresdb but i keep on getting this error

2024-09-26T00:40:59.843Z | info     | Initializing n8n process "{ file: 'start.js', function: 'init' }"
2024-09-26T00:41:00.395Z | debug    | Lazy Loading credentials and nodes from n8n-nodes-base "{\n  credentials: 362,\n  nodes: 460,\n  file: 'LoggerProxy.js',\n  function: 'exports.debug'\n}"
2024-09-26T00:41:00.476Z | debug    | Lazy Loading credentials and nodes from @n8n/n8n-nodes-langchain "{\n  credentials: 15,\n  nodes: 81,\n  file: 'LoggerProxy.js',\n  function: 'exports.debug'\n}"
2024-09-26T00:41:00.812Z | error    | Error: There was an error initializing DB "{ file: 'LoggerProxy.js', function: 'exports.error' }"
2024-09-26T00:41:00.814Z | error    | Error: SASL: SCRAM-SERVER-FINAL-MESSAGE: server signature is missing "{ file: 'LoggerProxy.js', function: 'exports.error' }"

Here is my compose file details.

volumes:
  traefik_data:
    external: true
  n8n_data:
    external: true

networks:
  traefik-public:
    external: true

services:
  n8n:
    image: docker.n8n.io/n8nio/n8n:${RELEASE:-latest}
    container_name: ${N8N_CONTAINER_NAME:-n8n}
    restart: always
    ports:
      - "127.0.0.1:5678:5678"
    labels:
      - traefik.enable=true
      - traefik.http.routers.n8n.rule=Host(`${SUBDOMAIN}.${DOMAIN_NAME}`)
      - traefik.http.routers.n8n.tls=true
      - traefik.http.routers.n8n.entrypoints=https
      - traefik.http.routers.n8n.tls.certresolver=le
      - traefik.http.middlewares.n8n.headers.SSLRedirect=true
      - traefik.http.middlewares.n8n.headers.STSSeconds=315360000
      - traefik.http.middlewares.n8n.headers.browserXSSFilter=true
      - traefik.http.middlewares.n8n.headers.contentTypeNosniff=true
      - traefik.http.middlewares.n8n.headers.forceSTSHeader=true
      - traefik.http.middlewares.n8n.headers.SSLHost=${DOMAIN_NAME}
      - traefik.http.middlewares.n8n.headers.STSIncludeSubdomains=true
      - traefik.http.middlewares.n8n.headers.STSPreload=true
      - traefik.http.routers.n8n.middlewares=n8n@docker
    environment:
      - N8N_HOST=${SUBDOMAIN}.${DOMAIN_NAME}
      - N8N_PORT=5678
      - N8N_PROTOCOL=https
      - NODE_ENV=production
      - WEBHOOK_URL=https://${SUBDOMAIN}.${DOMAIN_NAME}/
      - GENERIC_TIMEZONE=${GENERIC_TIMEZONE}
      - N8N_EMAIL_MODE=${N8N_EMAIL_MODE}
      - N8N_SMTP_HOST=${N8N_SMTP_HOST}
      - N8N_SMTP_PORT=${N8N_SMTP_PORT}
      - N8N_SMTP_USER=${N8N_SMTP_USER}
      - N8N_SMTP_PASS=${N8N_SMTP_PASS}
      - DB_TYPE=${DB_TYPE}
      - DB_POSTGRESDB_DATABASE=${DB_POSTGRESDB_DATABASE}
      - DB_POSTGRESDB_HOST=${DB_POSTGRESDB_HOST}
      - DB_POSTGRESDB_PORT=${DB_POSTGRESDB_PORT}
      - DB_POSTGRESDB_USER=${DB_POSTGRESDB_USER}
      - DB_POSTGRESDB_PASSWORD=${DB_POSTGRESDB_PASSWORD}
      - DB_POSTGRESDB_SCHEMA=${DB_POSTGRESDB_SCHEMA}
      - N8N_LOG_LEVEL=debug
      - DB_LOGGING_ENABLED=true
      - DB_LOGGING_OPTIONS=query,error,schema,warn
      - N8N_ENCRYPTION_KEY
      - N8N_USER_MANAGEMENT_JWT_SECRET
    volumes:
      - n8n_data:/home/node/.n8n
    networks:
      - traefik-public

Is there a special way to do this?

I am using

n8n version: 1.59.4
Database: Supabase

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:

Hey @Adrian_Guya,

Welcome to the community :raised_hands:

I have taken a quick look, It could be that Supabase is set to enforce SSL. The quick way to resolve this issue though is to toggle the Ignore SSL options setting, I did this a few minutes ago and it worked as expected so this should get it working for you.

sorry i have the same issue, i am learning, where is this option?

I just realised I replied to the wrong issue with the above but ignoring ssl issues may still apply.

It is worth noting that while we do support Postgres as a database we don’t officially support Supabase as a database for the application so it could be that there is a setting enabled that is causing issues.

I would recommend trying to connect to a normal Postgres database first that isn’t managed by supabase to see if that works.

The actual error message could be with the credentials as well after doing some research online.

I have it running on a normal postgres db however running it on supabase is till an issue. Where is the ignore ssl option you mentioned?

Hey @Adrian_Guya

The option I meant was in the node I replied to the wrong post, however we do have an option on this page to ignore ssl issues Supported databases and settings | n8n Docs

But… looking online it could be an issue with the credentials or the user, for now I would be tempted to stick to a standard Postgres database for the application as that is what we support.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.