• Resolved sylvank

    (@sylvank)


    When attempting to back up to a bucket on Backblaze B2 that has object-lock enabled (I set the default for 30 days), the upload fails (log below). Without object-lock enabled appears to work fine.

    [20-Sep-2021 13:49:56] 1. Trying to generate a file with installed plugin names …
    [20-Sep-2021 13:49:56] Added plugin list file “WEBSITENAME.pluginlist.2021-09-20.txt” with 1.15 KB to backup file list.
    [20-Sep-2021 13:49:56] 1. Trying to generate a manifest file …
    [20-Sep-2021 13:49:56] Added manifest.json file with 2.41 KB to backup file list.
    [20-Sep-2021 13:49:56] 1. Trying to create backup archive …
    [20-Sep-2021 13:49:56] Compressing files as ZipArchive. Please be patient, this may take a moment.
    [20-Sep-2021 13:49:56] Backup archive created.
    [20-Sep-2021 13:49:56] Archive size is 1.80 KB.
    [20-Sep-2021 13:49:56] 3 Files with 3.78 KB in Archive.
    [20-Sep-2021 13:49:56] 1. Trying to send backup file to S3 Service …
    [20-Sep-2021 13:49:57] Connected to S3 Bucket “BUCKET-TestObjectLock” in us-west-000
    [20-Sep-2021 13:49:57] Checking for not aborted multipart Uploads …
    [20-Sep-2021 13:49:57] Starting upload to S3 Service …
    [20-Sep-2021 13:49:57] ERROR: S3 Service API: Missing required header for this request: Content-MD5

Viewing 4 replies - 1 through 4 (of 4 total)
  • @sylvank
    Thank you for reporting that, this is likely an issue on the BackWPUp side, I’m going to contact our devs about the object lock issue then back to you!

    Hello @sylvank
    hmm, I tried to reproduce the issue but I can’t, already enabled object lock on B2, the job still working fine.
    Please check my site here: https://prnt.sc/1tcub0z
    possibly a plugin conflict? could you just enable BWU then run the job again:?
    Thank you!

    Thread Starter sylvank

    (@sylvank)

    Hi, it looks to me like you haven’t enabled Default Bucket retention. See: https://help.backblaze.com/hc/en-us/articles/1260804786409-Default-Bucket-Retention-Immutability-

    My understanding is: that means that the files uploaded by BackWPUp don’t have object lock applied, because the plugin isn’t setting an object lock expiry time itself via the API (and I haven’t seen the option). You can check if the files are actually locked by browsing the files in your bucket and clicking the Info button which will show the Object Lock status, or attempting to delete a file.

    If you select the bucket settings and set a Default Bucket Retention time, the Info display on a newly-uploaded file should show the enabled Object Lock status & duration, as well as deletion now not being possible (if you select file then delete, it will alert you the file cannot be deleted).

    It is when a Default Retention is set that the above header Content-MD5 error is generated when attempting to run the backup job.

    My desire to use object lock is so that if a WordPress site is compromised, and the B2/S3 API key is extracted from the database, the site backups are protected from deletion by the hacker.

    Thanks for looking into this!

    Hello @sylvank
    Thank you I was able to reproduce the issue, reported it to our devs ^^

    My desire to use object lock is so that if a WordPress site is compromised, and the B2/S3 API key is extracted from the database, the site backups are protected from deletion by the hacker.

    hmm by default keys are encrypted in your database so hackers can’t get these keys.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘“Missing required header for this request: Content-MD5” – Object Lock, B2’ is closed to new replies.