I am following the tutorial provided by Retool on YouTube (https://www.youtube.com/watch?v=AgB2-CSrnoI)
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 insert 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.
Hi @Esther_SZ,
Would you mind sharing a screenshot of your set up to try and troubleshoot?
Experiencing the same issue as well.
ENETUNREACH 2600:1f1c:f9:4d0b:ac65:e3d5:7703:7ea7:5432 - Local (:::0
I am also experiencing this issue.
Test connection failed connect ENETUNREACH 2600:1f18:2e13:9d03:7d56:4bf9:414:26c8:5432 - Local (:::0)
I added the Retool IP addresses per this Supabase Doc.
Hey everyone! Thanks for sharing your reports. We're looking into this now. Can you share screenshots of your resource setup?
Hey there!
Thanks for reaching out. Would you mind sharing screenshots of how your resource is setup? I found this error appear when the Database password is incorrect. The password comes from the password you set up when you made the initial database.
Let me know if you have questions.
Hey everyone!
I resolved this issue using the 'Transaction pooler' and SSL Configuration setup in Supabase. You'll need to add the CA certificate into the Retool configuration from Supabase shown in the screenshot attached. Use SSL/TLS, and then insert your certificate. This solves the error message : connect ENETUNREACH 2600:1f18:2e13:9d16:81... - Local (:::0)
Hope this helps!
Hello all. I am having the same error when trying to connect to my Supabase database. Tried adding the CA cert, the transaction pooler and forcing SSL in the Supabase settings but still no luck. Any thoughts on what is going wrong here?
connect ENETUNREACH 2600:1f1c:f9:4d02:6f49:8d72:c78a:4abc:5432 - Local (:::0)
Welcome to the community, @workspace! Thanks for reaching out.
Have you tried using the Session pooler connection, instead?
Let us know if you still need assistance, @workspace! If none of the above suggestions are working for you, it might be helpful to learn more about your setup. Are you on a Cloud or self-hosted instance, for example?
