Issues upgrading from 2.3.1 on Unraid docker compose | Immich | Page 1

upper laurel Jan 29, 2026, 11:03 PM

#

I have Unraid with docker compose manager running 2.3.1, I tried upgrading to 2.4.1 couple weeks ago with some thumbnail/live video issuesm so now I tried again with the same issues. After upgrade to 2.4.1 everything works, just the uploading from my phone is weird. All newly uploaded pictures show "error loading image" in web ui, I have to manually select "Refresh thumbnails" on every image to fix this. On android it is fine, except the live video, which has incorrect aspect ration (but i saw some aspect ration bug fixes in recent version so maybe that might solve it)
The log says this

ERROR [Microservices:MetadataService] Failed to extract motion video for c491be83-d339-4f47-abf9-5e520fbc7b07: /usr/src/app/upload/upload/91272929-ceda-4f66-a469-b87213eccc16/fc/fc/fcfc421f-b937-4c05-8e16-3d2c2c8b2c12.jpg: PostgresError: column asset_exif.lockedProperties does not exist
PostgresError: column asset_exif.lockedProperties does not exist
    at ErrorResponse (/usr/src/app/server/node_modules/.pnpm/[email protected]/node_modules/postgres/cjs/src/connection.js:794:26)
    at handle (/usr/src/app/server/node_modules/.pnpm/[email protected]/node_modules/postgres/cjs/src/connection.js:480:6)
    at Socket.data (/usr/src/app/server/node_modules/.pnpm/[email protected]/node_modules/postgres/cjs/src/connection.js:315:9)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Readable.push (node:internal/streams/readable:392:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:189:23)

So that is one issue. I tried to fix it by upgrading directly to 2.5.2 but this time the web UI just shows "Failed to get time bucket (Immich Server Error)" and no images are visible. This is my docker compose. I tried to update the redis image from the new docker compose or removed the ram limitations i have there but it didnt make a difference.

📎 message.txt 📎 message.txt 📎 message.txt 📎 message.txt

flint bronzeBOT Jan 29, 2026, 11:03 PM

#

:wave: Hey @upper laurel,

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...

:ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
:ballot_box_with_check: read applicable release notes.
:ballot_box_with_check: reviewed the FAQs for known issues.
:blue_square: reviewed Github for known issues.
:ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
:ballot_box_with_check: uploaded the relevant information (see below).
: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.

upper laurel Jan 29, 2026, 11:05 PM

#

📎 dc.yaml

#

This is what i get from log right after upgrading to 2.5.2.

📎 log.txt

#

You guys have any tips what might by the issue here?
All help appreciated, thanks 🙂

river jacinth Jan 29, 2026, 11:13 PM

#

Please post the postgres server logs and run these command:
https://docs.immich.app/FAQ/#how-can-i-verify-the-integrity-of-my-database

upper laurel Jan 29, 2026, 11:20 PM

#

2026-01-29 23:12:12.992 UTC [61] ERROR:  column asset_file.isEdited does not exist at character 229
2026-01-29 23:12:12.992 UTC [61] STATEMENT:  select "asset"."originalPath", "asset"."originalFileName", "asset_file"."path" as "path" from "asset" left join "asset_file" on "asset"."id" = "asset_file"."assetId" and "asset_file"."type" = $1 where "asset"."id" = $2 order by "asset_file"."isEdited" desc
2026-01-29 23:12:12.996 UTC [79] ERROR:  column asset_file.isEdited does not exist at character 229
2026-01-29 23:12:12.996 UTC [79] STATEMENT:  select "asset"."originalPath", "asset"."originalFileName", "asset_file"."path" as "path" from "asset" left join "asset_file" on "asset"."id" = "asset_file"."assetId" and "asset_file"."type" = $1 where "asset"."id" = $2 order by "asset_file"."isEdited" desc
2026-01-29 23:12:12.999 UTC [82] ERROR:  column asset_file.isEdited does not exist at character 229
2026-01-29 23:12:12.999 UTC [82] STATEMENT:  select "asset"."originalPath", "asset"."originalFileName", "asset_file"."path" as "path" from "asset" left join "asset_file" on "asset"."id" = "asset_file"."assetId" and "asset_file"."type" = $1 where "asset"."id" = $2 order by "asset_file"."isEdited" desc

