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?
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.×