PostgreSQL Error & Bad Gateway

Checklist

• Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
  • Yes
• Are you sure you're not using someone else's docker image?
  • Yes
• Have you searched for similar issues (both open and closed)?
  • Yes

Describe the bug
When enabling PostgreSQL, the dashboard throws a Bad Gateway-error and the logs print the following:

[1/14/2025] [8:47:38 PM] [Global   ] › ✖  error     no pg_hba.conf entry for host "xx.xx.xx.xx", user "nginx_proxy_manager", database "nginx_proxy_manager", no encryption error: no pg_hba.conf entry for host "xx.xx.xx.xx", user "nginx_proxy_manager", database "nginx_proxy_manager", no encryption
    at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:283:98)
    at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:122:29)
    at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:35:38)
    at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:11:42)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:191:23) {
  length: 183,
  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: '535',
  routine: 'ClientAuthentication'
}

Nginx Proxy Manager Version
v2.12.2

To Reproduce
Steps to reproduce the behavior:

1. Go to log in screen
2. Login
3. See error.

Expected behavior
Connect to database and login to dashboard

Screenshots


PS. Stock compose file, also tried with the advanced vars in the compose file, but same issue.

Operating System
Debian 12

Additional context
My database is a managed one from Digital Ocean, I think the issue comes from the certificate.
This is how I normally connect to the database:
postgresql://project_name:password@xx.xx.com:25060/project_name?connection_limit=5&pool_timeout=360&connect_timeout=360

Start with the stock compose file and its advanced database variables, then reproduce the login-screen failure against the managed DigitalOcean PostgreSQL database. Compare the connection settings and certificate requirements with the reported pg_hba.conf error; done means the dashboard connects to PostgreSQL and login no longer returns Bad Gateway.