Question

upstream connect error or disconnect/reset before headers. reset reason: overflow

Posted on October 27, 2023
DigitalOcean Spaces
Asked by nilesh kharad

why i’m getting this Err msg while accessing files from Digital-Ocean spaces bucket—> “upstream connect error or disconnect/reset before headers. reset reason: overflow”

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

alexdo

Site Moderator

• October 30, 2023

Heya,

This error message can be caused by a lot of things, but the most common reasons are:

Your internet connection is slow or unreliable. Make sure you have a good internet connection before trying to access your DigitalOcean Spaces bucket.
You’re trying to access a very large file. DigitalOcean Spaces has limits on the size of files that can be uploaded or downloaded. If you’re trying to access a file that’s too large, you’ll get this error.
You’re using the wrong access credentials. Make sure you’re using the correct access key and secret key to authenticate your requests to DigitalOcean Spaces.
Your proxy or firewall is blocking access to DigitalOcean Spaces. Make sure your proxy or firewall settings allow access to DigitalOcean services.
The software or SDK you’re using to access DigitalOcean Spaces is out of date or not configured correctly. Make sure you’re using the latest version of the software or SDK and that it’s configured correctly.

Here are some things you can do to try to fix this error:

Make sure you’re using the correct access credentials.
Avoid trying to access or upload very large files.
Check DigitalOcean’s status page for any ongoing issues with their services.
If you’re using a specific library or client, check the documentation and any available logs for more specific error information.

Hope that this helps!