Large Uploads (>100MB) fail with 404 "Failed to load resource"
-
When uploading files larger than 100MB, the upload fails and the browser console reports: Failed to load resource: the server responded with a status of 404 ().
I think this is because Cubby does not support chunked uploads and users behind proxies like Cloudflare (Free tier) are strictly limited to 100MB per request?
If so, would be great if Cubby could in the future implement chunked file uploads (splitting large files into smaller parts during transmission) to ensure reliability and bypass common proxy limitations (e.g., Cloudflare's 100MB limit), similar to NextCloud.
-
The 404 is likely just the name collision pre-flight check the UI does to see if the uploaded file would need a different name. This has caused confusion a few times, as it is an error status code but in this case not an error.
The chunked upload is probably a valid feature request.
-
Hi @nebulon , hope all is well. Is the chunked upload feature on the roadmap for the future?
-
Thanks for the reminder, I have looked into this again and added chunked upload for file larger than 90Mb now. There is one caveat though, this is only supported via the webinterface for now. webdav and WOPI (office intergration) do and I think never will support that, as those clients are out of our control.
-
N nebulon marked this topic as a question
-
N nebulon has marked this topic as solved
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login