i need help ASAP pls
errors
Test connection failed: getaddrinfo ENOTFOUND db.exsarzogufvgvwpqwkoa.pooler.supabase.com self-signed certificate in certificate chainThe issue is that Supabase does not show the “Allowed IPs” section anywhere in Database → Settings, and I don’t see any place to enable IP allowlisting. Here is what Supabase gives me: Direct connection string: postgresql://postgres:[PASSWORD]@db.exsarzogufvgvwpqwkoa.supabase.co:5432/postgres Pooler connection string: postgresql://postgres.exsarzogufvgvwpqwkoa:[PASSWORD]@aws-1-sa-east-1.pooler.supabase.com:5432/postgres Retool tries to connect to: db.exsarzogufvgvwpqwkoa.pooler.supabase.com …but that host does not exist (DNS ENOTFOUND). Also, my project is on the Free/Nano tier in sa-east-1, and I’m not sure if IP allowlisting is available for this plan or region. My questions: Is it possible to connect Retool to a Supabase Free/Nano project in sa-east-1? Should the pooler hostname look different? Is IP allowlisting disabled on this plan/region? Thanks!
3 Replies
Your pooler name with Retool does not look correct.
Use the connection tab to get either the session (5432) or transaction (6345) pooler info. Those are .com and IPv4 compatible.
The .co 5432 address is IPv6 only.
There is no allow list.
yo i didnt get it LOL
can u help me??
like what to touch haha
im trynna export thiz to retool
I have no idea about Retool.
You show entering the string in the image (which is the pooler string and looks correct for host. See you connection tab for the corresponding user name for that (it has your instance id in it).
BUT you say Retool is trying to go to: db.exsarzogufvgvwpqwkoa.pooler.supabase.com I have no idea how Retool would go from the string you entered to one that looks sort of like the direct db connection but instead of .co you show it as .com.
The connection tab gives you a full URL AND values for each of the individual settings.
You probably can't use the .co one as retool does not support IPv6 according to this doc: https://supabase.com/docs/guides/troubleshooting/supabase--your-network-ipv4-and-ipv6-compatibility-cHe3BP#checking-ipv6-support
So you have to use the session pooler which is the one with aws and ends in .com.
