I
Immich2d ago
Domsl

Stacktrace after upgrade to stable

Hi, I just tried to upgrade from 1.140.0 to 2.000.0 (using "v2.000.0", but the I got the following error:
sudo docker compose -f docker-compose.immich.yml up -d
[+] Running 2/2
✘ immich-machine-learning Error manifest unknown 0.8s
✘ immich-server Error context canceled 0.8s
sudo docker compose -f docker-compose.immich.yml up -d
[+] Running 2/2
✘ immich-machine-learning Error manifest unknown 0.8s
✘ immich-server Error context canceled 0.8s
then I tried it with version=release, which sucellfully updated, but now when I open immich I get stack traces:
Error: 500 ()

Stacktrace
Error: Error: 500
at Object.Ge [as ok] (http://fred:2283/_app/immutable/chunks/Cn2c85Km.js:1:5430)
at async Promise.all (index 1)
at async n (http://fred:2283/_app/immutable/chunks/CtQfMd50.js:1:511)
at async o (http://fred:2283/_app/immutable/chunks/B5ohcbZc.js:1:177)
at async pt (http://fred:2283/_app/immutable/nodes/0.DGBk-j7E.js:1:1989)
at async je (http://fred:2283/_app/immutable/chunks/cztDL2Pb.js:1:15834)
Error: 500 ()

Stacktrace
Error: Error: 500
at Object.Ge [as ok] (http://fred:2283/_app/immutable/chunks/Cn2c85Km.js:1:5430)
at async Promise.all (index 1)
at async n (http://fred:2283/_app/immutable/chunks/CtQfMd50.js:1:511)
at async o (http://fred:2283/_app/immutable/chunks/B5ohcbZc.js:1:177)
at async pt (http://fred:2283/_app/immutable/nodes/0.DGBk-j7E.js:1:1989)
at async je (http://fred:2283/_app/immutable/chunks/cztDL2Pb.js:1:15834)
or
Error: 500 ()

Stacktrace
Error: Error: 500
at Object.Ge [as ok] (http://fred:2283/_app/immutable/chunks/Cn2c85Km.js:1:5430)
at async Promise.all (index 1)
at async n (http://fred:2283/_app/immutable/chunks/CtQfMd50.js:1:511)
at async o (http://fred:2283/_app/immutable/chunks/B5ohcbZc.js:1:177
Error: 500 ()

Stacktrace
Error: Error: 500
at Object.Ge [as ok] (http://fred:2283/_app/immutable/chunks/Cn2c85Km.js:1:5430)
at async Promise.all (index 1)
at async n (http://fred:2283/_app/immutable/chunks/CtQfMd50.js:1:511)
at async o (http://fred:2283/_app/immutable/chunks/B5ohcbZc.js:1:177
I might have nuked my database? The docker logs of the server show:
[Nest] 17 - 10/02/2025, 6:54:00 PM ERROR [Api:GlobalExceptionFilter~dnqrmo0z] Unknown error: PostgresError: relation "sessions" does not exist
[Nest] 17 - 10/02/2025, 6:54:00 PM ERROR [Api:GlobalExceptionFilter~dnqrmo0z] Unknown error: PostgresError: relation "sessions" does not exist
[Nest] 17 - 10/02/2025, 7:02:20 PM ERROR [Api:ErrorInterceptor~2fnqpgi1] Unknown error: PostgresError: relation "users" does not exist
[Nest] 17 - 10/02/2025, 7:02:20 PM ERROR [Api:ErrorInterceptor~2fnqpgi1] Unknown error: PostgresError: relation "users" does not exist
Any ideas? Do you think I should go straight back to my backup from last midnight? I am kind of worried, so any help would be very appreciated 🙂
5 Replies
Immich
Immich2d ago
:wave: Hey @Domsl, 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:
Domsl
DomslOP2d ago
sudo docker logs immich_server
Initializing Immich v1.131.3
sudo docker logs immich_server
Initializing Immich v1.131.3
damn - I guess I might have downgraded by accident by choosing release?! I try return back to v.1.140.0 I returned to previous version, seems to work again. Do you think I broke something? Should I be careful of anything? Or do you think it is save to try to upgrade to 2.0.0?
bo0tzz
bo0tzz2d ago
Probably fine You have a backup anyways
Domsl
DomslOP2d ago
Thank you for your time and answer! I upgraded (now actually upgraded :D) - everything is fine.
Immich
Immich2d ago
This thread has been closed. To re-open, use the button below.

Did you find this page helpful?