-
Lychee versionv7.4.2 Did you check the latest Lychee version?Yes, I did Which PHP version are you using?PHP 8.5 Detailed description of the problemI've been having issues uploading images on a specific Lychee instance, with or without workers, which has persisted since roughly version 7.0 (though I updated to 7.3.2). I recently migrated to a new system, and it looks like it's failing again on v7.4.2. One way this has manifested is a bunch of placeholders with missing original images: 
When I go to one of the images and try and download it, I get this: 
with these log entries: and sure enough when I go to my Steps to reproduce the issue
Diagnostics [REQUIRED]Browser & System [REQUIRED]System: Lychee v7.4.2 on docker, host is Unraid v7.2.3 Please confirm (incomplete submissions will not be addressed)
|
Beta Was this translation helpful? Give feedback.
Answered by
rfilmyer
Mar 31, 2026
Replies: 3 comments 6 replies
-
So the reason why this is happening is because in version 7.2 (if I remember correctly) we fixed the root-less mode so you can now properly set your puid and guid. As a consequences, images which were uploaded prior, have the wrong access permissions. The way to fix this is pretty much a |
Beta Was this translation helpful? Give feedback.
5 replies
-
|
If I have: in my |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
You should see in the container log: |
Beta Was this translation helpful? Give feedback.
-
|
Confirming that I see that, and I think I remember having to Though on this system, the primary group of user 1000 looks to be group ID 100... 
... so out of an abundance of caution, I'm doing a rebooting works fine, looking at the diagnostic page, these warnings show up again... so I'm fixing those permissions... and I try and upload, and the same thing happens. No dice. |
Beta Was this translation helpful? Give feedback.
-
|
Full logs of me uploading photos, then attempting to look at them and download an original: |
Beta Was this translation helpful? Give feedback.
-
|
So I've enabled debug mode after trying to upload photos again, with the same issues (it seems like I've now lost the ability to make writes against my other lychee installation, after migrating it to unraid). This is a sample traceback that got spat out from trying to download one of the borked files: Lychee Error Traceback 2026-03-30-18-46.pdf I seem to get a few "Write Errors" from the docker container when I either upload or attempt to view photos. The failed album is here: https://photos.synolect.com/gallery/qsDK4zYBTxo7PT4orNT-u_mT |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I did something stupid. Fixing it resolved this problem: 
The issue was in my docker-compose file: I forgot to add the bind to I wonder if this can be a diagnostic thing to check for the workers... I guess I'm thinking of new ways to screw up the config. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Well that does not help indeed :/ |
Beta Was this translation helpful? Give feedback.
Answer selected by
rfilmyer
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I did something stupid. Fixing it resolved this problem:
The issue was in my docker-compose file: I forgot to add the bind to
/app/public/uploadsto my worker containers. This meant that files uploaded and processed properly, but were never written to disk.I wonder if this can be a diagnostic thing to check for the workers... I guess I'm thinking of new ways to screw up the config.