hicetnunc
hicetnunc copied to clipboard
hicetnunc2000
Minting silently fails with net::ERR_EMPTY_RESPONSE during file upload to IPFS via Infura.io
Describe the bug After submitting a fairly large file to upload (13 or 20MB), this user was getting mint hanging during IPFS upload phase. This caused the mint screen to hang forever with "preparing OBJKT" message.
Console reports error message from Infura: Failed to load resource: net::ERR_EMPTY_RESPONSE from ipfs.infura.io:5001/...ue&progress=false:1 (full path not discernable from user's screenshot)
https://discord.com/channels/759930487946215444/821700631365943317/830189539296935941
To Reproduce
- Go to 'mint', enter details, select ~20MB GIF file
- Click on 'preview'
Expected behavior UI should indicate that it's at the step of uploading file to IPFS UI should report the error message and/or other information to the user to assist with debug File should be correctly loaded.
Screenshots See screenshot
Desktop (please complete the following information): See discord - user tried on both Brave & Chrome
Additional context Add any other context about the problem here. Please include the wallet address (tz...) and/or the OBJKT number.
It's possible that this may be an environment issue (eg local network dropout), and it might be useful to trap the error and retry the transaction a few times.
Seems to be other apps experiencing same issue - https://github.com/ipfs/js-ipfs/issues/3555
I'm getting the same error while trying to mint a large 38mo mp4 file (so under the 40mo limit). I tried both on Chrome and Firefox. However the error I got in Firefox is slightly different as it mention a "cross-origin" problem...
Also the infura full path mentionned above is visible on my Firefox screenshot:
https://ipfs.infura.io:5001/api/v0/add?stream-channels=true&progress=false
same with this .glb file: https://www.dropbox.com/s/4yk892iagy8bl9e/Untitled_Scan_21_24_30.glb?dl=0
Some users have similar issues here: https://community.infura.io/t/err-empty-response/2484/8
Some workarounds are mentioned in that forum post
Thank you, I have solved it for myself at least. Simply find a faster internet connection and it worked.
