Backblaze Generic S3

  • Resolved GregF

    (@gregf)


    3 years, 11 months ago

    Using Generic S3 (compatible) settings for the new S3 API at Backblaze, I get the following error:

    S3 settings test result: Failure: We successfully accessed the bucket, but the attempt to create a file in it failed. Please check your access credentials. (UpdraftPlus_S3::putObject(): [AuthorizationHeaderMalformed] Authorization header does not contain a Credential)

    Thanks for any help.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor bcrodua

    (@bcrodua)

    3 years, 11 months ago

    Hi,

    Apologies for the late reply.

    Please can you make sure that you have entered the correct credentials?

    Regards,
    Bryle

    Thread Starter GregF

    (@gregf)

    3 years, 11 months ago

    I did double check them and if the error message is meaningful, the credentials allowed access to the bucket.

    Plugin Author David Anderson

    (@davidanderson)

    3 years, 11 months ago

    Hi Greg,

    Please could you ask Backblaze support to look into this? Our “Generic S3” module works with Amazon, DigitalOcean, Linode, Cloudian and loads of others. As such, the likelihood is that Backblaze’s initial release of S3 support is in some way subtly different to the “normal” S3 protocol. i.e. Isn’t fully compatible. The best people to look at that would be them at this stage – there’s a good chance that since they’ve just released this layer, that in the next few weeks they’ll iron out some bugs in it, so it’d probably be not the best use of our limited developer resources to dive in immediately (especially since we already have a fully-supported Backblaze add-on for their “regular” protocol).

    David

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Backblaze Generic S3’ is closed to new replies.