You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While using this in my project and having mutliple uploads from various instances, some of them are just not working and are producing this error:
Request failed on attempt 3 (HTTPSConnectionPool(host='blob.vercel-storage.com', port=443): Max retries exceeded with url: /output.mp4 (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7fbceb6fd8d0>, 'Connection to blob.vercel-storage.com timed out. (connect timeout=10)')))\n
There are in total 3 retries happening and all of them fail all the time. I wonder what could be the issue here?
I have seen that others vercel/storage#595 switched to sending a buffer instead of the file, but I did this in my code as well, but the issue is still there.
@SuryaSekhar14 maybe you have an idea what could be wrong here?
The text was updated successfully, but these errors were encountered:
The code tries to upload the file buffer itself, and not the file as a whole. You need to open the file in binary mode before uploading it. But yes, the connection was never consistent when I created this wrapper, hence I added the retry mechanism.
This might be due to the fact that Vercel Blob Storage is still in Beta, or they might be doing something like multipart uploads. However, it is difficult to know for sure, without getting access to their API Docs.
While using this in my project and having mutliple uploads from various instances, some of them are just not working and are producing this error:
There are in total 3 retries happening and all of them fail all the time. I wonder what could be the issue here?
I have seen that others vercel/storage#595 switched to sending a buffer instead of the file, but I did this in my code as well, but the issue is still there.
@SuryaSekhar14 maybe you have an idea what could be wrong here?
The text was updated successfully, but these errors were encountered: