Invalid upgrade path?
Hello, I had been running Immich for a while without updating. It runs in docker. Today I ran docker compose pull and now the server fails to start. I've attached the log file.
My .env is standard:
UPLOAD_LOCATION=../library
DB_DATA_LOCATION=./postgres
TZ=America/Denver
IMMICH_VERSION=release
DB_PASSWORD=[Redacted]
The values below this line do not need to be changed
###################################################################################
DB_USERNAME=postgres
DB_DATABASE_NAME=immich
29 Replies
:wave: Hey @Juice Dab Isolation,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs
docs
- Container Status: docker ps -a
docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: reviewed the FAQs for known issues.
4. :ballot_box_with_check: reviewed Github for known issues.
5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: uploaded the relevant information (see below).
7. :ballot_box_with_check: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l
and df -h
).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close
command, and re-open it later if needed.Also here is my docker compose
It looks like there have been a lot of changes since I updated. Would it be best for me to start from scratch? I can backup my photos to another server if that would be best, but if there's a straightfoward path to upgrade properly that would be nice. Also I tried navigating to https://immich.app/errors#typeorm-upgrade but it's a 404.
Thanks so much!
Did you follow all breaking changes in between the version you were on and the latest? https://github.com/immich-app/immich/discussions?discussions_q=label%3Achangelog%3Abreaking-change+sort%3Adate_created
I'm not sure what version I was on 😬
docker exec immich_postgres psql -U postgres -d immich -c 'select version, "createdAt" from version_history'
ERROR: relation "version_history" does not exist
LINE 1: select version, "createdAt" from version_history
So probably a pretty old one then :monakS:
Ripp in my .env theres this comment
The Immich version to use. You can pin this to a specific version like "v1.71.0"
So probs close to that version
Would it be best to just reinstall in this case?
Personally I would try to salvage it by going through the breaking changes since 1.71 and booting into a few intermediate versions (especially v1.132.3 as mentioned in the docs), and theoretically it should work. But if you think it’s less work to just start fresh then that’s up to you
Okay I'll try to salvage it then 👍
1.71 is > 2 years old :monakS:
Nah that's not really meaningful
It still says that in the comment today
I assume that’s not what they were on but at least we know that’s the worst case scenario
It's at least a year because I have all my versions in there and I've been using it since august 2024 :p
I checked the file date from the OS and they were created July 2 2024
The compose and .env files
Sounds like around v1.107 then
But I know I updated at least once between then and now so not sure
You don't have
start.sh
so at least newer than 107
port is still 3001 so older than 1.118I was accessing it through 2283
Apply the breaking changes from 118 and 133
https://github.com/immich-app/immich/discussions?discussions_q=label%3Achangelog%3Abreaking-change+sort%3Adate_created
Then set the IMMICH_VERSION to
v1.136.0
and update
yes you were, but not in your composeahh gotcha
2283:3001 -> 2283:2283
Thank you I'll give that a try
If you are using oauth don't forget to apply 118
if you don't know what oauth is, you're not using it
Awesome that worked great!!
If you've managed to upgrade to 1.136 successfully, just go straight to
release
this timeMoving forward I'll do my best to stay on top of updates lol you guys just work so quickly
version 1.143.1 appears to be working correctly 👍