server does not support SSL, but SSL was required / no pg_hba.conf entry … no encryption
The client and server disagree about SSL — the client requires it but the server doesn’t offer it, or the server requires it and the client didn’t use it.
server does not support SSL, but SSL was requiredno encryption Meaning
sslmode=require on a local server without SSL fails; managed databases (RDS, Azure, Supabase) often require SSL, rejecting non-SSL clients with “no encryption”.
Common causes
- sslmode=require against a server without SSL
- Managed DB requiring SSL while the client uses sslmode=disable
- Self-signed server cert with sslmode=verify-full
⚡ Quick fix
- Set sslmode=disable for local dev servers
- Use sslmode=require (and the provider CA for verify-full) for managed databases
Detailed fix by platform
PostgreSQL
postgres://app:pass@db.example.com:5432/app?sslmode=require
How to diagnose
- Client — sslmode?
- Server — ssl on / pg_hba hostssl?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in PostgreSQL
Other ways to find it
Where this error sits
Origin: Data. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 14 Oct 2026