Upgrading from older versions
Hi, I'm currently running an older Immich version (because I'm an idiot), v1.125.7; the release notes for v2.0 mention there's no need to do anything specific before upgrading to it, but I'm assuming that applies to upgrades from the latest version before that. Is there something specific I need to do, such as maybe upgrading to specific in-between versions, or can I actually just upgrade to v2.0.1 or even v2.1?
13 Replies
:wave: Hey @Nix,
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. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: 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.
https://github.com/immich-app/immich/discussions?discussions_q=is%3Aopen+label%3Achangelog%3Abreaking-change+sort%3Adate_createdThis list all version were breaking changes happened
Although You can go to 1.132.3 to directly 2.1, if and only if, you also apply the different breaking changes in between
Meaning that when you’re on 132 you apply the changes of 136 and 137 when upgrading to latest
so, since I'm on 1.125.7, I should upgrade to v1.133 (performing the appropriate actions), then prepare for upgrading to v1.136 and v1.137, and then upgrade to v2.1?
I would do
132.3 (I think there were no breaking changes)
137.0 (while also applying changes of 133 and 136)
2.1
why 132.3 if the listed breaking version is 133?
Because it’s the last version without any breaking changes
makes sense
And to go straight to 137, you had to start to 132 or newer
But if you want to update to each breaking change version you also can
It’s just personal preference here
133
137
2.1
Works
Well I would even do
132.3
2.1 (while applying changes of 133, 136 and 137)
Which is the « safest way »
I can hazard the riskier way given I just took a drive snapshot, I guess
I see 136 doesn't apply
same goes for 137, since it just wants me to run 132 before upgrading
I'm still going to do the safe thing and upgrade to breaking versions, as well as manually inspecting env and docker-compose files for changes
on a somewhat related note, I might've been a dummy and forgot to change the DB password from the default
postgres
I'm guessing it'll just break if I change it in the .env file now, so I should probably also manually change it in Immich's database via psql?Yes, you have to change it at both places
https://docs.immich.app/guides/database-queries/#postgres-internal
A command like this, I think allows you to change it (adapt it with your container name; postgres user and password
thanks, much appreciated
ok, I'm at v2.1 and nothing seems to have broken; thanks a lot for your help!
No problem! Glad I could help and happy you got it working:)
This thread has been closed. To re-open, use the button below.