And many more lines like this

upper laurel Jan 29, 2026, 11:39 PM

#

I ran the DB commands, all looks fine. Checksums on, DB corruption all 0, file structure shows no errors

ruby sierra Jan 30, 2026, 8:58 AM

#

Can you post your .env file as well, for completeness?

upper laurel Jan 30, 2026, 9:08 AM

#

UPLOAD_LOCATION=/mnt/user/immich-media
SSD_LOCATION=/mnt/user/data-ssd/immich-ssd

DB_DATA_LOCATION=/mnt/user/appdata/immich/immich-postgres

TZ=Europe/Prague

IMMICH_VERSION=v2.5.2

DB_USERNAME=postgres
DB_DATABASE_NAME=immich


DB_SKIP_MIGRATIONS=true

#

Just removed the DB password line

ruby sierra Jan 30, 2026, 9:10 AM

#

DB_SKIP_MIGRATIONS=true
Why in the world do you have this set lol

#

That's the cause of your issues

upper laurel Jan 30, 2026, 9:32 AM

#

It must have been there from the last time I tried upgrading and found it somewhere online.
If I remove it and upgrade to 2.5.2, server is just restarting in loop without being able to access the web ui.

#

Even upgrading to 2.4.1 without this results in a server loop restarting.

ruby sierra Jan 30, 2026, 9:47 AM

#

Please post the logs from the latest upgrade without that env var set

upper laurel Jan 30, 2026, 9:51 AM

#

📎 im.log

ruby sierra Jan 30, 2026, 9:55 AM

#

Did you stop it manually at the end? Those errors are fairly harmless and shouldn't cause a crash/restart

upper laurel Jan 30, 2026, 9:55 AM

#

nope, not touching it at all

#

this is what it spits in the logs for each restart it does automatically

#

📎 im_log.log

#

current version, i have it running and it is still restarting by itself

#

Maybe there are some other logs I can give you? This is stack logs so i guess it should have all the containers in it.

#

#

docker version 27.5.1

upper laurel Jan 30, 2026, 10:25 AM

#

log from 2.4.1 upgrade

📎 241.log

#

i am just changing the version in env file, updating images and compose up, hope thats all it needs

upper laurel Jan 30, 2026, 10:42 AM

#

i can downgrade to 2.3.1 and everything works fine

#

2.4.0 doesnt work as well, keeps restarting the immich_server container, others are fine

📎 240.log

#

Do you think it`s worth it to try make a new instance of 2.5.2 with mounted media but without db and try to restore the old db from the new first page UI?

upper laurel Jan 30, 2026, 1:26 PM

#

Ok, i tried it and it has same error as the log says:

PostgresError: duplicate key value violates unique constraint "asset_file_assetId_type_uq"

#

#

2.3.1 DB dump

#

I just renamed the old db folder to generete new one and upgraded, the new startpage show up, i proceeded with restore of the 2.3.1 db i just dumped couple minutes ago in the web ui of 2.3.1, only restore issue with folders was in profile folder, it showed missing files i think, but i dont have any files in there (it is usually just profile picture which i didnt even set, right?), so i dont know what might be the problem here

ruby sierra Jan 30, 2026, 1:46 PM

#

upper laurel

Huh so the database dump has a duplicate key in it

#

That's very strange

upper laurel Jan 30, 2026, 2:00 PM

#

Do you have an idea what to do about it?

upper laurel Jan 31, 2026, 5:34 PM

#

Ok, I think I fixed it with the help of chatgpt, I had to run this on the postgres to delete pointers to sidecar, it then migrated without issues.
⁨```
DELETE FROM asset_file
WHERE type = 'sidecar';

#

Thanks for you help.

#Issues upgrading from 2.3.1 on Unraid docker compose

References

Checklist

Information