BombVault 10.6.0 moves into the fortress, and it brings the neighbors along. Your apps finally talk to each other, and one phrase opens the whole house. ShipLog and TowerTorch ask for a backup before they touch a container, FireSquire checks when the flash was last saved, and the apps in your containers hand BombVault a backup of their own. On top of that, several servers can share one repository, and any file can be found by name in every backup. Read Breaking changes before you update, because this one likes company: the whole group moves at once.
🎉 Yes, we did it: BombVault is on Google Play. Thank you to everyone who kept it installed through the closed test, used it for real and told us what broke. You got it there.
⚠️ Breaking changes
- Update every BombVault of a group and the phone app together. Pairing runs on new groundwork, and an older version cannot reach a group that has moved on. Once all of them are updated, they find each other again by themselves, and the Instances card names any device that still runs an older version.
- The phone app pairs by the twelve words alone. Servers it kept by address leave the list on its first start. The app names them once, with a button to scan the phrase and bring the whole group back.
- BombVault needs Docker 19.03 or newer. It talks to Docker through the maintained client now, which leaves older engines behind.
- There is no way back. An older version refuses to start on the updated database. If you want a way back, export your settings first under Settings, System, or copy the appdata folder with the container stopped.
✨ Added
- BombVault joins a fortress. Enter the fortress's twelve words under Settings, Pairing, and BombVault joins your other apps there. The instances and phones it is paired with come along, and one that was away follows once it is back. The old pairing stays open for 30 days at most, and a device still missing after that is named on the Pairing page and in the app, so you can bring it in with the phrase or remove it. Thanks to @Revan335 for the idea. (#434)
- One phrase for everything. The twelve words that pair your BombVaults open the fortress as well, so another app given the same words finds BombVault right there. A group that was paired before takes its phrase into the fortress on its own, and leaving takes the instance out of both.
- Every permission between apps has its own switch. The Pairing page shows what the other apps of your fortress may do at BombVault, each with a switch of its own. An app only gets to do what it named when it joined, and anything else is turned away.
- The fortress sits on top of the Pairing page. One card holds the instance's name, the phrase and the buttons to show it, change it or leave, with the switch for the other apps at its end. Leave the name empty and BombVault goes by your Unraid server's name. The other apps follow in cards like the ones on the Instances tab, each with its own logo and a switch per permission.
- Take an app out of the fortress. Every other app's card has Remove, and the window names app and device before anything happens. Once it is out, the fortress lets no new app in until the phrase changes, so BombVault offers to change it right away. A BombVault that enters the phrase before then says why it can't get in, instead of joining a fortress with nobody in it. Until you do, the card names who was taken out, even after a restart, and an app that was taken out says so on its own page. A paired phone can't remove anyone.
- Open any app of your fortress from anywhere. Open on another app's card shows that app's own pages, directly at home and through the relay when you're out, without a single forwarded port. Each app has its own permission for it, and its own sign-in still guards the door. A plugin's pages sit behind Unraid's login, so a plugin opens as a window with its state, its work and its latest log lines.
- Show or change the phrase, or leave the fortress. The words appear once you enter your password, beside a QR code for the app that wants to join. A new phrase reaches every app and instance in reach, and any it missed are named, so you know where to type the new words. A member that was away during the change still finds its way to the new phrase for 30 days, and the window that changes it tells you so. A newcomer who still holds the old phrase finds nobody at all.
- The apps back themselves up. When an app in your fortress can back itself up, BombVault fetches that backup right before it backs up the app's container and keeps it with the container in an encrypted repository. It ages, goes off-site and is deleted along with the container's other backups, and you can download it from the container's list.
- Give a backup back to an app. From the container's list of backups you can hand an app the backup it made of itself, and the app swaps what it holds for it. That replaces the app's current data, so its switch on the Pairing page stays off until you turn it on. One switch per app is all it takes.
- Other apps check before they change something. FireSquire, ShipLog and TowerTorch can see when the last backup worked, look through a container's backups and ask for a fresh one, and BombVault waits if another backup is running. While ShipLog runs on the same server, it updates its own containers after BombVault has backed them up.
- A status for the other apps.
GET /api/fortress/v1/statusandGET /api/fortress/v1/logtell how the backups stand, what needs you, what runs and what comes next, in the language the reader asks for. An API token or a signed-in browser can read them, and nobody else can. - Shared repository. An instance with a receiving server can hold one shared repository for its group, so files that sit on several servers are stored only once. The others ask to join under From your group and you let them in on the Instances page. Each copies only its own backups in, through an append-only login of its own, and only the server that holds it prunes. Thanks to @Revan335 for the idea. (#419)
- Upkeep in one place. The window of the receiving server shows how much space the shared repository saves, when it tidies up and how long it keeps each server's backups. Before a prune it tells the others, and they hold their copies back until it is done. Its holder can copy its own backups in as well, and forget what a server left behind once you type that server's name.
- What the members see. The Instances page lists the shared repositories this server copies into, with who prunes them, who else is in, how much space they hold and save, and when the owner tidies up next.
- Restore from other servers. Under Other servers on the Restore page you get back what the other servers of a shared repository saved there, each shown with its name and host.
- Jobs from Duplicati or Duplicacy. Other sources on the Restore page reads jobs exported from Duplicati, a Duplicacy CLI folder or the settings of Duplicacy Web, and turns each job into folder sets with its folders, exclusions, schedule and storage place. A preview shows what each job becomes first. Thanks to @Revan335 for asking. (#418)
- Find a file. The Restore page has a Find a file card. It searches every backup of your containers, folder sets, ZFS datasets and the flash drive for a file name, lists each backup that holds it with date, size and place, and opens the restore window with just that file ticked. The MCP server has a
search_filestool for the same search. - System junk excludes. A new folder set suggests leaving out
.DS_Store,Thumbs.db,desktop.ini,@eaDir,.Recycle.Bin,.Trash-*and*.tmp, each with its own switch. An existing set stays as it is until you add them in its editor. - Connections per storage location. A storage location on S3, B2, REST, SFTP, rclone or another network backend can set how many connections restic opens, from 1 to 32.
- Delete backups everywhere. An entry's menu lists each place that holds its backups, at home and off-site, and deletes them all once you type the entry's name. The entry and its settings stay. Thanks to @manilx for asking. (#416)
- Apply a keep rule right away. The How long to keep card of a storage location has Apply now, which shows what the rule no longer keeps there and removes it once you confirm. Thanks to @manilx for the helpful suggestion. (#415)
- OLED. Under Theme an OLED switch gives OLED and AMOLED screens true black whenever the dark theme shows. Thanks to @leonp5 for the idea. (ArrowLoop #123)
- Your device's color as the accent. The wand at the start of the accent colors takes your device's own color: Material You in the Android app, and the system color in Firefox and Safari. Thanks to @leonp5 for this one too. (ArrowLoop #124)
🎨 Design
- A welcome worth watching. A fresh BombVault greets you with a little scene above the first steps: a container, a VM and a folder hop into the open vault, the door swings shut, the wheel turns and Backed up pops up, confetti included. It follows your motion setting and holds still at Off. The Welcome page row under Info, Help brings it back, even once your backups are running.
- Pairing without a password says in one sentence what it gives away, right above the fortress's card, and you can close the warning on this device.
- A new sign-in page. The logo stands large above the name, each field shows its name inside until you type, and Forgot password? opens the reset in the same card. A refused try shakes only its button and selects the field to fix.
- Follows GlimStone 4.4.1. A switch that is on draws its knob in the accent's own ink, so it no longer disappears on yellow or green. Toasts are wider with their button under the message, Don't ask again is a real checkbox, each file in a snapshot shows its kind, and full-width rows lift while you hold one.
- Selectors keep to one row. On a phone a selector gives up its even widths first, then its words where every option has an icon, and turns into a dropdown where even that does not fit.
- No colored edges. Findings and a picked backup row no longer draw a colored bar along their side. The badge says how serious a finding is.
- The others tremble while you move one. Holding a tile in Settings to reorder it makes the other tiles tremble, and so does every list you can reorder.
- Readable on every accent color. Text on an accent color keeps a contrast of at least 4.5:1, whichever color you pick.
- ParleyPort wears its new logo on the Pairing page and on its button in the README.
⚡ Improved
- Pairing runs on the same groundwork as the other apps of the family. Every instance and phone signs what it asks with a key of its own. A new one waits on the Instances card until you approve it there, with its key to compare. Instances and phones that were paired already stay approved, so there is nothing for you to do.
- Pairing goes by the twelve words alone. The field for this instance's own address and Can't find it? are gone.
- Home Assistant runs on that groundwork too, and every entity, topic and button stays as it was.
- ShipLog and TowerTorch find BombVault on their own server, whatever name you give it, so a new instance name never costs you a backup before an update.
- No network address on any card. Every member reads Connected or Not reachable, in the web interface and in the app.
- Notifications are a list of channels. Add as many as you like, each with its own switch, its own Notify choice and its own test: ntfy, Gotify, Discord, Slack, Matrix, email, Apprise, Healthchecks, Unraid, and a webhook with method, headers and a body template. Your settings move over at the first start, channel by channel. Every message has a title that names what happened, such as
BombVault: backup FAILED, and Discord and Slack show it above the text, Discord as an embed. Unraid's level follows how bad the news is: failures as warning, a VM left frozen and critical anomalies as alert. - A channel tries up to three times before it gives up, and it follows a redirect only on the same host, since a webhook's headers can carry secrets.
- TollRoll is the tile for the Unraid dashboard. BombVault no longer installs the old widget over host SSH. Get TollRoll from Community Applications.
- A host of its own for each server. Backups carry a restic host made from the key of the backups, such as
bv-3f9a0c41d2e7, instead ofbombvaulton every server. The first backup after the update builds on the last one, and the keep rules treat the old and new backups of an entry as one. Thanks to @Revan335 for the idea. (#419) - Recovery kit and emergency wizard. The kit has a section on shared repositories. If the server that holds one is lost, its kit makes a new server the owner, and the others follow it once it proves it holds the same repository.
- Deferred copies. A copy that waits while the owner tidies up shows as deferred in the activity log and on the card of that repository.
- Deleting backups works without a login password. Deleting, pruning and clearing a storage location still ask before they remove anything, and once a password is set they still need you to sign in. A paired phone can't delete.
- Comparison with Duplicacy. The comparison in the README has a column for Duplicacy and rows for deduplication across servers and for taking over jobs from other tools. Thanks to @Revan335 for asking. (#418)
- Questions go to the support thread, bugs and ideas to an issue. The issue form no longer offers Discussions, and the release notes thank @manilx without a link that leads nowhere.
- Fresh building blocks. Built with Go 1.27.4, which fixes a crash in Go's HTTP server, and the Docker client moved to its maintained module. Vite, Vitest, Tailwind and the React plugin are on their latest versions.
🐛 Fixed
- Home Assistant shows overdue backups as overdue. The Status sensor said
failedfor a section whose backups had stopped, while the overview said overdue. It now readsoverdue. If an automation of yours should fire for late backups too, addoverduenext tofailed, as the example does. - A container without backups yet gets its first one when ShipLog asks. BombVault turned such a request away as an unknown container, and ShipLog held the update back. Now the container is backed up first and the update goes ahead.
- A status that cannot be read answers with an error.
GET /api/statusanswers 500 instead of 200 when it cannot read the status, as/api/v1/statusdoes, with the same body as before. - Stacks deployed by Dockhand. Dockhand runs Compose inside its own container, so BombVault took its stack folders for folders outside Host Data and skipped them. It now finds them through Dockhand's own mount and backs them up with the stack. Thanks to @manilx for the detailed logs from two servers. (#416)
- A stack that moved to another manager no longer stops with "its backup folders are not reachable right now" when nothing is unmounted. If you had chosen its folders yourself, the message names the ones that are gone. (#416)
- Monitoring apps such as Glances mount the host's root read-only to read the disks, and their backups no longer warn that
/lies outside Host Data. - Dates in your region's order. Dates take their order and clock from your browser's region, so a moment in Portugal reads 07/11 17:05 instead of 11/07 05:05 PM. Thanks to @manilx for spotting it. (#417)
- Copies to Proton Drive after a failed upload. A broken upload left a draft that refused every later try. BombVault now lets rclone replace it, so you can drop
RCLONE_PROTONDRIVE_REPLACE_EXISTING_DRAFTif you set it as a workaround. - Locks of a second server stay. Clearing stale locks on one server could remove the lock of a backup still running on another. A lock now counts as stale only after 30 minutes without a refresh, or when this server's own earlier run left it behind.
- No restic left running after a stop. A run nobody waited for, such as the size check after a start, outlived the server and was killed hard. It now ends with the server.
- The activity log stays where you scrolled up, even when a new line arrives at that very moment.
- A tap no longer gets lost while a page loads. A page that redirects once its data is in, such as a bare Settings, used to swallow the page you tapped to in the meantime.
- Downloading a database dump from the container's own location works again.
- The nightly summary names the folders to pick again. It said
[path]where the folders of a stack belonged, while the run itself named them. - The Relay card shows the fortress's own link. In a fortress it says whether the fortress reaches the relay, not the old pairing, and an own relay BombVault can't reach reads Relay not reachable.
- A BombVault the fortress turns away leaves nothing behind. When it enters the phrase before the phrase was changed, the other BombVaults show no request from it waiting for approval, and a BombVault with a group and fortress of its own keeps both, still connected.
- A phrase you just generated stays generated after a reload. The Pairing page showed it as entered words still searching for the other instance.
- BombVault stays connected to the fortress when you open it under two addresses, such as your reverse proxy's domain and the IP with its port. It keeps the address it already goes by, so the other apps no longer lose it for minutes at a time.
- Every member of the fortress shows up, and a BombVault left behind asks for the new phrase. An app BombVault knows only from the other members is listed by its device, and you see whether it is away or still on the old phrase. After a phrase change, the list of who missed it names each member with its app and device, so three plugins on Tower no longer read as one Tower. A BombVault that missed the change says so on its card, and Enter phrase takes the new words.
🌐 Translations
- New and changed texts in all 42 languages, and the documentation pages updated in all 26.