need help setting up supabase credentials in n8n.
I'm having a real hard time getting suprabase set up in my n8n node. I am not self-hosting. the basic parameters are
Host: db.rlwttcwqozzqapdpuvyd.supabase.co
Database: postgres
User: postgres
Port: 5432
Password: [copied from database password reset link]
I'm getting an error code: connect ENETUNREACH 2600:1f18:2e13:9d0b:5e58:a74e:2eaa:5594:5432 - Local (:::0)
33 Replies
You need to use the IPv4 supavisor port.
So I understand that I need to change the port from 5432 to another port. Where do I find that port?
No
It is still 5432
You need to use the supavisor 5432 port and not the direct port which is IPv6 only. 99% sure n8n does not support IPv6.
See your connection tab at top of dashboard.
Direct connections to the database only work if your client is able to resolve IPv6 addresses. Enabling the dedicated IPv4 add-on allows you to directly connect to your database via a IPv4 address.
If you are connecting via the Supavisor connection pooler, you do not need this add-on as our pooler resolves to IPv4 addresses. You can check your connection info in your project database settings.
So it means I need to implement a connection pooler?
No. Use the session mode.
It goes thru the pooler but does not do pooling. It just gives you IPv4 access.
And I can't confirm n8n is ipv4 only in a quick search so I could be thinking of another platform.
reading the documentation ...
The other common issue is the password has special characters. If the "client" side does not url encode them then that will cause the type of error you see also.
changed the host to: aws-0-us-east-1.pooler.supabase.com
still fails.
The user name also changes to instanceid.postgres
Does you DB password have special characters?
yes, i changed the user name and the db password is the one that is automatically generated.
now i get error: SASL: SCRAM-SERVER-FINAL-MESSAGE: server signature is missing
I don't know if the auto password has special chars or not. I always enter my own.
password has no special characters
check that setting.
a lot of people on n8n are using suprabase for postgres so it can't be so hard.
read that. maybe i should try another postgres solution or any other solution at all. i'm only storing email addresses and usage statistics.
Did you toggle off ssl?
yes, it changed nothing. same error message.
I assume your password is not in []. I've seen that happen.
here's a youtube video where a guy is demonstrating rag on n8n using suprabase. at 5 min 51 sec he is showing the credentials set up for suprabase and you can see his host settings are aws so he's probably pooling.
Cole Medin
YouTube
This RAG AI Agent with n8n + Supabase is the Real Deal
Artificial Intelligence is no doubt the future of not just software development but the whole world. And I'm on a mission to master it - focusing first on mastering AI Agents.
In this video I show how to implement an AI Agent with RAG using n8n and Supabase for the chat memory and vector DB. This AI Agent is the REAL deal - something you could ...
but he says nothing about the IPv4 issue
There are two ports in his screen
One is the transaction (real pooler port).
with 6543
Then there is another connection below that.
Never mind on 2nd connection. He is using the real pooler port with 6543.
the n8n help thread you sent they talk about how supabase is not officially supported but they don't talk about what is officially supported and the thread is three months old.
Sorry. I know nothing about n8n and just going thru the typical connection issues people have with the DB.
The video IS using 6543 not 5432.
With the "AWS" IPv4 connection.
i tried 6543 and nothing changes.
With the supavisor aws-xxxxx port?
If so I've got nothing for you. You have tried the 3 basic combinations and dealt with ssl.
yes, with both hosts.
i got neon to come up right away.
There a few n8n posts here and at quick glance did not see errors connecting, but I they seem to be using the REST interface as described in this N8N doc.
Also having this same exact problem. The transanction pooler suddenly stopped working such that I paid to go pro with the $4 top up for direct ipv4. Direct connection also doesn't want to connect on both cloud and self-hosted n8n
Was anyone able to solve?
