Container "api" failing to connect to DB with pg_hba.conf error after migration

[sharpdima]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Content

Hi Dify Team, I'm trying to run Dify via Docker Compose on a new machine. The api container is constantly throwing an OperationalError: FATAL: no pg_hba.conf entry for host "172.18.0.x".

I noticed that in the latest version, the docker-compose.yaml is auto-generated and the DB configuration has changed. Even after running docker-compose down -v, the connection is still being refused by the Postgres container.

Could you please advise on the correct way to reset the DB permissions or if there's a specific environment variable in the new template to allow these internal connections?

Thank you!

[dosubot[bot]]

The error means Postgres is rejecting connections from your Docker network IP because pg_hba.conf doesn't allow it. The latest Dify docker-compose.yaml doesn't provide an environment variable or built-in config for this—you need to manually update pg_hba.conf to permit connections from your Docker subnet (like 172.18.0.0/16).

Here's how you can fix it:

1. Find the pg_hba.conf file in your Postgres data volume (usually ./volumes/db/data/pg_hba.conf or ./volumes/db/data/pgdata/pg_hba.conf).
2. Add a line like:

   host    all    all    172.18.0.0/16    md5
   

3. Restart the Postgres container (and any dependent containers) to apply the change.

This will persist across restarts since the data directory is mounted as a Docker volume. There’s currently no automated way to do this in Dify’s compose setup, so you’ll need to repeat if you reset volumes or migrate again. For future-proofing, consider mounting a custom pg_hba.conf or using an init script if you rebuild often.

References:

• Manual pg_hba.conf update and restart fixes the issue
• No environment variable for pg_hba.conf in compose
• General solution discussion

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}