Immich microservice won't boot up since update to newest version

After updating my immich from 1.51 to 1.52 the immich microservice service (and immich_proxy) somehow keeps restarting with the validation error message: Typesende_api_key is required. Can somebody please help me? Im using a dell wyse 5070 with debian, on proxmox. Furthermore when accessing the webpage i get the following error: getaddrinfo ENOTFOUND immich-server
No description
16 Replies
bo0tzz
bo0tzz3y ago
Did you read the release notes?
Peda1996
Peda1996OP3y ago
this time I didn't, have I missed something important?
bo0tzz
bo0tzz3y ago
Yes, you should read them every time
Peda1996
Peda1996OP3y ago
thanks dude, so I just have to add typesense to my docker compose and everything should work again?
bo0tzz
bo0tzz3y ago
Yes
Peda1996
Peda1996OP3y ago
thanks a lot 🙂 i feel kinda stupid now for asking this question, and wasting your time 😅
bo0tzz
bo0tzz3y ago
All good! At least it was an easy one to answer ;)
Peda1996
Peda1996OP3y ago
thanks dude 🙂 well, somehow I also have the same error after changing the setting do you know a way of getting this TYPESENSE_API_KEY api key? well, now the immich_typesense container also keeps on restarting
Alex Tran
Alex Tran3y ago
TYPESENSE_API_KEY is a random value that you specify
Peda1996
Peda1996OP3y ago
thanks for your info 🙂 somehow I missed this when updating thanks a lot Alex and bo0tzz, its working now: If anybody is having the same issue, just a small summarization for updating: 1. add these to .env TYPESENSE_API_KEY=some-random-text 2. exchange your docker compose for the newest version Now just update like you would regularly update the service: 1. docker compose pull 2. docker compose up -d
David P.
David P.3y ago
I just came here for the same error, and glad I got a quick resolution!
danielo515
danielo5153y ago
Is it just me or almost every release introduces a new required env variable that breaks things? I don't see red flags and warning ⚠️ signs in the annoucements channel, which should be
bo0tzz
bo0tzz3y ago
The warnings are in the release notes, which you should read every time before upgrading
danielo515
danielo5153y ago
I don't update on a weekly basis, so it's hard to find the breaking changes. I'll review them, if the breaking changes are there, then fair
Alex Tran
Alex Tran3y ago
Good idea
danielo515
danielo5153y ago
Awesome. Everything that makes breaking changes more visible is welcome

Did you find this page helpful?