Use this when a Postgres client successfully resolves Supabase's host (no more "host not found") but then fails with something like "self-signed certificate in certificate chain."
Steps
- Open the database connection settings in whatever client you're using.
- Find the SSL setting, set it to Allow (not Disable, not strict Require if that also fails).
- If there's a separate toggle like "Ignore SSL Issues (Insecure)", turn it on.
- Reconnect or retest.
Gotcha
The word "insecure" in that toggle sounds alarming, but the connection is still encrypted over SSL either way. What this actually relaxes is strict certificate chain validation, not encryption itself. For a personal project connecting to your own database, this is a standard, low-risk workaround for a known compatibility quirk between some Postgres clients and Supabase's pooler certificates, not a real security hole.
Quick reference
SSL: Allow
Ignore SSL Issues (Insecure): ON