2 hours ago, BJZwart said:

Installed BombVault and it looks great, one issue ran into.

I don't use any VM backup but every time I open the Gui this error appears in the containers log.
error: Cannot recv data: ssh: Could not resolve hostname 192.168.x.x: Name or service not known: Connection reset by peer

Hey, thanks for the kind words and the report!

That SSH error was BombVault checking for libvirt VMs on every page load, even when you don't use VM backup. Fixed now: it only talks to libvirt when the VMs domain is turned on. Update to the latest image and the log should be clean.

I'm trying to get Off-site copy to Backblaze B2 working.
I have added the rclone config and tested that it sees all buckets.
I now have the rclone.conf file in the appdata folder but what do I now set as path in Off-site copy?

My rclone config is called [BackBlaze] and the bucket BombVault-test.

I tried using BackBlaze:BombVault-test no errors in the container log but nothing is uploaded to Backblaze.

Edited July 2Jul 2 by BJZwart

4 hours ago, BJZwart said:

I'm trying to get Off-site copy to Backblaze B2 working.
I have added the rclone config and tested that it sees all buckets.
I now have the rclone.conf file in the appdata folder but what do I now set as path in Off-site copy?

My rclone config is called [BackBlaze] and the bucket BombVault-test.

I tried using BackBlaze:BombVault-test no errors in the container log but nothing is uploaded to Backblaze.

Hey! The path just needs the rclone: prefix so restic uses rclone instead of treating it as a local folder. That's why it ran without errors but nothing showed up on B2 (it was quietly writing to a local path named BackBlaze:BombVault-test).

Set the Off-site copy path to: rclone:BackBlaze:BombVault-test

The format is rclone:<remote>:<bucket>, using the exact remote name from your rclone config (BackBlaze here). Keep pasting the rclone config into BombVault's Rclone settings card (not just dropping it in appdata) so it wires the config into restic; since it already lists your buckets, that part looks good. The B2 repo will initialize itself on the first off-site copy.

Give that a shot and let me know if it still doesn't push!

Thanks, yes it's working now.

Buckets are filling up nicely.

Love this tool, been posting on git as ptmorris1 but wanted to informally request: under dashboard, Last Backups, if it could have start and end time?

Also under the container domain, a search filter. I have a lot of them.

Not sure if you prefer these on git or here?

Thanks!!

Thanks @phunky1, really glad it's useful to you!

Both of those are good ideas:

- Start and end time on the Dashboard "Last Backups": an easy one, since each run already records when it started and finished, so showing the times (and the duration) there is straightforward.

- A search/filter box on the Containers tab: agreed, once you have a lot of them the list gets unwieldy.

On where to post: GitHub is the better spot for feature requests and bug reports.

Filed as issues they don't get lost in the thread and I can track them properly, so if you don't mind dropping these two into separate issues over at github.comjunkerderprovinz/bombvault/issues that would be perfect. I've noted them down in the meantime either way.

Thanks again, and thanks for all the reports as ptmorris1, they've been genuinely

helpful.

Edited July 6Jul 6 by Junker der Provinz

I’ve been using BombVault for a while now and have been very happy with both its functionality and the frequency of updates so great work! That being said Is there currently a way to configure the order in which containers are stopped, backed up, and restarted to account for service dependencies? I know it uses a per-container option to stop other dependent containers during a backup, but I’m not sure whether that can also control the overall restart order or wait for a dependency to become healthy before continuing. In my case, Nextcloud was restarted 36 seconds before Pi-hole, and Authelia was restarted more than 12 minutes before Pi-hole. Both failed to start because pihole was not yet available and they remained stopped afterward. Authelia also protects my Pelican panel and Wings web endpoints, so its failure made the game-server management stack inaccessible until I manually started panel/wings some time later. Is there a way to set the startup order such as Pi-hole first, then wait for it to become healthy, followed by Authelia, Nextcloud, Pelican, and other dependent services? If not it would be extremely useful.

Hey @Kazem , thanks for your kind words. I'll look into it next week when I'm back home and give you some more details then. I'm always glad to see feature requests on BombVaults GitHub site, since it's easier for me to stay on top of everything there. Feel free to open an Issue there if you want to.