When setting  up Immich following this guide and this guide. I get an error when I start Immich:

 

[Nest] 602  - 07/21/2023, 2:20:12 PM   ERROR [TypeOrmModule] Unable to connect to the database. Retrying (6)...
error: password authentication failed for user "postgres"
    at Parser.parseErrorMessage (/app/immich/server/node_modules/pg-protocol/dist/parser.js:287:98)
    at Parser.handlePacket (/app/immich/server/node_modules/pg-protocol/dist/parser.js:126:29)
    at Parser.parse (/app/immich/server/node_modules/pg-protocol/dist/parser.js:39:38)
    at Socket.<anonymous> (/app/immich/server/node_modules/pg-protocol/dist/index.js:11:42)
    at Socket.emit (node:events:514:28)
    at addChunk (node:internal/streams/readable:324:12)
    at readableAddChunk (node:internal/streams/readable:297:9)
    at Readable.push (node:internal/streams/readable:234:10)
    at TCP.onStreamRead (node:internal/stream_base_commons:190:23)

 

My Immich setup  has this

 

postgres has this:

 

I have verified the passwords are the same. Not sure where the error is.

 

Any help would be greatly appreciated.

 

 

Did you run the postgres container before setting the user and password how you wanted them? These are only used on the very first run, changing them later won't do anything. 

Edited July 21, 20232 yr by Kilrah

Yes, I setup redis and postgres prior to. I have removed all three, set them up in redis->postgres->immich order and still have the issue. I can try again though.

Removing the container doesn't change anything, it's the appdata folder for it you need to remove. Stop container, delete this container's appdata folder, start it again - then you should have what you set in the template.

Kilrah, just so I understand, your saying stop all three containers, remove them, delete their appdata files, then reload all three and start over again? or I only need to do that for the Immich docker?

If you have problems logging into the database, only for the database container.

using Krusader, cannot delete the postgres appdata folder

Did you stop that container? Also Dynamix File Manager plugin i.e. file manager built into unraid may be preferable.

Edited July 21, 20232 yr by Kilrah

that appears to have worked

Thanks for all the help

Edited July 21, 20232 yr by crusemm

thanks for this thread! i also had the same problem

 

i completely removed postgres14 and its appdata, and set it up correctly

 

now immich is loading properly

On 10/13/2023 at 10:48 PM, ShadowVlican said:

thanks for this thread! i also had the same problem

 

i completely removed postgres14 and its appdata, and set it up correctly

 

now immich is loading properly

Have you lose all the data on the database ?

That's what I am worry now.

 

I updated Immich and it started doing connection problem. But I don't want to lose the data either...

On 21.7.2023 at 22:01, Kilrah said:

Das Entfernen des Containers ändert nichts. Sie müssen lediglich den zugehörigen Appdata-Ordner entfernen. Stoppen Sie den Container, löschen Sie den Appdata-Ordner des Containers und starten Sie ihn erneut. Anschließend sollten Sie die in der Vorlage festgelegten Einstellungen erhalten.

Thanks, I had the same problem now DBeaver connects (postgrestql 17)

On 12/20/2023 at 8:09 PM, Watever said:

Have you lose all the data on the database ?

That's what I am worry now.

 

I updated Immich and it started doing connection problem. But I don't want to lose the data either...

I had the same problem and found this thread in a search. For others who are showing up well after like me, I wanted to make sure there's a clear answer that yes, your Immich data (user accounts, albums, etc.) will be lost. If you're okay with this, go for it. If not, then you can reset your Postgres password with these steps:

1. In the Unraid web UI, open the Docker tab.
2. Click on the Postgres container and select "Console" to open a shell inside the container.
3. Enter

   psql -U postgres

   This will take you to a postgres prompt

4. Enter

   \password postgres

   You will be prompted to enter a new password and confirm it. This updates the password for the postgres superuser account, by the way.

Make sure you update (if needed) your Immich container postgres password variable to match.

 

Troubleshooting:

If you can't complete the above steps because step 3 is asking for authentication, check your pg_hba.conf file (found in your appdata/postgres.. folder). After making a copy of this file for safety, edit the file to replace `md5` with 'trust' (no quotes). This will allow passwordless login for the above steps. Restart postgres and give the above steps another go.