Errors after upgrade attempt
Tried to upgrade to v1.137.3 that didn't work. Went back to my old version v1.120.2 and now getting this error
Error: 500 ()
Stacktrace
Error: Error: 500
at Object.st [as ok] (http://192.168.68.67:2283/_app/immutable/chunks/fetch-client.BBjLa0zr.js:1:7295)
at async Promise.all (index 1)
at async n (http://192.168.68.67:2283/_app/immutable/chunks/server-config.store.DeBHHfFA.js:1:515)
at async o (http://192.168.68.67:2283/_app/immutable/chunks/server.BrciNeRq.js:1:189)
at async ra (http://192.168.68.67:2283/_app/immutable/nodes/0.C_df2rd4.js:1:2445)
at async Ue (http://192.168.68.67:2283/_app/immutable/chunks/entry.D-lbPkut.js:1:15768)
Please help how to fix it
49 Replies
:wave: Hey @lbg,
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.Docker logs please
Here are the requested logs
[31m[Nest] 17 - [39m09/29/2025, 7:33:52 PM [31m ERROR[39m [33m[Api:ErrorInterceptor~kfh1m9b7][39m [31mDatabase error: QueryFailedError: relation "users" does not exist[39m [31m[Nest] 17 - [39m09/29/2025, 7:33:53 PM [31m ERROR[39m [33m[Api:ErrorInterceptor~h3la8fiq][39m [31mDatabase error: QueryFailedError: relation "users" does not exist[39m [31m[Nest] 17 - [39m09/29/2025, 7:33:57 PM [31m ERROR[39m [33m[Api:ErrorInterceptor~zdfo6tvi][39m [31mDatabase error: QueryFailedError: relation "users" does not exist[39mYou didn't restore the database after reverting? In any case I'd advise you to go to 136 instead of 137 and then to latest, that should work If it doesn't, please post the logs from the attempt
ok, should I check if the upgrade to 136.0 is successful, or run two upgrades to 136.0 and then to 137.0 without any verifications?
start with checking 136
ok, running install...
immich_server is looping
ah darn, I was hoping this could have been avoided
but 137 will break the typeorm migrations 🤔
LOL I was hoping too...
You can pick between restoring an older backup or doing the 137 upgrade anyway and posting the error(s) so we can work it out
restoring - I have only media backup, I didn't take the database backup (my mistake), I think we can go to 137 since I already did that once
I'd pick that too, but you should have our automated DB dumps anyway in UPLOAD_LOCATION/backups
I didn't know that, where is that directory located?
What are you hosting on?
Ubuntu 24.04.3
So you've set UPLOAD_LOCATION in the .env
In that folder, there's another folder called backups
found it 14 days of backup
I'd still go for 137 but at least we know your daily dumps are working 😉
agree
running 137.0 install
as expected immich_server error
Now that's strange, it's still missing a migration even with 137?
You didn't go to latest, did you?
I don't think so
we can go back to the oldest backup available
Unfortunately I don't remember when I did it first time
I did an upgrade and had to travel for work
so there is a gap in between my attempts
I'm pretty sure it won't have made a dump during the time it was broken 😛
use the time converter (or just the file creation date?) to make sure
oh 👀 wild
Keep a copy safe!
I have to go to bed
can we reconnect tomorrow?
Sure thing, also feel free to post here regardless of whether I'm online
This is how you restore btw
made a copy of the backup, so do you want me to restore?
and to what version?
To whatever it was before would be best
docker exec immich_postgres psql -U postgres -d immich -c 'select version, "createdAt" from version_history'
If the postgres container still works, this should tell you whichdamn, I did 143.
version | createdAt
---------+-------------------------------
1.117.0 | 2024-10-07 20:44:30.883692+00
1.120.2 | 2024-11-15 17:47:20.530734+00
1.132.0 | 2025-09-22 20:03:15.692448+00
1.143.0 | 2025-09-22 20:20:15.413481+00
1.120.2 | 2025-09-26 21:24:33.066117+00
1.121.0 | 2025-09-29 14:50:22.575016+00
1.120.2 | 2025-09-29 19:32:51.432107+00
(7 rows)
Dunno that sounds like a nice thing to try too 👀
It also means the upgrade was succesful, apart from some DB shenanigans
Sep 22 was 132 and older than that was 120
So if you use the sep 19 or older backups, 120 it is
anyway I really need to go to bed 😛
Thanks!
Hi @Mraedis , the restore was a success!
Hurray
I'm back on v1.120.2
so, to avoid this mistake again, what are the steps to upgrade to the latest version from v1.120.2?
Hi @Mraedis I'm getting ready for the v1.132.3 upgrade can I ask you to check my docker-compose.yml?
Sure
actually when I restored, I've forgot to to change this:
database:
container_name: immich_postgres
# image: docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:90724186f0a3517cf6914295b5ab410db9ce23190a2d9d0b9dd6463e3fa298f0
image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:8d292bdb796aa58bbbaa47fe971c8516f6f57d6a47e7172e62754feb6ed4e7b0
The SHA doesn't matter much, and as long as the postgres image has the vector extension you used before and is on the same pg version it's fine
Which version are you upgrading to?
120.2 -> 132.3 as you suggested. after that 132.3->1.136.0 then latest.
to go to 132.3 can I use this image: image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0 ?
Ok, you should uncomment the healthcheck and command for 1.132.3 though
No keep the one you posted in the compose
For 1.136 you use the vectorchord image
(and also remove the healthcheck again)
is healthcheck needed for 120.2 -> 132.3?
well necessary is for when it doesn't work 😛