Error after updating server(v.112 -> v.143) on Synology nas
Hello everyone.
I'm really new in this docker/container stuff. I've had a Immich server running my Synology NAS since february and we encountered a few issues with our phone apps, so thought it was bout time I went about updating the server.
I updated the Immich stack through Portainer and now I'm getting this error when Immich-SERVER runs:
I of course went to the link and read the guide that says I need to do a intermediate upgrade to 1.132.2, but I have no clue how to target a specific release through portainer. Could someone help shed light on this? 🙂
14 Replies
:wave: Hey @Zpanzer,
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.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:Did you read all the breaking changes and apply them in between your version you were on and the lastest?
as far as I can see, theres tons of breaking changes that has to do with the docker config. But none are specific to the issue with "TypeORM Upgrade".
It seems like I have to do a target update to 1.132.2 first, fix the issues with that, and then go from there towards release.
But I cant seems to figure out how to do the targeted updates through Portainer.
You will need to go back to your version you were on, probably restore a backup, then in the compose file, specify the version of the breaking change to pull. Apply the changes from the link above for that version. So on until you get to latest
setting the image in portainer from release to 1.132.2 doesn't seem to work
I believe you need a v in front.
v1.132.2doesn't seem to work.
Can you post your compose and env
Your image is wrong for both the ml and server.
You have
ghcr.io/immich-app/immich-server:1.132.2 should be ghcr.io/immich-app/immich-server:v1.132.2 also you are pulling latest for the ML container stillI've tried with both v infront and -release on both of them.
I've been googling like crazy, but no matter what I set up, I get the missing manifest
okay, I think I might have gotten some progress. I've tried moving down versions from 1.132.2 until it started
Thanks for the help, I appreciate the time! I will try this out and if ends out not working, I will have to clean installs
Yep, going from 1.112->1.132->release worked perfectly
This thread has been closed. To re-open, use the button below.