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.
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.
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.
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