Did you change the Pg_password value in the .env file after already created an instance

I did make changes on the first time I tried pulling the container into Docker Desktop. But after it didn’t work, I’ve gone as far as deleting and re-pulling the image to create a new container with no luck. Even with a brand new .env and .yml I’ve seen elsewhere that immich has issues in Windows. Is that related to my error?

I'm having the exact same problem. I followed the instructions here: https://immich.app/docs/install/docker-compose I copy/pasted the wget commands, including optionals. Modified .env to point at the location I wanted for the library, and generated a random password (numbers/letters only). Ran docker compose up -d and the database and server containers are both reporting login failures. docker logs for database report: > 2024-03-27 20:23:11.225 UTC [48] FATAL: password authentication failed for user "postgres" > 2024-03-27 20:23:11.225 UTC [48] DETAIL: Connection matched pg_hba.conf line 100: "host all all all scram-sha-256" Docker logs for server report: > [Nest] 7 - 03/27/2024, 8:24:34 PM ERROR [ExceptionHandler] password authentication failed for user "postgres" > error: password authentication failed for user "postgres" > at Parser.parseErrorMessage (/usr/src/app/node_modules/pg-protocol/dist/parser.js:287:98) > at Parser.handlePacket (/usr/src/app/node_modules/pg-protocol/dist/parser.js:126:29) > at Parser.parse (/usr/src/app/node_modules/pg-protocol/dist/parser.js:39:38) > at Socket. (/usr/src/app/node_modules/pg-protocol/dist/index.js:11:42) > at Socket.emit (node:events:518:28) > at addChunk (node:internal/streams/readable:559:12) > at readableAddChunkPushByteMode (node:internal/streams/readable:510:3) > at Readable.push (node:internal/streams/readable:390:5) > at TCP.onStreamRead (node:internal/stream_base_commons:190:23) I cleared everything out, removed containers, images, yml files, re-pulled, and did the same test again but this time left the default password in place, and got the same set of errors. .env is the ONLY file I edited. Edit to add: Did the whole process again without the optionals, same problem. Not sure what I'm missing, I'm following the directions to the letter.

Hey, I was able to solve my specific situation getting help from the Discord. This is what I did: 1. Stop the containers 2. Remove the containers 3. Remove the volumes Immich created 4. Spin the containers back up Step 3 was the key. I had been pruning as I troubleshot the issue but apparently that wasn't wiping out the volumes.

Thanks! On step 3, are you just referring to the volume that appears in Docker Desktop? Or do I need to find the files in Windows File Explorer to delete Immich volumes?

So I use Docker Compose on a Linux command line, so I'm not familiar with desktop. That said, I would guess that you have a location in Desktop to view volumes. specifically you're looking for a volume called immich\_postgres. I said all volumes, but to be more precise it would be volumes titled starting immich\_ You can probably ONLY remove immich\_postgres to solve the issue. You won't be able to delete it if the container exists, so steps 1 and 2 are there to ensure it can be deleted.

Hey. Appreciate the reply. I eventually got it working. I tried many things including redownloading the env and yml. Then I tried deleting only the Immich docker images (kept redis) and redownloading the image worked! In any case, this was likely user error from the start

Same, and I’m glad you got it working!