Unable to upgrade from unknown version. Hot mess inside.
So I don't know what version I was running before this mess started. What I do know is according to my mobile app, I was successfully syncing photos up until July 30th.
I tried to upgrade to latest release but the server container does not start, I see
In the logs
18 Replies
:wave: Hey @yahooeny,
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.I tried to downgrade to v1.132.3 and I get this error instead:
If I downgrade further to v1.131.1, the server container starts but the database seems mangled and I get the following log error:
And my homepage is blank. Not really sure what to do from here.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
I am running immich in a portainer stack.
This is the compose file:
1. v132 vs v122 in logs
I tried to downgrade to v1.132.3 and I get this error instead:
Initializing Immich v1.122.3So it was downgrade to 1.122, not 1.132, right? 2. What is in version history?
When you still have a DB which is intact, you could just do a whole fresh install, like:
1. Restore the DB
2. Move all Pictures/Videos etc to the new instance
that log was from running 1.122.3, yes. same thing happens in 1.132.3 however
^^ This
You can restore the database + revert to the initial compose file (if changed). Even without touching asset files.
hey if this is the path of least resistance i'll take it. will this retain users? i ask because i share this immich instance with my mom
So you was on v1.134.0 before. That's good, not so far from the release v1.139
haha i wish i knew that instead of fumbling around and downgrading to a version past what i was running
Coud you try v1.137.3 ?
wait a moment...
ah, i already recreated the container
and i'm back to
and if back to v1.134.0 ?
trying that...
whoa! ok. everything works again
regarding start.sh - https://github.com/immich-app/immich/issues/20421#issuecomment-3135671909
yes, that's probably what it was. i was just blindly upgrading by recreating containers in portainer
ok so my next steps are probably:
* do the vectorchord migration
* move up to 1.135 after changing the path variable
* move up to 1.136 after changing the immich_media_location path
* move up to 1.137 and check if anything is broken
* move up to latest?
phew ok. just kinda yolo'd my way to latest after the vectorchord migration and everything seems fine and i'm back on latest. thanks for the help yall!