OneLinersCommand workbench
Verified diagnostic signature

PostgreSQL transport succeeded but identity, database, or TLS expectations do not match.

Match output from postgresql, understand the likely cause, then continue with sourced, read-only checks.

Confidence
high
Platforms
linux · macos · windows
Verified
2026-07-24
Recognized output

Signature matched locally

database .* does not exist

OneLiners matches this pattern in your browser. Your pasted output is not stored or indexed.

Likely causes

What usually produces this signal

  1. Wrong role or database
  2. Credential mismatch
  3. TLS mode mismatch
  4. Connection string mismatch
Safe next checks

Collect evidence before changing the system

01

Check whether a TCP port accepts connections

nc -vz <host> <port>

The output matches the expected target and exits without an error.

02

Inspect a remote TLS certificate

openssl s_client -connect <host>:<port> -servername <host> </dev/null 2>/dev/null | openssl x509 -noout -subject -issuer -dates

The output matches the expected target and exits without an error.