Question
SPACES - How can I solve the <Error><Code>NoSuchBucket</Code>
- Posted on March 3, 2019
- Block StorageStorage
Asked by stevenfd06def5751af5729656
I’m setting up a file-share/storage and cannot get around this. The file-sharing script is on DO droplet, and ready for API credentials.
I’ve tried every configuration possible (I think). Error the same. Everything works perfectly when utilizing local disc.
Getting this in error logs:
Error executing “ListObjects” on “https://sfo2.digitaloceanspaces.com/https%3A%2F%2Fmedia-spdn.sfo2.digitaloceanspaces.com?prefix=2Lz71G4IIEkR8LKpIqwnMF7oB8Mz6ufWWeCqp3vd%2F2Lz71G4IIEkR8LKpIqwnMF7oB8Mz6ufWWeCqp3vd%2F&max-keys=1&encoding-type=url”; AWS HTTP error: Client error: GET https://sfo2.digitaloceanspaces.com/https%3A%2F%2Fmedia-spdn.sfo2.digitaloceanspaces.com?prefix=2Lz71G4IIEkR8LKpIqwnMF7oB8Mz6ufWWeCqp3vd%2F2Lz71G4IIEkR8LKpIqwnMF7oB8Mz6ufWWeCqp3vd%2F&max-keys=1&encoding-type=url resulted in a 404 Not Found response:
<?xml version=“1.0” encoding=“UTF-8”?><Error><Code>NoSuchBucket</Code><RequestId>tx000000000000020c02053-005c7b5e83-79b1 (truncated…)
NoSuchBucket (client): - <?xml version=“1.0” encoding=“UTF-8”?><Error><Code>NoSuchBucket</Code><RequestId>tx000000000000020c02053-005c7b5e83-79b1a-sfo2a</RequestId><HostId>79b1a-sfo2a-sfo</HostId></Error>
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.
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Hey friend,
Thank you for asking this question here. It looks like there is an error in your code which is causing the URL of your bucket to look like this:
Your bucket URL should look more like this:
Jarland