-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Unable to upload "big" files to S3 external storage #43642
Comments
Might be unrelated to big files, I'm getting a 500 when uploading a random photo I just took from the mobile app. |
For what it's worth, I can upload files to S3 via External Storage without any problem, Both large and small. If there is a 500 error, please look at the entries in the Nextcloud log during the time period of the upload for clues as to the underlying cause. |
All my errors in the log have to do with that same Array to string conversion I already sent. |
Related: #43408 |
The array to string conversion will be addressed in #43794. It's unclear if that's the underlying cause of your primary reported issue, but it's definitely the one you provided logs for. Any chance you confirm whether applying that PR in your environment addresses your upload issue? https://docs.nextcloud.com/server/latest/admin_manual/issues/applying_patch.html |
Bug description
I simply can't upload files larger than at least 80MB using Nextcloud. It uploads just fine on S3 console.
Steps to reproduce
Expected behavior
It should upload.
Installation method
None
Nextcloud Server version
26
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
Using Caddy and here's the file: https://drive.google.com/file/d/1YiYQhWQxqOA8fBGJPQhrWT2snHOUeJix/view?usp=sharing
The text was updated successfully, but these errors were encountered: