(FIXED) “Can't be connected!” Supabase integration error

Help & Support 💻
,
1

I try connecting to my Supabase DB but I keep getting the error
“connect ENETUNREACH 2600:1f18:2e13:9d16:81… - Local (:::0)”

I used my connection string from Supabase to double check credentials and everything is accessible manually and through my n8n connections.

Anyways whenever I press “Test Connection” the same error pops up.

It’s worth to mention that if I remove “db.” from the host address I get the timeout error instead of instant fail.

image
image1114×773 38.1 KB

Thank you guys for any support

2

Hi @Esther_Souza,

ENETUNREACH could be caused either:

  • because no route to the network or host exists
  • because of status information returned by intermediate gateways or switching nodes
  • because no interface was found connected to a route that was found (at least according to a comment on stackoverflow)

From what I’ve read on stackoverflow and other forums, IPv6 can cause this kind of issue. Looking at the error message you shared and the fact that you are using Supabase’s direct connection string, I’m pretty confident this connection uses IPv6.

I saw you also posted almost the same question on retools forum. If you look at the image that MiguelOrtiz posted in a reply there, you can see that he is not using the direct connection string, but the Supavisor session mode.

Try setting up a connection with that and see if it works :+1:t3:

2 Likes
3

Hi @Esther_Souza and @Max,

Yes, this error is caused by IPv6. We’re working on implementation in the background.
Please use Session or Transaction Pooler, these types of connection work!

image
image1848×1548 289 KB

2 Likes
4

@spherebread @Max Thanks so much you guys, I’ll try out your suggestions.

It worked like magic using the transactional pooler

2 Likes