Failed to read upload/encoded-video/.immich
Hi ! I have some issues with immich on docker. I just update my immich server but get somes errors. I have read https://immich.app/docs/administration/system-integrity/#folder-checks but idk how can i fix it.
I use the lastest docker-compose with : wget -O docker-compose.yml https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml
In my console i get : https://pastebin.com/z0csH7cp
I anyone can help me :)
Ping for reply
29 Replies
:wave: Hey @Cleboost,
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.I use the lastest docker-compose with : wgetThis is not the right way to update
I used an old version of docker compose file befrore i get the new one
Please read this carefully
you seem to have updated from a pretty old version
You need to apply the breaking changes listed there and also have at least one version between 132 to 136 online for the migration to properly happen
i just apply the first breaking change to my docker
https://github.com/immich-app/immich/discussions/18429
now my container server spam log
but i dont touch redis config in my docker
Please post your current compose + env file
I'm pretty sure I said you need to run a version between 132 and 136 before it will work at all, but you are running
release
?mybad, that's true, I forgot
i just install
1.133.0
but same errors
What are you running this on?
this is a vm in my proxmox
Oh curious
How are you doing the container management? what commands are you using
i use same as wiki,
docker compose pull && docker compose up -d
purge sometime because i dont have lot of space on nvme (vm main disk)Running any other containers besides immich?
actually do a
docker compose down
and check with docker ps -a
whether everything is really down or there are orphaned containersyes, portainer but i think that not a problem
Are you not using portainer then? 😛
I see nothing that could cause this connection issue with redis
Try a simple reboot?
ah wait
I was using it, but to make sure it didn't come from there with my env var adaptations, I did my docker compose manually instead of using a stack.
could you check the volume attached to the redis container
and delete that manually
But that didn't solve my problem Portainer x)
Huh
I think i need to purge it

Bro....
Immich work
Why? Idk but it's working
We switched to valkey
But you switched back to redis
the functionality is identical but the volumes are not
I update 1.127 to 1.133 now
i will continue to latest with breaking changes
If you want to switch to the newest compose with valkey, do a
docker compose down -v
to wipe the redis volumethank you very much for all support, all work perfect now :)
This thread has been closed. To re-open, use the button below.