-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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]: Web File Upload buggy/not resilient on bigger files (Firefox) #44113
Comments
Probably duplicate of nextcloud-libraries/nextcloud-upload#5 |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
In my case the probles came from traefik in the 2.11.1 version (so it's not related to this issue because here it seems ngnix is used - sorry for interfering). I downgraded traefik to 2.10.7 and now everything works fine. Before I couldn't upload files greater approx. 50MB. Only the Nextcloud PC Client could do because it failed, and recovered in several iterations until the upload was done... (no retry for failed chuncs from browser upload). Uploaded 8GB this way. Traefik seems to play around with this (not helpful) fix: traefik/traefik#10599. Welcome in configuration hell: https://github.com/traefik/traefik/wiki/respondingTimeouts-for-applications. All this goes beyond by skills. I was not able to configure the latest traefik version to work correctly wih nextcloud. Never had a problem the last 5 years with traefik... |
Yes, I agree, let's close this one then :) |
Could this be the same I did run into? |
Bug description
The Web File Uploader is buggy/not resilient enough when uploading larger files (e.g. a 800mb file). Random chunks might fail to upload on the browser side and are not retried.
Also there seems to be a timing issue which deletes upload directories before the file upload is actually complete. The Move command also seems to be missing.
Here the first chunk fails, but the file upload continues. The Chunk is never retried:
Here we can then see a timing issue where the web upload client deletes the upload directory before the file upload is finished:
Another try on uploading the same file, here a random later chunk failed, no retry is done. The Move command is not sent but the upload directory is deleted in the end. No error message was displayed in the browser
These are the log messages in the web developer console. Apparently the code sees that a chunk failed to upload, but does not retry to upload it.
The NS ERROR NET INTERRUPT seems to be a bug in firefox related to http2/http3 ( https://stackoverflow.com/a/76873402/979507 ) . I will disable http2/http3 in the meantime. While this issue might be related to the bug in firefox, it highlights the underlying issue that the web uploader is not retrying to upload a chunk if it failed for some reason.
Steps to reproduce
Expected behavior
Installation method
Community Docker image
Nextcloud Server version
28.0.3
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.3
Web server
Apache (supported)
Database engine version
MySQL
Is this bug present after an update or on a fresh install?
Fresh Nextcloud Server install
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
I'm fronting the nextcloud installation with nginx on docker:
with this custom config for the hostname in question:
The text was updated successfully, but these errors were encountered: