Hello all,
I've successfully updated to the latest version of Immich but I'm facing issues when I try to add healthchecks. It gives me authentication error, but I'm not changing any passwords. For testing purposes, I created a new VM with the same config but with empty database, everything worked as expect. I backup/restored my database and still gives me authentication problem. I've tried to change the password directly in database container and in the database itself, but still no luck. Any suggestions will be appreciated. Also, after the last update, I noticed that I was using old docker and docker compose. So I've upgraded everything to the latest version. After upgrading to the latest docker compose and using the provided docker compose file from the official website still authentication problem.
#Issues with database
1 messages · Page 1 of 1 (latest)
:wave: Hey @small solar,
Thanks for reaching out to us. Please follow the recommended actions below; this will help us be more effective in our support effort and leave more time for building Immich
.
References
- Container Logs:
docker compose logsdocs - Container Status:
docker compose psdocs - Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
Checklist
- :ballot_box_with_check: I have verified I'm on the latest release(note that mobile app releases may take some time).
- :ballot_box_with_check: I have read applicable release notes.
- :ballot_box_with_check: I have reviewed the FAQs for known issues.
- :ballot_box_with_check: I have reviewed Github for known issues.
- :ballot_box_with_check: I have tried accessing Immich via local ip (without a custom reverse proxy).
- :ballot_box_with_check: I have uploaded the relevant logs, docker compose, and .env files using the buttons below or the
/uploadcommand. - :ballot_box_with_check: I have tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
If this ticket can be closed you can use the /close command, and re-open it later if needed.
@small solar uploaded
@small solar uploaded
@small solar uploaded
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
Did you remove the DB_PASSWORD from the env file to hide it, or is it actually empty?
I've tried to change the password directly in database container and in the database itself
Can you post the commands you used and the output they printed?
I can't find the output, but the command I used was the following one:
ALTER USER postgres WITH PASSWORD 'new_password';