Question

Receiving "SignatureDoesNotMatch" errors when using Spaces with Transmit 5.0

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?

Show comments

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!

Sign In or Sign Up to Answer

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.

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

cc @johngannon

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.

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