Content-MD5 HTTP header is required for Put Object requests with Object Lock parameters

KB ID: 4806
Product: Veeam Backup & Replication | 13
Published: 2026-01-08
Last Modified: 2026-01-08
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

Jobs targeting an S3-Compatible repository fail with either of the following errors:

Error: S3 error: Content-MD5 HTTP header is required for Put Object requests with Object Lock parameters Code: InvalidRequest Agent failed to process method
S3 error: Checksum Type mismatch occurred, expected checksum Type: null, actual checksum Type: sha256

Cause

Starting in Veeam Backup & Replication 13.0.1, the software now utilizes the SHA256 algorithm for hash calculation when signing API requests to S3 storage systems.

SHA256 is supported by AWS (as stated in their documentation), but not all S3-compatible storage systems implement SHA256, instead relying on the obsolete MD5.

Solution

Option 1: Enable SHA256 Support on Storage

For on-premises storage devices, review the settings to determine if the option to use compliant SHA-256 hashing is available. If this option is not available, we encourage you to contact your storage vendor for assistance in determining if newer firmware is available that includes SHA-256 hashing or if it will be available in an upcoming firmware release.

Option 2: Enable Legacy MD5 Hashing in Veeam Backup & Replication

If SHA-256 hashing cannot be enabled on the S3-compatible storage or is not available, Veeam Backup & Replication can be configured to re-enable the legacy MD5 hashing method.

Notes:

  • The default value is 0, and setting it to 1 enforces the MD5 hashing method.
  • This does not create a failover from SHA256 to MD5; it wholly changes all S3 content hashing from SHA256 to MD5.
This setting must be configured on the Veeam Backup Server (Windows-based Veeam Backup & Replication) or Veeam Software Appliance (Linux-based Veeam Backup & Replication)as well as on every Gateway server that interacts with the S3-Compatible storage.
For Veeam Backup & Replication on Windows and Windows-based Gateways

Create the following registry value:

Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: S3UseMd5ContentHash
Value Type: DWORD (32-Bit) Value
Value Data: 1

New-ItemProperty -Path 'HKLM:\SOFTWARE\Veeam\Veeam Backup and Replication\' -Name 'S3UseMd5ContentHash' -Value "1" -PropertyType DWORD -Force
For Veeam Software Appliance and Veeam Infrastructure Appliances (JeOS)

Modify the following configuration file and set the indicated value:

Configuration file: /etc/veeam/veeam_backup_and_replication.conf
Section: [root]
Setting: S3UseMd5ContentHash=1

For more information on applying custom settings on the Veeam Storage Appliance, please review:
KB4779: Applying Custom Settings to Veeam Software Appliance

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.