Problem settting up remote backup with Backblaze

I have entered the bucket name, key ID and application Key. I have also generated the appplication key multiple times but I still get this error message when I click save. What could be the problem please?

Checking the error log. Here is what I found.

In order to get this working you must setup rclone, a remote host, then add that backup host to hestiacp.

rclone config

very rclone is working:

rclone lsd my-s3:your-bucket-name

add the instance to hestiacp

v-add-backup-host ‘rclone’ ‘my-s3’ ‘’ ‘’ ‘your-bucket-name’ ‘’

test it

v-backup-user admin

I believe Rclone is different. I am setting up BackBlaze which does not required Rclone.

Actually, you are correct, I am mistaken, hestiacp seems to include a Backblaze now. So perhaps you have an issue with the endpoint format?

The docs says it automatically resolves the endpoint, however, it doesn’t seem to be working.

I would try it with rclone if I needed it. I don’t see any reason not to stick with restic for now.

Ok, from the command line it seems to work:

Backblaze B2 (native)

v-add-backup-host ‘b2’ ‘my-bucket’ ‘keyID123’ ‘applicationKey456’

yeah, that worked:

-- SUMMARY –
2026-09-07 21:07:43 Upload to B2:

Don’t forget to turn Local Backups off in the panel.

Also set the number of backups to retain in the Package settings.

It is a bug

This should fix it…

B2 was supported way before Rclone was. But Rclone also support B2 as backup host…

Oh! You fixed it, nice! How long will it take for that to be merged with the distributed branch? I am in no hurry just curious about the process, thanks!

ok I see it is already in Main and there was a service release two weeks ago, so it should be in the next release whatever type it is:

In Main: hestiacp/bin/v-add-backup-host at main · hestiacp/hestiacp · GitHub

Last service release: Release [1.10.4] Service release · hestiacp/hestiacp · GitHub