Skip to content

[Bug]: PostgreSQL Database POSTGRES_HOST_AUTH_METHOD Not Being Set Through Configuration Page #5914

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
takayumi opened this issue May 29, 2025 · 0 comments
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization.

Comments

@takayumi
Copy link

takayumi commented May 29, 2025

Error Message and Logs

The Bug

I was trying to change the POSTGRES_HOST_AUTH_METHOD via the Coolify GUI, but it never seems to reflect in the actual container configuration.

The /var/lib/postgresql/data/pg_hba.conf file will always be the default scram-sha-256, as per the postgres image environment variable options, instead of the one we set in the Configuration > Host Auth Method input field within Coolify.

The last line will always be this.

host all all all scram-sha-256

Expected Result

It should match the value we set in step (2) of the "Steps to Reproduce" section like so:

host all all all password

Steps to Reproduce

  1. Create a new PostgreSQL database.
  2. Set the Host Auth Method to password or md5
  3. Go to the Terminal tab and do cat /var/lib/postgresql/data/pg_hba.conf

Example Repository URL

No response

Coolify Version

v4.0.0-beta.418

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Debian GNU/Linux 12 (bookworm)

Additional Information

Workaround

  1. Go into the container (like via the Terminal GUI in Coolify)
  2. Edit the file yourself with this command vi /var/lib/postgresql/data/pg_hba.conf

Are you willing to work on this?

I can spend some of my time to fix it. Not sure which part of the codebase I should start looking at though. I'd greatly appreciate it so that I can fix it.

It's possible that the other configuration settings do not properly reflect on the actual container as well, so this is a bit concerning.

@takayumi takayumi added 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels May 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization.
Projects
None yet
Development

No branches or pull requests

1 participant