Multiple errors in Immich

Hi everyone, I’m running into some frustrating issues with Immich. My immish is running on Container Station on a QNAP NAS. 1) Admin panel → I can’t access it anymore. When I click on Administration, I get a 500 error: Failed to get storage - 500 Error: Error: 500 at Object.rt [as ok] (…/B5Vwu9Yy.js:1:5407) at async Ti (…/BhBgn_Ix.js:1:72418) at async Ct (…/40.DV7kHpur.js:1:1481) at async Fe (…/2mN68leT.js:1:16238) 2) Zooming on a photo → I get a loading error. 3) Playing videos → Nothing happens. (Solved by adapting my caddyfile to take in charge big files, thx to the FAQ) Has anyone else experienced these issues or knows how to fix them?
9 Replies
Immich
Immich4w ago
:wave: Hey @StephBdx, 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.
StephBdx
StephBdxOP4w ago
Any help is welcome, I updated Immich client and server with the latest package (1.140.1) but without any result. Immich is running under Container Station on a QNAP TS-253D with 32Gb of memory and a few TB of free space.
Immich
Immich4w ago
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
StephBdx
StephBdxOP4w ago
docker ps -f name=immich CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES dce5a522a871 altran1502/immich-server:release "tini -- /bin/bash -…" 4 days ago Up 19 hours (healthy) 0.0.0.0:2283->2283/tcp immich-server ae094893bdf2 altran1502/immich-machine-learning:release "tini -- python -m i…" 4 days ago Up 4 days (healthy) immich-machine-learning 33e800b1a0cd tensorchord/pgvecto-rs:pg15-v0.2.0 "docker-entrypoint.s…" 5 weeks ago Up 3 weeks (healthy) 5432/tcp immich-postgres 149f04c85e02 redis:7-alpine "docker-entrypoint.s…" 5 weeks ago Up 3 weeks (healthy) 6379/tcp immich-redis
StephBdx
StephBdxOP4w ago
Here is the error message when I try to click on the Administration button
No description
bo0tzz
bo0tzz4w ago
Can you get the specific logs that are generated when you trigger that error?
StephBdx
StephBdxOP4w ago
Here is the log generated by the error: [Nest] 19 - 09/10/2025, 5:31:19 PM ERROR [Api:ErrorInterceptor~0kd87b7x] Unknown error: Error: ENOENT: no such file or directory, statfs '/usr/src/app/upload/library' Error: ENOENT: no such file or directory, statfs '/usr/src/app/upload/library' at async Object.statfs (node:internal/fs/promises:1048:18) at async StorageRepository.checkDiskUsage (/usr/src/app/server/dist/repositories/storage.repository.js:137:23) at async ServerService.getStorage (/usr/src/app/server/dist/services/server.service.js:57:26) [Nest] 19 - 09/10/2025, 5:31:19 PM ERROR [Api:ErrorInterceptor~fpmafxt5] Unknown error: Error: ENOENT: no such file or directory, statfs '/usr/src/app/upload/library' Error: ENOENT: no such file or directory, statfs '/usr/src/app/upload/library' at async Object.statfs (node:internal/fs/promises:1048:18) at async StorageRepository.checkDiskUsage (/usr/src/app/server/dist/repositories/storage.repository.js:137:23) at async ServerService.getStorage (/usr/src/app/server/dist/services/server.service.js:57:26) [Nest] 19 - 09/10/2025, 5:32:21 PM ERROR [Api:ErrorInterceptor~51ildiro] Unknown error: Error: ENOENT: no such file or directory, statfs '/usr/src/app/upload/library' Error: ENOENT: no such file or directory, statfs '/usr/src/app/upload/library' at async Object.statfs (node:internal/fs/promises:1048:18) at async StorageRepository.checkDiskUsage (/usr/src/app/server/dist/repositories/storage.repository.js:137:23) at async ServerService.getStorage (/usr/src/app/server/dist/services/server.service.js:57:26)
bo0tzz
bo0tzz4w ago
The files aren't where they should be There's probably something wrong with your mount point
Sergey Katsubo
There's probably something wrong with your mount point
Definitely. @StephBdx was you config always like this:
IMMICH_IGNORE_MOUNT_CHECK_ERRORS: true
volumes:
- ${UPLOAD_LOCATION}:/usr/src/app/upload/thumbs
IMMICH_IGNORE_MOUNT_CHECK_ERRORS: true
volumes:
- ${UPLOAD_LOCATION}:/usr/src/app/upload/thumbs
Or did you modify it recently? Your compose looks similar to this one https://blog.immensity.in/qnap-running-immich-using-container-station/. Have you considered running official compose+.env?

Did you find this page helpful?