I made a mistake of upgrading directly to v2.0 from v.1.131.3
I was using immich version 1.131.3 and directly upgrade to v2.0 and when i ran the docker compose up, ran into problem, immich-server microservices exited with code 1, and saw an error message Invalid upgrade path. when cchecking the typeORM error it said that i should ugraded to version 1.132.3 and the consequently can upgrade to version 1.37 and above. What should i do? can i downgrade back to version 1.132.3?
7 Replies
:wave: Hey @Fathi,
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. :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.yup
and directly upgrade to v2.0what steps did you take? Have you changed your compose since v1.131.3?
can i downgrade back to version 1.132.3?yes. However if you already modified your compose for 2.0, then you should revert to your older compose file.
Yup i used the compose file for v2.0
now i am reverting back to my old compose file and try to use v.1.132.3
found this on github https://github.com/immich-app/immich/issues/22115
downgraded back to 1.36.0 and then upgrade back to latest realese works for me
when i downgrade to 1.36.0 there was error message on multiple primary keys for table "geodata-places". I ignored it and changed abck to latest release with the v2.0 compose file
and now it works
This thread has been closed. To re-open, use the button below.