Skip to content

Backblaze B2

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

Backblaze does not show a Region field. The bucket page lists Endpoint (for example s3.us-east-005.backblazeb2.com). Paste that into ConstellaWP; the region is derived from the hostname.

  • A Backblaze account
  • Permission to create buckets and application keys
  • ConstellaWP role owner or admin
  1. Sign in to the Backblaze B2 web console.

  2. Create a private bucket. Note the bucket name.

    Backblaze: create a private bucket
  3. Open the bucket. Copy Endpoint — it looks like s3.us-east-005.backblazeb2.com. Do not use api.backblazeb2.com.

    Backblaze bucket page: Endpoint s3.us-east-005.backblazeb2.com
  4. 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
  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
ConstellaWP field Where to find it in Backblaze
Bucket Bucket name in B2
Application Key ID Application key keyID
Application Key Application key applicationKey (shown once at creation)
S3 Endpoint Endpoint on the bucket page, for example s3.us-east-005.backblazeb2.com. https:// is optional
Path prefix Chosen by you; objects are stored under {prefix}/{site id}/backup-….zip

There is no Region field. s3.us-east-005.backblazeb2.com means region us-east-005; ConstellaWP reads that from the endpoint.

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
Paste the Endpoint from the B2 bucket page Native API host (api.backblazeb2.com) or a website URL instead of the S3 Endpoint
Invalid key Pasted the master application key by mistake, or copied keyID into the secret field