Problems with adding files over 15MB with progress handler

[salamantos]

I tried to create progress bar to my file uploading. I used this code:

let progress_func_video = function (len) { 
    console.log("video progress:", len); 
}; 
ipfs.files.add(files_video, {progress: progress_func_video}, (err, result) => {...}

When I upload 1MB files, it's ok, but on 30MB files I got this error in Chrome:

POST https://site.com:81/api/v0/add?progress=true&stream-channels=true net::ERR_INCOMPLETE_CHUNKED_ENCODING
Uncaught (in promise) TypeError: network error at new exports.IncomingMessage (response.js?99b5:67) at module.exports.ClientRequest._connect (request.js?af32:259) at eval (request.js?af32:157)

How to fix it?

[daviddias]

@salamantos mind creating a test that reproduces this issue?

[kliu128]

I get the same error, but on files > ~1 MB, through a nginx reverse proxy. Turning off progress fixes the issue. I get a timeout on the backend after 1 minute from nginx.

[lidel]

Hey, someone says "problem with ipfs.files.add + progressbar over HTTP API", I hear ipfs/kubo#5168 (and https://github.com/ipfs/js-ipfs-api/issues/797) 🙃

Are you able to check raw JSON response and confirm the error is go-ipfs returning http: invalid Read on closed Body OR that error goes away when you send with hardcoded Connection: close OR run custom go-ipfs build with fix from ipfs/kubo#5168 (comment)?

These days I strongly suspect all those random errors are related to ipfs/kubo#5168

[achingbrain]

js-ipfs is being deprecated in favor of Helia. You can follow the migration plan here #4336 and read the migration guide.

If the remote node you are talking to is Kubo, please switch out ipfs-http-client for kubo-rpc-client - it is a drop-in replacement and is where bug fixes and features will land going forwards.

If the remote node is js, please convert your app to Helia!