I had a working Supabase postgres node for over a year, but I accidentally wiped it thinking that I was setting up another connection I was testing (I used Edit instead of creating a new connection). When I realized it I tried to add my Supabase Transaction Pooler settings again but it fails. I copied my value settings from Supabase and even tried to reset my DB password several times, but now it doesn’t seem to work no matter which connection I try to use. My Transaction Pooler settings are:
Host = db..supabase.co
Database = postgres
User = postgres
Password =
Port = 6543
Ignore SSL Issues (Insecure) = disabled
I’ve tried everything and even reset my DB password many times. It was working perfectly before I wiped my settings. I’ve tried every solution that I’ve read on this forum and everywhere else on the web and nothing seems to be working. I even contacted Supabase support, but apparently this is an n8n issue. Any help or suggestions would be greatly appreciate.
What is the error message (if any)?
“Couldn’t connect with these settings” (when trying to save the node with my postgres settings)
Please share your workflow
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
Hi @mohamed3nan thanks for the reply and screen shots. I’m at a total loss. It was working until I wiped my settings on this node. I’ve tried every type of connection settings including what you provided. I was trying the PSQL settings (tried all 3) and you are showing URI settings. I’ve just tried those which include the ‘aws’ in the host and that also doesn’t work for me. The only difference I see is that your IPv4 compatible is showing with a green checkmark and mine is a red x. What I don’t understand is why it was working perfectly one moment and when I needed to recreate it now it doesn’t work. I have literally tried every type of setting. Should I pay the $4 per month for Supabase to turn on my IPv4 compatibility? I had no issues when I was on the free Supabase plan. Any other ideas?
I’m on the free plan, so my Transaction pooler is set to Shared Pooler,
From your screenshot, it looks like yours is set to Dedicated Pooler,
Not sure if that’s the issue, but hopefully someone with a paid plan can confirm and help..
Hi @mohamed3nan After trying every type of connection setting iteration, I created a new free Supabase account to try with that and it also failed. I then tried to connect via Python and it worked, which led me back to n8n being the source of the problem. I went with a hunch and checked my version of n8n and it was a version behind. I updated it to
1.116.2 and now my original Postgres Supabase connection works! (as well as the free one I created). So, it looks like something happened with the version of n8n that I was on. Just FYI
