-
-
Notifications
You must be signed in to change notification settings - Fork 222
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
❓ [immich] Does not connect to postgress 'FATAL: password authentication failed for user "postgres"' #1614
Comments
Hi, I have the same issue trying to get TeslaMate running. I have set the POSTGRES_PASSWORD in the configuration. Also tried setting the username but it didn't matter. 2024-10-26 13:25:30.119 CEST [299] FATAL: password authentication failed for user "postgres" |
Hi, I think that postgres's password can't be changed after running it once. You could try with the default password, |
At least for me, postgres is using the correct password. I confirmed this by connecting with my own client, which only works with the expected password |
I got it to work now by resetting the postgres addon and setting it up with the default password. If I do that, the immich addon is able to connect to postgres. |
I repeated the same process, now using a different password without special characters, this is working. The previous, unusable password contained the '!' and '%' characters. |
Yes! Resetting the add-on and using the default pw worked for me too. |
Thanks very much ! Perhaps it's an issue with characters escape. I'll look if I can do something. I think it's also due to how HA manages strings (with " and not ') |
The postgres addon is working. I can connect to it with the set password from a client.
immich can't connect to it, the password I set in the config is the same one that works in the client but it seems to not be used.
Already tried setting the password in config/addon_config/immich/config.yaml, but it makes no difference.
Log when starting immich:
(
<redacted>
is the actual password and jwt token I set)The text was updated successfully, but these errors were encountered: