Skip to content
ConstellaWP Docs

Backblaze B2

Use Backblaze B2 through its S3-compatible API. In ConstellaWP, choose provider Backblaze B2.

Prerequisites

Section titled “Prerequisites”
  • A Backblaze account
  • Permission to create buckets and application keys
  • ConstellaWP role owner or admin

Steps

Section titled “Steps”

  1. Sign in to the Backblaze B2 web console.

  2. Create a private bucket. Note the bucket name and the region shown on the bucket (for example us-west-004).

    Backblaze: create a private bucket

  3. Open Application Keys and create a new key:

    • Restrict it to this bucket (least privilege).
    • Allow read, write, list, and delete.
    • Copy keyID and applicationKey immediately — the application key is shown once.
    Backblaze: create application key

  4. Copy the S3 endpoint for that region. It looks like https://s3.us-west-004.backblazeb2.com.

    Backblaze: S3-compatible endpoint URL

  5. In ConstellaWP, go to Storage → Add Destination:

    • Name: anything you will recognize
    • Provider: Backblaze B2
    • Fill the fields from the table below
    • Path prefix: backups unless you need another prefix
    • Save, then Test connection

Field mapping

Section titled “Field mapping”
ConstellaWP field Where to find it in Backblaze
Bucket Bucket name in B2
Region Bucket region, for example us-west-004. If omitted, ConstellaWP defaults to us-west-004
Application Key ID Application key keyID
Application Key Application key applicationKey (shown once at creation)
S3 Endpoint (optional) S3 endpoint, for example https://s3.us-west-004.backblazeb2.com. If empty, ConstellaWP builds https://s3.{region}.backblazeb2.com
Path prefix Chosen by you; objects are stored under {prefix}/{site id}/backup-….zip

Common errors

Section titled “Common errors”
Error Likely cause
Connection test failed / AccessDenied Key is not allowed to s3:PutObject / s3:DeleteObject on this bucket
NoSuchBucket Bucket name typo, or the key is scoped to a different bucket
Wrong region / endpoint Region and endpoint must match the bucket (for example us-west-004 with https://s3.us-west-004.backblazeb2.com)
Invalid key Pasted the master application key by mistake, or copied keyID into the secret field