I am running Unraid 7.0.1 and have immich set up as a docker. My current Immich server version is v1.129.0 and I cannot get it to update. I have posted to the Immich github support and they say it is an unraid issue. 

I go to the docker and hit "apply update" and it appears to run through the entire update process and ends by saying "The command finished successfully!" I hit the "Done" button, but then sure enough, no update applied!

 

I just don't understand why this won't update. Logs are attached. Any help would be so appreciated!

immich.log.txt

Post the docker run output.

I think this is what you mean? See attached, let me know if this is not what you mean.

immich.update.txt

Yeah that looks good. And you’re still not in 1.132.3 after that?

nope, runs through the entire process and then just leaves me at 1.29.0

 

 

try this, instead of using the :latest tag, change it to this:

 

ghcr.io/imagegenius/immich:1.132.3

 

On the immich template page, check the advanced view and replace the repository line with this ^

 

example of where to put it:

Edited May 11, 20251 yr by MowMdown

That seems to have crashed immich all together. Did I just lose all my Immich photos?

 

 

immich.log new.txt

No you didn’t lose anything, just change it back to “:latest” and it should bring it back.

 

apparently you might have to log into GitHub or something to pull the correct docker information. 
 

running “docker logout ghcr.io” from command line and then maybe running “docker login ghcr.io” and logging back in?

Edited May 11, 20251 yr by MowMdown

Well, I am at a loss, so weird. changed it to ":latest" and looking at the docker it now says up today and looks fiine but now can't access the webui....

immich.log new.txt

Edited May 11, 20251 yr by DarB
Adding logs

the logs say the postgres password is invalid. Did something change?

 

PostgresError: password authentication failed for user "postgres"

 

Edited May 11, 20251 yr by MowMdown

That was weird! Not sure how that happened. Changed the postgres password back and now the server is up to date??

I don't quite understand what happened but it is working now so...okay. 

2 hours ago, DarB said:

That was weird! Not sure how that happened. Changed the postgres password back and now the server is up to date??

I don't quite understand what happened but it is working now so...okay. 

postgress template to set the password is a one time at first run  to trigger Postgres sql initialization... if you change Postgres password you have a runnign database, You will need to delete the appdata folder and recreate the postgress database to use the new updated password...

(Or run Postgres sql table commands to update and change passwords...)
 

 

9 minutes ago, bmartino1 said:

postgress template to set the password is a one time at first run  to trigger Postgres sql initialization... if you change Postgres password you have a runnign database, You will need to delete the appdata folder and recreate the postgress database to use the new updated password...

(Or run Postgres sql table commands to update and change passwords...)
 

 

So, I was able to use the same postgres password that I used at set up (it was still the same in the postgres docker, just changed somehow in the immich docker) and it worked. Do I still need to do this?

2 minutes ago, DarB said:

So, I was able to use the same postgres password that I used at set up (it was still the same in the postgres docker, just changed somehow in the immich docker) and it worked. Do I still need to do this?

no if immich and Postgres are talking once more leave it be

2 minutes ago, bmartino1 said:

no if immich and Postgres are talking once more leave it be

Sounds good! Thanks

2 hours ago, MowMdown said:

the logs say the postgres password is invalid. Did something change?

 

PostgresError: password authentication failed for user "postgres"

 

Thanks so much for the help today!