We’re encountering an authentication error while trying to upload files to Storj via the S3-compatible API from a self-hosted Kerbero Vault. The error occurs consistently during object uploads, and we’d appreciate your guidance to resolve it.
> [ERROR] POST /api/storage 400 | Header 'x-amz-content-sha256' mismatch
Endpoint:POST /api/storage (via Kerberos Vault ). When It Happens: Immediately after attempting to upload any file.
Environment
Storj Configuration:
Access Key: REDACTED
Secret Key: REDACTED
Region: global
Bucket: REDACTED (already created).
Have you encountered similar issues (x-amz-content-sha256 mismatch) in integrations with Kerberos Vault?
Is it possible to access request logs/debug traces for our Storj bucket?
Hello @Alexey
I’m sorry, I didn’t mention it. Yes, I did use `gateway.storjshare.io ’
In the “Storage Providers” configuration in Vault, I get a “Configuration is valid and working” message.
Hello @hydr
I’ll try a downgrade Vault version. Just in case, do you know what the last working Vault version is?
I saw the issue on their GitHub, and I think x-amz-content-sha256 header mismatch happens due to a 0 length uploaded object, and of course it would fail the check.
The more interesting, that it gets 400 Bad Request on upload requests, I believe this is a culprit of the issue.
Could you please try to configure it as a Minio provider? You would need to enable SSL and provide the hostname gateway.storjshare.io, the Access Key and the Secret Key which you got from the Storj Console when you created S3 credentials.