📘 BACKCLICK Doku
Anmelden

Update, offline package and backup

✎ Bearbeiten + Unterseite Historie (1)
⋯
Erstellt von KI (MCP) am 13.11.2026 05:41 ¡ zuletzt geändert von KI (MCP) am 13.11.2026 05:54 ¡ v2

Since version 5.10.0, BACKCLICK 5 runs as a Docker stack and is updated through the administration interface. This page describes the update, the offline package, the way back and the backup.

Update at the click of a button

The Update page is in the administration interface.

  • “Nach Updates suchen” (check for updates) checks whether a newer version is available. If the installation is up to date, the page reports “kein Update notwendig” (no update required); “Update starten” (start update) is then disabled.
  • “Update starten” installs the new version. During the update, a notice banner appears; the page reconnects by itself afterwards.
  • Database changes are applied automatically with every update.
  • All packages are digitally signed. If an update fails, the previous state is restored automatically.
  • The page shows the version number and, behind it, the identifier of the installed build. Between two version numbers, updates can appear that change only the identifier.

Offline package

For servers without internet access, an offline package is available for every version.

  • The Update page shows the download address and, on request, the credentials for copying. This allows the package to be downloaded on a computer with internet access.
  • The package is uploaded on the Update page directly after the package selection, with a progress bar. An interrupted transfer is resumed.
  • The update is then started as usual. Packages that are no longer needed can be removed.

Return to the previous version

After a successful update, update.sh --zurueck on the command line returns to the previous version. The database is kept, provided the previous version can work with it; otherwise it is restored from the backup.

Update channel

Live installations follow the channel “produktion”. The earlier setting “aktuell” (current) remains valid and is read as “produktion”.

Daily backup

The stack contains an optional backup service. The operator chooses the targets, including several: directory, rsync, restic or Proxmox Backup Server.

Certificates

The proxy can obtain and renew TLS certificates via ACME (optional, for example Let’s Encrypt). Existing installations keep their setting.

License key

Since version 5.10.1, there is a new, digitally signed license key format. Existing license keys remain valid.

Migration of an existing installation

A migration tool transfers an existing installation, including its data, to the new stack. The migration first runs in trial mode, without sending and without mailbox retrieval. Sender IPs are backed up and checked before the start.

All changes per version are listed in the changelog.