Skip to content

Service upgrades

A new version, with a backup and a way back

The app checks for a new release every six hours, and Check for updates asks right away. When the service page says New version available, the service can be upgraded from there.

An upgrade is offered when the published release is newer than the build on the server. If the server runs a newer build than the published one, the page says so and offers nothing; a build whose version cannot be compared is offered with a warning that only the file checksum tells the two apart.

  1. Back up the data and keep the current program, so there is something to go back to. The last three backups are kept.
  2. Replace the program and bring the stored data up to the new version.
  3. Start and check — it only counts as done when the service answers.

Every step can go back: any failure restores the previous program and data automatically and tells you it rolled back, so a failed upgrade is not a broken server.

  • The service stops for a moment, so devices pause and resume by themselves when it is back.
  • The server needs free space for the backup; if it does not have it, the page asks you to free some first instead of starting.
  • Click Start upgrade and leave the window open until it finishes.