Upload issues with S3 - unfinished job queues, broken links ... #2521
-
Lychee versionv5.5.1 Which PHP version are you using?PHP 8.3 Detailed description of the problemHello, I can't get Lychee to work correctly with self-hosted S3 backend. Issue descriptionWhen using the "Upload photos" feature in the browser, although (as per S3 logs) all uploads were successfull, and all objects actually uploaded to the bucket (as per
When upload starts: A few moments later: Despite these, most of the time everything works alright, photos can be browsed, etc. However:
All these problems appear both with sqlite and mysql database backends, both with chrome and firefox. None of them seem to appear when not using S3 backend. I'm not sure it's related, but the following errors always appear in logs, when uploading (even a single) photos:
I've inserted a log in the
OtherI have a few other minor issues / questions regarding S3 support, I'll create separate issues for them, once this is figured out (as they might be related). S3 bucket for lychee devsPlease note that I'm willing to provide a permanent access to a S3 bucket to lychee devs for dev/testing, let me know if you're interested. Steps to reproduce the issueNo response Diagnostics [REQUIRED]
Browser & System [REQUIRED]System: FreeBSD 14.0, installed from the release v5.5.1 Please confirm (incomplete submissions will not be addressed)
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
That one will be fixed on the v6.
This will be reworked in the v6.
Seems indeed like it is to the wrong size variants. By the way, the S3 implementation has been done by @Kovah and to be brutally honest, I have 0 clue how it really works. I did try setting up an AWS S3 bucket but coulnd't get it to work. :( |
Beta Was this translation helpful? Give feedback.
-
This issue is indeed caused by the error below:
It should be fixed by this PR: #2849.
I was unable to reproduce this. In fact, all my duplicates are marked as 'skipped' and not uploaded. Do you have any more information about this? |
Beta Was this translation helpful? Give feedback.
This issue is indeed caused by the error below: