Troubleshoot connection errors

Classify the failure

• Name resolution: the hostname does not resolve.
• Timeout or refused: network path, firewall, service state, or wrong port.
• TLS error: client trust or SSL configuration.
• Password authentication failed: wrong, expired, or rotated credential.
• Database does not exist: wrong database name or project.
• Too many connections: pool sizing or leaked clients.

Run safe checks

# DNS
nslookup db.renviq.com

# PostgreSQL readiness with the exact URL
pg_isready -d "$DATABASE_URL"

# Authenticated check
psql "$DATABASE_URL" -c "select current_database(), current_user, now();"

Compare environments

If a laptop connects but production does not, compare outbound firewall rules, DNS, CA certificates, environment-variable loading, and URL encoding. If neither connects, inspect the Renviq database status, current incidents, and credential lifecycle.

Escalate safely

Open a support request with the database name, region, time range, client library and version, and redacted error. Do not include the password or complete connection URL.