Recently I’ve faced some problems with a Space Bucket using the endpoint https://sfo3.digitaloceanspaces.com since I cannot add new files directly in the
Upload button or with the AWS sdk
I’ve created another Space Bucket using
nyc3 region as endpoint (https://nyc3.digitaloceanspaces.com) and all seems to be working correctly, I can add files directly or with
s3 without any problem.
Also checking the URL: https://sfo3.digitaloceanspaces.com/
this returns that the site cannot be found. Using
curl I get:
curl: (6) Could not resolve host: sfo3.digitaloceanspaces.com
I wonder if this is a temporary problem with that endpoint (since the other endpoints seems to be working correctly) or if I should migrate my current files to the new Bucket (with
Also, my current Droplet and Database Cluster are using the
sfo3 region and both are working correctly. So I also wonder if there is no problem by having the Bucket in
nyc3 region and my Droplet and Cluster in
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.
Click below to sign up and get $200 of credit to try our products over 60 days!
If you experience a problem with the sfo3.digitaloceanspaces.com endpoint and if the error is the same -
could not resolve hostyou can check if there is a reported problem with the endpoint on our status page.
I’ll check this internally and will report back here if there are any problems.
I currently don’t see any active incidents regarding the SFO3 datacenter on the DigitalOcean status page:
Are you still seeing the problem? If so please reach out to our amazing support team who will be more than happy to assist you with this issue!
Hope that helps!