Receiving "SignatureDoesNotMatch" errors when using Spaces with Transmit 5.0

September 15, 2017 233 views
API Storage

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?

3 comments
  • Hi @jeremyfuksa would you mind sharing where/hoe you generate proper the equivalent of the key/secret in Digital Ocean? I am trying as well using Transmit and s3cmd but with no luck.

    Thanks!

  • I am also having this issue. Did you get it resolved? I have regenerated keys and tried that, but am still getting this error.

  • No, still same error. The key/secret works fine with s3cmd though, so it must be a problem Transmit 5. Need to file a support ticket with them.

3 Answers

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?

Have another answer? Share your knowledge.