-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Google Drive remote source does not chunkify the request for Tus server #4857
Comments
what's your companion configration? i just tried to upload a 100gb file from google drive to tus and at 500+mb the uploaded it's still going strong..
do you see anything in companion logs? also when do you get the 413 error? do you get it immediately after the upload starts, or only right after the upload progress has exceeded 100mb? also are you running newest version of uppy and companion? |
thx. which companion version are you running? |
I think the problem is that you're not setting I just tested companion remote uploads using Tus and onChunkComplete(...args) {
console.log('chunk complete', ...args)
} and run an upload, I see
so I think you just need to set the companion variable too |
Initial checklist
Link to runnable example
No response
Steps to reproduce
I have a limit of 100MB per request on my server.
Uppy init:
Companion standalone config:
Tusd server command:
tusd -hooks-http https://mysite.com/api/cloud/upload_check -disable-cors -behind-proxy -upload-dir=/ssd/uploads -host=192.168.0.122 -port=3022
Expected behavior
When I upload something from a device(below or above 100MB), everything is ok. It should be able to do the same when a file is uploaded from Google Drive.
Actual behavior
If i upload something bigger than 100MB, from Google Drive, i receive 413 http error. When a file lower than 100MB is uploaded, everything is ok again.
The text was updated successfully, but these errors were encountered: