DavRoll setup guide
Connect B2, R2, Wasabi, or MinIO as an S3 backup
Use the provider preset to select addressing and region defaults, then enter the real endpoint and bucket-scoped keys shown in the provider console.
Connection steps
- Open Settings → Backup location → Advanced storage → S3 in DavRoll.
- Select the Storage provider and compare the preset with the console values.
- Enter the bucket, optional prefix, access key, and secret key.
- Tap Test and save to verify the real bucket connection.
- Run a small manual backup, then confirm the Verified state and browse it in Restore Center.
| Provider | Endpoint / region | Addressing |
|---|---|---|
| Backblaze B2 | https://s3.<region>.backblazeb2.comExample region: us-west-004. Copy both values from Buckets. | Path-style preset |
| Cloudflare R2 | https://<ACCOUNT_ID>.r2.cloudflarestorage.comregion: auto | Path-style preset |
| Wasabi | https://s3.<region>.wasabisys.comUS East 1: https://s3.wasabisys.com / us-east-1 | Path-style preset |
| MinIO | The public HTTPS API endpoint supplied by the operator default region: us-east-1 | Path-style preset |
Provider preparation
Backblaze B2
Copy the S3 endpoint and region from Buckets. In App Keys, create an application key restricted to the target bucket. Enter keyID as the access key and applicationKey as the secret key. Official Backblaze S3-compatible API guide
Cloudflare R2
Create a bucket, then create an API token with Object Read & Write permission for that bucket only. Copy the S3 API endpoint from the token result or R2 Overview and use auto as the region. Official Cloudflare R2 S3 guide
Wasabi
Use the service URL and region that exactly match the bucket location. Prefer bucket-scoped sub-user keys instead of root keys. Official Wasabi region URL list
MinIO
DavRoll accepts HTTPS endpoints only, so the externally reachable API endpoint needs a valid TLS certificate. Enter the S3 API endpoint rather than the Console address, and restrict a dedicated user or service account to the target bucket.
If connection testing fails
- Signature error: confirm the endpoint and region refer to the same bucket location.
- Access denied: review bucket list, object read, upload, and multipart permissions.
- DNS or addressing error: keep the preset's Path-style setting and do not repeat the bucket name in the endpoint.
- TLS error: check the certificate host name, expiry, and intermediate chain.