AirVault — self-hosted iPhone backups for your unRAID server. Pair an iPhone once over USB, then backup it over Wi-Fi to a local share — no computer in the middle, no cloud involved. Backups are incremental and versioned: every run is a restore point you can browse and restore from, with optional backup encryption, all managed from a web UI. Website: https://airvault.cloud Template: https://github.com/airvault/airvault Image: ghcr.io/airvault/airvault (linux/amd64) Installation Install AirVault from Community Applications. Defaults work out of the box: - Backups directory — an unRAID share with enough free space for your iPhone backups (default /mnt/user/backups/iphone). - Application Data / Pairing Records — appdata paths, keep the defaults. - Web UI Port — 32298. Host networking is required (Wi-Fi backups rely on mDNS discovery). Note: if you change this port, the "WebUI" button will still point to 32298 — also edit the WebUI field on the container edit page (Advanced View) to match. This is an unRAID limitation for host-network containers. FAQ Q: The iPhone is not detected over USB. A: Make sure you connect your iPhone directly to your unRAID server, the USB Devices (/dev/bus/usb) and USB Hotplug Events (/run/udev) mappings are present (they are in the template by default), the cable is a data cable, and the phone is unlocked when you plug it in. Q: Wi-Fi backups don't start. A: The phone must be on the same network as the server, and the container must run with host networking (default in the template). Wi-Fi sync must have been enabled during USB pairing. Q: Where is my Web UI password? A: It's the Web UI Token. If you left it blank, check the container log for the generated token; it is also stored in Application Data (/data/config/auth-token). Bug reports are welcome here or on GitHub: https://github.com/airvault/airvault/issues