Postgres connection error with self-hosted Braintrust

This error can occur with cloud service provider database services such as Azure Managed Postgres or it can occur with a customer-deployed Postgres instance.

Failed to run Clickhouse ETL loop
error: no pg_hba.conf entry for host "10.0.1.62", user "admin", database "postgres", no encryption
    at /braintrust/api-ts/local.js:348:12938
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async y0e (/braintrust/api-ts/local.js:1034:209)
    at async /braintrust/api-ts/local.js:1033:696     
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async y0e (/braintrust/api-ts/local.js:1034:209)
    at async /braintrust/api-ts/local.js:1033:696 {
  length: 158,
  severity: 'FATAL',
  code: '28000',
  detail: undefined,
  hint: undefined,
  position: undefined,
  internalPosition: undefined,
  internalQuery: undefined,
  where: undefined,
  schema: undefined,
  table: undefined,
  column: undefined,
  dataType: undefined,
  constraint: undefined,
  file: 'auth.c',
  line: '630',
  routine: 'ClientAuthentication'
}

This error is likely to be caused by a misconfigured Postgres URL, or possibly an SSL mismatch between the Braintrust side and the Postgres database. Ensure the Database connection URL is specified correctly.

Also, ensure that the sslmode parameter is configured correctly.

Check the Postgres pg_hba.conf to ensure that the client authentication configuration is correct when specifying the hosts that will be connecting to the database. Each pg_hba.conf record specifies a connection type, a client IP address range (if relevant for the connection type), a database name, a user name, and the authentication method to be used for connections matching these parameters.

Please review the Postgres Documentation for additional information on pg_hba.conf, which can be found here. https://www.postgresql.org/docs/current/auth-pg-hba-conf.html