Failed because: Error: tus: failed to upload chunk at offset 195035136 about tus-js-client HOT 6 CLOSED

First of all, I want to thank you for this detailed explanation and, in particular, the screenshot. Here's what I believe is happening: The long running uploads (the PATCH requests) get, at some point, interrupted. I cannot exactly tell why, with the information you provided, but there are quite a lot of reasons. Anyway, the tus protocol has been engineered with these incidents kept in mind and provides a way to resume directly after the interruption.

Now here's the deal: the tus-js-client demo (the page you have opened in Firefox) will not automatically resume and will always ask you before doing the actual resume. This is why pressing the OK button always will, in the end, result in a complete upload. On our soon roadmap is an entry which will add automatically resuming to tus-js-client meaing the script can handle these cases without user interaction.

I hope this answers helps you :)

from tus-js-client.

Thank you for you repply!

I did try increase the timeout via parameters in tusd but them same error occurs yet.

Again, executing the upload process, now in Google Chrome, in colsone tab I fount the error above:

from tus-js-client.

A connection reset error is sadly not very helpful. Does the output of the tusd process revile something about misbehavior? Could you please post it's output here?

from tus-js-client.

In tusd output don't have nothing to help us

I am thinking that can be a problem with proxy of the my company.
Today, in home, I will test in a EC2 server and post results here.

Thank you!

from tus-js-client.

Indeed, the tusd output is not helpful in this case. Furthermore, I agree with out that any proxy in between may cause these interruptions. However, as I said, these should not matter anymore once we implemented automated resuming as described above.

from tus-js-client.

The 1.4.1 release of tus-js-client has been published and contains the automated retries feature I have mentioned the last times. This should eradicate the issues you were experiencing. Since this has also been deployed to tus.io/demo.html, I would be pleased if you could give it a try.

from tus-js-client.