Hello everyone.

Running immich off lxc container in proxmox and I created a symlink to move the library to a NAS share but I'm getting an error when I upload a file. [Nest] 124 - 08/24/2025, 8:35:55 PM DEBUG [Microservices:ApiKeyService] Attempting to rename file: /opt/immich/upload/upload/3308fee0-f6f1-43a9-a873-b87537318e62/54/20/5420e09a-e9b3-45e9-8f17-b61ee33f261e.jpg => /opt/immich/upload/library/admin/img_1458.jpg [Nest] 124 - 08/24/2025, 8:35:55 PM DEBUG [Microservices:ApiKeyService] Unable to rename file. Falling back to copy, verify and delete [Nest] 124 - 08/24/2025, 8:35:55 PM ERROR [Microservices:StorageTemplateService] Problem applying storage template [Nest] 124 - 08/24/2025, 8:35:55 PM ERROR [Microservices:StorageTemplateService] Error: EPERM: operation not permitted, copyfile '/opt/immich/upload/upload/3308fee0-f6f1-43a9-a873-b87537318e62/54/20/5420e09a-e9b3-45e9-8f17-b61ee33f261e.jpg' -> '/opt/immich/upload/library/admin/img_1458.jpg' at async Object.copyFile (node:internal/fs/promises:621:10) at async StorageCore.moveFile (/opt/immich/app/dist/cores/storage.core.js:156:17) at async /opt/immich/app/dist/services/storage-template.service.js:167:17 at async /opt/immich/app/dist/repositories/database.repository.js:379:27 at async /opt/immich/app/node_modules/.pnpm/kysely@0.28.2/node_modules/kysely/dist/cjs/kysely.js:535:20 at async DefaultConnectionProvider.provideConnection (/opt/immich/app/node_modules/.pnpm/kysely@0.28.2/node_modules/kysely/dist/cjs/driver/default-connection-provider.js:12:20) at async /opt/immich/app/dist/repositories/database.repository.js:376:13 I'm guessing it's a permissin thing but the NAS share is everyone full control and the permissions look good on the linux side: root@immich:/opt/immich/upload/library# ls -l total 0 lrwxrwxrwx 1 immich immich 23 Aug 24 15:56 admin -> /mnt/main/_photostorage Thank you! I appreciate it.
No description
No description
10 Replies
Immich
Immich2mo ago
:wave: Hey @DasVekman, 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.
Zeus
Zeus2mo ago
Permission issue indeed. We don’t recommend LXC, and DEFINITELY not the script which I believe doesn’t even use docker
DasVekman
DasVekmanOP2mo ago
@Zeus any change of a version without docker in the future? I use all LXC containers and would rather not do docker for just 1
schuhbacca
schuhbacca2mo ago
Not at this point. Docker makes it easier for the team to customize the libraries used by immich.
DasVekman
DasVekmanOP2mo ago
gotcha, ty. With docker, I'll be able to point the library and upload folders to another device?
schuhbacca
schuhbacca2mo ago
If you mean over SMB or NFS or something, yes.
DasVekman
DasVekmanOP2mo ago
yeah SMB, thanks!
schuhbacca
schuhbacca2mo ago
Just mount the smb share in the VM and all should work fine (Just don't put the DB on the remote network share)
DasVekman
DasVekmanOP2mo ago
yeah DB local ty!
Immich
Immich2mo ago
This thread has been closed. To re-open, use the button below.

Did you find this page helpful?