Skip to content
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

Connection to blob.vercel-storage.com timed out #15

Open
TimPietrusky opened this issue Dec 10, 2024 · 1 comment
Open

Connection to blob.vercel-storage.com timed out #15

TimPietrusky opened this issue Dec 10, 2024 · 1 comment

Comments

@TimPietrusky
Copy link
Contributor

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?

@SuryaSekhar14
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants