Skip to content
GitHub
Get started →

Database connection errors

Connection errors show up two places:

  1. Dashboard → Site → Test connection — red error banner
  2. Live voice sessions — AI tells the user “I can’t look that up right now”

Errors are surfaced from the adapter’s testConnection() / search() methods. They come back as plain text, so the exact message depends on the backend.

Universal causes

CauseWhat to check
Wrong credentialsUser, password, key — copy-paste again, check for whitespace
Wrong database/collection nameCase-sensitive; Usersusers
Firewall / IP allowlistOur egress IPs at spelo.ai/security/ips
TLS misconfigurationServer requires TLS, you set ssl: false (or vice versa)
Network outageTry connecting from your laptop with the same credentials — does it work?
PermissionsThe user exists but doesn’t have SELECT on the tables you listed

By adapter

ErrorFix
password authentication failed for user XWrong password, or user doesn’t exist
connection refusedFirewall blocking our IPs, or DB not listening on the port
permission denied for relation XGRANT SELECT ON TABLE X TO spelo_readonly;
relation "X" does not existWrong source in collection config (case-sensitive)
SSL connection requiredSet ssl: true in config
self signed certificateExpected — set ssl: true (we pass rejectUnauthorized: false)

See Postgres adapter.

Reading the actual error

Dashboard → Site → DataTest connection → scroll to the error banner. The raw adapter error is shown (truncated to 500 chars). Click Show full to expand.

For production errors during live sessions, check Dashboard → AnalyticsQuery log — failures are logged with the adapter’s error message.

Still stuck?

Email support@spelo.ai with:

  • The exact error text (copy-paste, not paraphrase)
  • Your adapter type (postgres, mysql, etc.)
  • Your collection config (redact credentials!)
  • Whether curl / psql / mongosh with the same credentials works from your laptop