Supabase
Connect a Supabase Postgres database to Credible through the session pooler, and fix the common Supabase connection errors
Supabase runs PostgreSQL, so you add it in Credible as a PostgreSQL connection. Three of Supabase's defaults need changing for it to connect: use the session pooler instead of the direct host, add the project-ref suffix to the username, and pick the right TLS option.
Step 1: Use the Session Pooler
Supabase's dashboard offers several connection strings and shows Direct Connection first. Use the session pooler instead: the direct host is published only on IPv6, which Credible cannot reach.
In the Supabase dashboard, click Connect and open the Session pooler tab. You'll find these values there:
| Setting | Value |
|---|---|
| Host | aws-0-<region>.pooler.supabase.com |
| Port | 5432 |
| Database Name | postgres |
| Username | postgres.<project-ref> |
| Password | your database password |
The username needs the project-ref suffix: postgres.abcdefghijklmnop, not postgres. The pooler serves many projects and uses that suffix to route to yours, so a bare postgres fails authentication.
Supabase also offers a transaction pooler on port 6543. Prefer session mode on 5432: transaction mode does not support prepared statements or session-level state, which some queries rely on, and a Statement timeout may not apply through it.
Step 2: Choose Database TLS
Supabase signs its certificates with its own authority rather than a public one, so the default TLS check fails. Set Database TLS to Encrypt, skip certificate check. The connection stays encrypted. Only the certificate check is skipped.
If you use the connection string field instead, append ?sslmode=no-verify:
postgresql://postgres.<project-ref>:<password>@aws-0-<region>.pooler.supabase.com:5432/postgres?sslmode=no-verifyA connection string without sslmode is not encrypted at all.
To check the certificate as well, Supabase's authority has to be trusted on Credible's side. Contact support to set that up.
Step 3: Connect in Credible
- In the connection form, choose PostgreSQL
- Enter the session pooler values from Step 1
- Set Database TLS as in Step 2
- Click Test Connection, then Connect
The other fields, including Statement timeout, work as they do for any PostgreSQL connection.
Client Limits
The session pooler limits how many clients one project can have open at once, and the limit depends on your Supabase compute size. Credible opens up to 10 sessions per connection on each of its query servers, so a busy dashboard on a small project can hit that limit. If you see max clients reached, raise the pool size or compute size in Supabase.
Troubleshooting
| Problem | Cause | Fix |
|---|---|---|
connect ECONNREFUSED <ipv6 address> | You used the direct connection host, which is IPv6-only | Use the session pooler host from Step 1 |
password authentication failed | The username is missing the project-ref suffix | Use postgres.<project-ref> |
self signed certificate in certificate chain | The TLS option checks the certificate, and Supabase's authority is not a public one | Set Database TLS to Encrypt, skip certificate check, or append ?sslmode=no-verify to a connection string |
max clients reached | The session pooler is at its client limit | Raise the pool size or compute size in Supabase |
permission denied for schema ... | The role lacks read access | Grant the role USAGE on the schema and SELECT on the tables you want to model |