Backblaze as Remote error Unsupported header 'x-amz-checksum-mode' received for this API call.

mguimond

When im trying to connect to my backblaze to configure a remote in xen orchestra I'm getting the following message. I'm able to connect with my credentiel with cyberduck.

{
  "name": "InvalidArgument",
  "$fault": "client",
  "$metadata": {
    "httpStatusCode": 400,
    "requestId": "4c022d6f8b1e258a",
    "extendedRequestId": "aNHQx6DCwZa1j6jhRM8s3OjQNYk0zvDkM",
    "attempts": 1,
    "totalRetryDelay": 0
  },
  "Code": "InvalidArgument",
  "message": "Unsupported header 'x-amz-checksum-mode' received for this API call."
}

Can anynome help me solved this ?

Thank You.

florent

thanks for pointing the exact issue in the aws SDK. It gave use enough matter to find the fix

DustinB

@mguimond Is your B2 bucket already created and waiting? Using CyberDuck you're able to authenticate to the web front, but is there already a bucket sitting there?

mguimond

@DustinB Yes the bucket exist. I'm able to connect and create folder.

DustinB

@mguimond While I have mine disable, I was able to connect without issue, are you able to confirm yours looks similar?

mguimond

@DustinB when i disable it I can't connect it.

I use the from source version

This one work correctly. this is another customer with a older version.
Xen Orchestra, commit fa974
Master, commit b3d66
You are not up to date with master. 221 commits behind

DustinB

@mguimond said in Backblaze as Remote error Unsupported header 'x-amz-checksum-mode' received for this API call.:

master. 221 commits behind

The version that is 221 updates behind works, but your current version does not?

mguimond

@DustinB That is correct.

DustinB

@mguimond Could be a bug in a recent release, @Danp are you aware of anything?

Danp

@DustinB No, but dev team has been notified so that they can investigate.

jr-m4

I submitted this as a GitHub issue last week.

TL;DR: Backblaze aparently doesn't support those flags that are enabled by default
"Backblaze does not yet accept these headers, so we recommend downgrading to AWS Javascript 3.x SDK version 3.728.0."

https://github.com/vatesfr/xen-orchestra/issues/8358

cloudrootab created this issue in vatesfr/xen-orchestra

open S3 Backup: "Unsupported header 'x-amz-checksum-mode' received for this API call." #8358

florent

@jr-m4 nice find . thank you

florent

@mguimond @jr-m4 I would like to be able to keep the library up to date.
Would it be possible to patch a file in your install ? and check if the backup run It will disable the checksum computation .

Note that if you use backup encryption, the checksum are already checked on restore

you can either use this branch : fix_s3_backblaze or modify directly the code in your installation in <xo>/node_modules/@xen-orchestra/fs/dist/s3.js

replace :

 requestHandler: new _nodeHttpHandler.NodeHttpHandler({
        socketTimeout: 600000,
        httpAgent: new _http.Agent({
          keepAlive: true
        }),
        httpsAgent: new _https.Agent({
          rejectUnauthorized: !allowUnauthorized,
          keepAlive: true
        })
      })

by

 requestHandler: new _nodeHttpHandler.NodeHttpHandler({
        socketTimeout: 600000,
        httpAgent: new _http.Agent({
          keepAlive: true
        }),
        httpsAgent: new _https.Agent({
          rejectUnauthorized: !allowUnauthorized,
          keepAlive: true
        })
      }),
      requestChecksumCalculation: "WHEN_REQUIRED",
      responseChecksumValidation: "WHEN_REQUIRED"

(the difference is

,
      requestChecksumCalculation: "WHEN_REQUIRED",
      responseChecksumValidation: "WHEN_REQUIRED"

probain

@florent said in Backblaze as Remote error Unsupported header 'x-amz-checksum-mode' received for this API call.:

,
requestChecksumCalculation: "WHEN_REQUIRED",
responseChecksumValidation: "WHEN_REQUIRED"

I (previously as @jr-m4) just tried the patch you suggested. And I can confirm that this does indeed make the backup complete successfully!
Great work finding a solution that quicklly!

olivierlambert

Great example on how great the community is and how fast our dev can fix it! Thanks for the feedback, it really matters, as you can see!

florent

thanks for pointing the exact issue in the aws SDK. It gave use enough matter to find the fix

mguimond

@florent Sorry for the delay. I was able to make it work with the change you posted. Thank You.