Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
rclone NoSuchKey status code: 404 Question Question
SPACES - How can I solve the <Error><Code>NoSuchBucket</Code> Question Question

Question

Receiving "SignatureDoesNotMatch" errors when using Spaces with Transmit 5.0

Posted September 15, 2017 4.1k views
APIStorage

I just set up a Space and am attempting to use Transmit 5.0 to access it.

I’ve used the information in my control panel to set up my Spaces login as an S3 instance in Transmit. And, it successfully logs in.

However, when I try to access the root bucket, I get a “SignatureDoesNotMatch” error. My Space is set to read/write and should be publicly viewable.

Thoughts on what’s up?

Add a comment
jeremyfuksa
By:
jeremyfuksa

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
rclone NoSuchKey status code: 404 Question Question
SPACES - How can I solve the <Error><Code>NoSuchBucket</Code> Question Question
Add a comment
3 comments

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.

×
Submit an Answer
5 answers
itsnyd3ll November 1, 2017

I’m no longer seeing this issue in the latest release. It seems to have been fixed.

cc @johngannon

Reply Report
  • johngannon November 1, 2017

    Yup - Transmit release 5.0.5 includes a fix specific to S3 compatible object stores, so this issue is no longer an issue :) Thanks for updating everyone who is on this thread.

    Reply Report
jasonj September 16, 2017
[deleted]
Reply Report
jeremyfuksa September 19, 2017

If you go into the API settings of your control panel, you’ll see a section for Spaces access keys. You can do it there.

Reply Report
arnaudsj September 19, 2017

@jeremyfuksa, thank you for responding. Yes, I did this that. But it only provide the accesskey, what about the secretkey (the second part, required to access AWS S3 as well). Am I missing something in the UI?

Reply Report
johngannon October 2, 2017

Hi everyone - I’m the product manager for Spaces.

Transmit 5 is not supported at the moment in Spaces (known issues).

However, we do have a tutorial for using Transmit 4 with Spaces here: https://www.digitalocean.com/community/tutorials/how-to-manage-digitalocean-spaces-with-transmit-4

Hope this helps and please continue to share your feedback about the product.

Reply Report

Related

Looking for something else?

Ask a new question Search for more help