MisterSparkle

Hello sirs, I am trying to get Bombvault to accurately back up some docker containers and associated files. There seems to be an issue however as Bombvault is not backing up to an off/on-site sftp server correctly. In the Bombvault docker logs, I seem to get a lot of these errors, below, and believe the issue may be related to it: 2026/10/10 15:20:45 api: offsite containers: copying folder container failed (continuing with the other sources): restic copy failed: error while unlocking: rclone stdio connection already closedFatal: context canceled 2026/10/10 15:20:45 api: offsite containers: copy to a destination failed (continuing): copying folder container: restic copy failed: error while unlocking: rclone stdio connection already closedFatal: context canceled 2026/10/10 15:20:45 api: offsite containers: copy failed (local backup is safe): copying folder container: restic copy failed: error while unlocking: rclone stdio connection already closedFatal: context canceled And in the activity log window on Dashboard, similarly: 10/10 15:20:45✗ContainersOff-site replication failed (Containers): copying folder container: restic copy failed: error while unlocking: rclone stdio connection already closedFatal: context canceled 10/10 16:31:42▶next: overdue-backup check at 09:00 (in 16h 28m) In the past it has run like this for over 12 hours with what appears to be no backup to the offsite device. In relation to the related info: Image tag is: junkerderprovinz/bombvault:latest Output of docker logs --tail 200 BombVault bombvault v9.9.1 · Backup & disaster recovery for Docker containers and KVM/libvirt VMs ✓ BOMBVAULT v9.9.1 IS READY - Open the WebUI now (HTTPS 3443) 2026/10/10 13:18:59 http: TLS handshake error from 192.168.8.158:53114: remote error: tls: unknown certificate 2026/10/10 13:18:59 mdns: announcing "BombVault (Metis)" as bombvault.local 2026/10/10 13:20:16 notify: unraid: sshconn: run "/usr/local/emhttp/webGui/scripts/notify": exit status 255 2026/10/10 13:49:48 http: TLS handshake error from 192.168.8.158:56758: remote error: tls: unknown certificate 2026/10/10 13:49:48 http: TLS handshake error from 192.168.8.158:52736: remote error: tls: unknown certificate 2026/10/10 13:50:44 api: backup: no progress for 30m0s. The backup is still running; if the target is a network share, check that it is still responding. 2026/10/10 15:20:44 api: backup: cancelled after 2h0m0s without progress. Nothing was written by the stalled attempt: restic writes its snapshot last, so an aborted run leaves unreferenced data and no snapshot. 2026/10/10 15:20:45 restic copy stderr: rclone: 2026/10/10 13:20:23 NOTICE: sftp: No host key validation is being performed. Set known_hosts_file (to "none" to silence this notice) or use --sftp-pin-host-key to enable it. See: https://rclone.org/sftp/#host-key-validation signal terminated received, cleaning up could not load snapshots: context canceled Remove(<lock/dcfeaf5ee3>) returned error, retrying after 635.406221ms: client.Do: Delete "http://localhost/locks/dcfeaf5ee355f767b4eb808672496a07b9f904a3a9d25908f11748a42f3389ae": unexpected EOF Remove(<lock/dcfeaf5ee3>) failed: rclone stdio connection already closed error while unlocking: rclone stdio connection already closedFatal: context canceled 2026/10/10 15:20:45 api: offsite containers: copying folder container failed (continuing with the other sources): restic copy failed: error while unlocking: rclone stdio connection already closedFatal: context canceled 2026/10/10 15:20:45 api: offsite containers: copy to a destination failed (continuing): copying folder container: restic copy failed: error while unlocking: rclone stdio connection already closedFatal: context canceled 2026/10/10 15:20:45 api: offsite containers: copy failed (local backup is safe): copying folder container: restic copy failed: error while unlocking: rclone stdio connection already closedFatal: context canceled 2026/10/10 16:21:13 http: TLS handshake error from 192.168.8.158:61061: remote error: tls: unknown certificate 2026/10/10 16:21:13 http: TLS handshake error from 192.168.8.158:64722: remote error: tls: unknown certificate 2026/10/10 16:21:13 http: TLS handshake error from 192.168.8.158:60277: remote error: tls: unknown certificate 2026/10/10 16:21:13 http: TLS handshake error from 192.168.8.158:64730: remote error: tls: unknown certificate Which domain (containers / VMs / flash) and what you were doing (backup / restore) I believe this issue is happening on Containers backup. For VM issues: the result of Settings → VM Backup over SSH → Test connection I don't believe this is a VM issue as I don't have any VMs and thus don't back them up. Browser + OS you're using I am using Windows 11 with latest version of Brave browser.

Hello #1: I have my router set to forward to the container using port 8080. #2: As far as I know Immich is listening on 8080. I can access locally via it. #3: my config is as you've listed but I have replacced with relative Duckdns name. Immich still is not accessible from mobile or outside the lan.

Hello, I'm not sure I have configured this Docker correctly. Sorry for my newish-user type question, but in the caddyfile config, there are references to PORT HTTPS as 8443 and PORT HTTP as 8080. I am trying to use this so that users (family) can just http://hostname.duckdns.org:PORT and be served with the Immich login screen. If I already have Immich on 8080 then do I need to change the caddyfile config to be a PORT HTTP different than 8080?