❗️PostgreSQL Node – "Server does not support SSL connections" in New UI (Connection String and ssl=false ignored)

Questions
1

Hi everyone,

I’m currently facing a persistent issue with the PostgreSQL node in the latest n8n UI and hoping someone from the community has encountered (and maybe solved) this before.

:jigsaw: Goal

I want to connect n8n to a local PostgreSQL instance (running on TrueNAS SCALE, port 5432), without using SSL, since the server does not support it.

:hammer_and_wrench: Setup

  • n8n version: latest (modern UI with dark theme & new credential handling)
  • Database: PostgreSQL 15/17 via TrueNAS App (localhost, SSL disabled)
  • pgAdmin connects fine (SSL disabled)
  • Port 5432 is open, authentication via user ollama_ai & DB ollama_memory

:x: The Problem

When testing a basic query like SELECT * FROM memory LIMIT 1; in the PostgreSQL node, I consistently get the following error:

“The server does not support SSL connections”

:white_check_mark: What I’ve Tried (with no success)

I’ve spent hours debugging this (including with ChatGPT) and here’s what I’ve already attempted:

1. Standard Credential Setup

  • Host: 192.168.200.162
  • Port: 5432
  • User/password + correct DB name
  • Result: :x: “The server does not support SSL connections”

2. “Ignore SSL Issues” toggle

  • Enabled via toggle and {{ true }} expression
  • :x: No effect

3. Connection String

bash

KopierenBearbeiten

postgresql://ollama_ai:[email protected]:5432/ollama_memory?sslmode=disable
  • Tried adding it as the only field in the credential UI
  • :x: n8n doesn’t appear to respect this string properly, no change in behavior

4. Node Options → “Add Option” → Query Parameters

  • No way to define key/value pairs like ssl=false
  • Query Parameter field only accepts values (value1,value2,...)
  • :x: ineffective for disabling SSL

5. TrueNAS App Environment Variable

env

KopierenBearbeiten

DB_POSTGRESDB_SSL_REJECT_UNAUTHORIZED=false
  • Set in container, confirmed restart
  • :x: No impact on n8n’s PostgreSQL connection attempt

:test_tube: Observations

  • The new UI seems to have removed fine-grained configuration options from the PostgreSQL node – especially critical ones like ssl: false
  • There is no “Additional Fields” section or custom connection options like in earlier versions
  • Other nodes (e.g., MySQL) allow better connection customization

:question:What I’m Asking

  1. Has anyone found a working way to disable SSL for the PostgreSQL node using the latest n8n UI?
  2. Is there a way to inject custom connection properties like ssl=false, rejectUnauthorized: false, etc.?
  3. Is a working connection string approach still supported somehow?
  4. Does this require a custom patch / community node / environment override?

:bulb: Context

We are building a memory system for a local AI agent using n8n + PostgreSQL. It’s hosted on TrueNAS SCALE, so we cannot use kubectl or container exec – everything must be managed via the TrueNAS GUI and app config.

The setup is functional except for this SSL limitation, which breaks PostgreSQL node connectivity.

Thanks in advance for any advice, experience, or workaround!
Benjamin (bk9tv)

2

Screenshot
Screenshot1844×1240 110 KB

When you make the credential in n8n, can’t u specify here?

3

image
image1158×735 24 KB

Thanks for your help in advance!

1 Like
4

can u try access postgress from the n8n container, in terminal, see if u get same error, it seems maybe the truenas config maybe requires SSL? maybe (not used truenas that much)

I see u said u can access via pgadmin, but be good to confirm from the n8n container, maybe a network issue,

did u manage to fix it? yet or?

Hope all is going well.
Have u tried to enable sll on truenas and use in n8n?