You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Changing passwords in the .env file produces failure to authenticate with postgres user #344
I have been trying to change passwords in the production server with the help of the .env file.
Though there is a problem in the backend due to a failure to authenticate with the postgres user after changing the database password.
psql: FATAL: password authentication failed for user "postgres"
FATAL: password authentication failed for user "postgres"
Isn't that all I am supposed to do to change passwords ?
I ran into the same issue after modifying the default password for PG, deleting the db volume manually and rerunning docker compose watch resolved the issue.
Hello ! I got the same problem and for me it was due to the volume creation of docker you can check that with :
docker volume ls
I'm not an expert in Docker but I think if you change the password in the .env it does not create a new volume or use the old one to connect with your new password and that will obviously not work.
From this constatation you have 2 solution the first one is more or less "brutforce" and it worked for me the second one is maybe more smart but i didn't test it:
1. Delete the old volume and build the image again with docker-compose
docker volume rm <old_db_volume_id>
or to delete every single volume
docker volume rm $(docker volume ls)
then build your project image again
docker-compose up -d
2. Access to the pg admin or directly form the shell (with docker commands) to access to your db_user and change the password (I didn't test is with docker but I've already done this on a running server I don't remember the commands tho)
Hope this will help you :) Do not hesitate to correct me or complete my answer
Activity
emirakdere commentedon Sep 17, 2024
Just upvoting that I ran into the same issue today, I think even a simple clarification on the readme would be a nice patch as a troubleshooting step.
👷 Run tests using Python env, setup with uv, and add tests to check D…
bironeaj commentedon Jan 23, 2025
We ran into the same issue.
sfxgg commentedon Mar 23, 2025
I ran into the same issue after modifying the default password for PG, deleting the db volume manually and rerunning
docker compose watchresolved the issue.