Receiving "SignatureDoesNotMatch" errors when using Spaces with Transmit 5.0

Posted September 15, 2017 4.1k views

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?


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

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

cc @johngannon

  • 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.

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.

@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?

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:

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