[2026-07-10 09:14:03] Customer - Maya R.: Hi, I'm running a self-hosted photo library on my home server and the mobile app stopped backing up new photos yesterday.

[2026-07-10 09:14:22] Support - Daniel: Hi Maya, I can help with that. Are you able to view your existing library from the mobile app, or is the app unable to connect at all?

[2026-07-10 09:14:47] Customer - Maya R.: I can browse everything that's already there. Albums load fine. It just says "Backup pending" for 184 items.

[2026-07-10 09:15:11] Support - Daniel: Thanks, that helps narrow it down. Could you check the server dashboard and tell me whether the storage volume is showing enough free space?

[2026-07-10 09:16:02] Customer - Maya R.: It says 1.8 TB free, so space should be okay.

[2026-07-10 09:16:31] Support - Daniel: Good. Next, please open Settings > Jobs on the server dashboard and check whether the "Library scan" or "Upload processing" jobs are paused or failing.

[2026-07-10 09:17:40] Customer - Maya R.: Upload processing shows failed 6 times. Last error says: "permission denied: /photos/incoming/mobile."

[2026-07-10 09:18:05] Support - Daniel: That points to a filesystem permission issue. Did anything change recently, such as moving the photo folder, updating Docker, or restoring from backup?

[2026-07-10 09:18:31] Customer - Maya R.: I updated the container yesterday and also changed the folder from an external USB drive to a NAS mount.

[2026-07-10 09:19:10] Support - Daniel: Understood. The container likely no longer has write access to the new mount. What user ID and group ID is your photo library container running as?

[2026-07-10 09:20:18] Customer - Maya R.: In my compose file it's PUID=1000 and PGID=1000.

[2026-07-10 09:20:47] Support - Daniel: Please run `ls -ld /path/to/photos/incoming/mobile` on the host and check the owner shown there.

[2026-07-10 09:22:03] Customer - Maya R.: It shows `root root`.

[2026-07-10 09:22:29] Support - Daniel: That's the issue. The container user 1000:1000 can read existing files but can't write new uploads to that folder. You can fix it by changing ownership of the photo directory to the same UID and GID used by the container.

[2026-07-10 09:23:14] Customer - Maya R.: So `chown -R 1000:1000` on the photo folder?

[2026-07-10 09:23:38] Support - Daniel: Yes, but run it only against the photo library path, not the whole NAS mount. For example: `sudo chown -R 1000:1000 /mnt/nas/photos`.

[2026-07-10 09:25:09] Customer - Maya R.: Done. Do I need to restart anything?

[2026-07-10 09:25:31] Support - Daniel: Please restart the photo library container, then open the mobile app and tap "Retry backup" if it doesn't start automatically.

[2026-07-10 09:27:02] Customer - Maya R.: Restarted. The app now says "Uploading 1 of 184." Looks like it's moving.

[2026-07-10 09:27:24] Support - Daniel: Great. While it uploads, keep the app open for a minute and confirm the server dashboard shows new files under Upload processing.

[2026-07-10 09:28:16] Customer - Maya R.: Yes, it's processing now. No errors so far.

[2026-07-10 09:28:43] Support - Daniel: Then the backup issue is resolved. The root cause was that the new NAS-backed photo folder was owned by root, while the container runs as UID/GID 1000.

[2026-07-10 09:29:11] Customer - Maya R.: Makes sense. Thanks for explaining it clearly.

[2026-07-10 09:29:29] Support - Daniel: You're welcome. If the NAS resets permissions after reboot, check the mount options or NAS share settings so newly mounted folders remain writable by UID 1000.