Immich•3w ago

Bad Gateway after updating to v1.142.1 from v1.141

Watchtower automatically updated Immich to 1.142.1 from v1.141, now I get a bad gateway error on the web app. This is a Saltbox install with traefik as the frontend. I get the following in the logs repeatedly.

Starting api worker
[Nest] 5052  - 09/17/2025, 8:01:32 PM     LOG [Api:EventRepository] Initialized websocket server
[Nest] 5052  - 09/17/2025, 8:01:32 PM     LOG [Api:DatabaseRepository] targetLists=1, current=1 for clip_index of 2248 rows
[Nest] 5052  - 09/17/2025, 8:01:32 PM     LOG [Api:DatabaseRepository] targetLists=1, current=1 for face_index of 763 rows
[Nest] 5052  - 09/17/2025, 8:01:32 PM     LOG [Api:StorageService] Verifying system mount folder checks, current state: {"mountChecks":{"thumbs":true,"upload":true,"backups":true,"library":true,"profile":true,"encoded-video":true}}
[Nest] 5052  - 09/17/2025, 8:01:33 PM   ERROR [Api:StorageService] Failed to write /photos/encoded-video/.immich: AggregateError: EPERM: operation not permitted, write
api worker exited with code 1

Starting api worker
[Nest] 5052  - 09/17/2025, 8:01:32 PM     LOG [Api:EventRepository] Initialized websocket server
[Nest] 5052  - 09/17/2025, 8:01:32 PM     LOG [Api:DatabaseRepository] targetLists=1, current=1 for clip_index of 2248 rows
[Nest] 5052  - 09/17/2025, 8:01:32 PM     LOG [Api:DatabaseRepository] targetLists=1, current=1 for face_index of 763 rows
[Nest] 5052  - 09/17/2025, 8:01:32 PM     LOG [Api:StorageService] Verifying system mount folder checks, current state: {"mountChecks":{"thumbs":true,"upload":true,"backups":true,"library":true,"profile":true,"encoded-video":true}}
[Nest] 5052  - 09/17/2025, 8:01:33 PM   ERROR [Api:StorageService] Failed to write /photos/encoded-video/.immich: AggregateError: EPERM: operation not permitted, write
api worker exited with code 1

I tried chmod 777 .immich Also deleted and redeployed the containers. Container logs attached Any thoughts on how I can make this work again?

immich.txt

immich-redis.txt

immich-postgres.txt

13 Replies

Immich•3w ago

:wave: Hey @mappedoutkc, 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.

Mraedis•3w ago

No clue what Saltbox is, it sounds like you want to ask them because Failed to write /photos/encoded-video/.immich: AggregateError: EPERM: operation not permitted, write is not an Immich issue, it's a host issue

mappedoutkcOP•3w ago

The /photos dir is an rclone mounted crypt google remote, its not a local drive. I can edit the file, and it has the correct permissions. The only thing that has changed is v1.142.1, all was working before that upgrade. Can I delete that file and have immich recreate somehow? I'm not sure that failed to write error is even related to the bad gateway errors.

Mraedis•3w ago

That is a mount check to see if everything is mounted correctly, deleting it will simply make immich refuse to startup

mappedoutkcOP•3w ago

so immich is refusing to start because of this error as well? or only wont start if file isnt there?

Mraedis•3w ago

Both, it needs to be able to read/write the file

mappedoutkcOP•3w ago

ok, so that is the problem

Mraedis•3w ago

and if the file doesn't exist while it should, it will refuse to start Also I have not seen anyone have a good time with their library on an rclone drive

mappedoutkcOP•3w ago

which user is that operation performed by?

Mraedis•3w ago

Whatever user you're running immich as Is this even docker?

mappedoutkcOP•3w ago

yes

Mraedis•3w ago

So whatever the docker user is then

mappedoutkcOP•3w ago

UID 1001 is what immich is running under, and that is the owner of that .immich file. weird i can login to the host and edit that file with UID 1001

Gaming

Programming

Bad Gateway after updating to v1.142.1 from v1.141

Did you find this page helpful?