- ✅ Dropbox
- ✅ Google Drive
- ✅ SFTP
- ✅ FTP
- ✅ Local
- ✅ S3 Amazon
- ✅ DigitalOcean spaces
- ✅ Any S3 service
- ✅ rsync
@Terry Upton Would you kindly share how you got B2 to work? When I put the B2 endpoint in the field, I get this message "The credentials.region must start with "http"". I have tried putting "http", "http://", and "https://" in front of the endpoint name, but that cause this message to appear: "We are unable to authenticate with your S3 bucket, please check the credentials (also check if you need a path styled endpoint)." This makes me wonder if the data I entered elsewhere is in the correct fields. Thanks in advance.
Hi @Terry Upton,
Can you let me know how you have done this please? @Dennis, is this still being worked on perhaps? I would ask on Discord but I am not sure if you are still using it.
Edit: This works with Custom S3 following Backblaze's instructions, so yeah this should be assumed as working! Awesome! :)
Thanks!
Merged Synology Drive backup driver into this item
Created by: Nathan Geerinck
At home I do have a Synology NAS, it would be awesome to choose the Synology Drive application as backup destination for database and file backups.
I am updating this thread with the Backblaze B2 configuration that works. The "Region name" must either be EMPTY or contain a valid region name, not a random label. The best option is probably to just leave it blank. Settings that work are: Ploi field / Value Label / Anything descriptive, such as Backblaze B2 EU Central Access key / Backblaze keyID Access secret / Backblaze applicationKey (cannot be your master application key) Bucket name / Your exact bucket name Region name / eu-central-003 (for EU Central, or LEAVE BLANK) Endpoint https://s3.eu-central-003.backblazeb2.com
