Connection error with Postgres Chat Memory. ENETUNREACH

Describe the problem/error/question

I’m trying to set up a Supabase RAG AI Agent workflow but getting a connection error when trying to connect Postgres Chat memory in n8n.

What is the error message (if any)?

connect ENETUNREACH 2406:da18:243:7404:d3ad:7e29:9747:59a9:5432 - Local (:::0)

Please share your workflow

Information on your n8n setup

  • n8n version: 1.76.1
  • Database: Supabase Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
  • Operating system: Windows

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:

can you DM me the hostname for the postgres server? I think this might be a DNS issue.

Somehow I’m not able to send DMs :frowning_face:

Here’s the hostname:
db.duzhrrqdsxgiuubrekfh.supabase.co

That domain resolves to 2406:da18:243:7404:d3ad:7e29:9747:59a9, which is not reachable from my personal computer or from my n8n cloud instance.
I’m not familiar enough with supabase, but this sounds like a network configuration issue.
Maybe this helps.

1 Like

Howdy,

Had this issue myself today, the issue (I think) is that Supabase’s base connection doesn’t support ipv4 which is what n8n uses to send the connection request.

If you choose the Supabase option below that one for the Transaction Pooler, it works fine.

2 Likes

Man I love internet, had this issue today and found this ongoing discussion.

I can confirm using transaction pooler works fine

2 Likes

Yess! thank you!

n8n does support IPv6 as well. so this is still a bug IMO. Not sure if the bug is in n8n , or in supabase, considering that I can’t connect to this IP from any of my machines.

1 Like

Worth noting that using the Supabase node for vector storage works fine. This seems to be a problem only when using the Postgres node but connecting to the n8n host