On this page

How-to

Go back to an earlier version

If a new version of Starboard causes you a problem, go back to an earlier one with one command. Your settings are backed up first, and you can update again when you are ready.

Before you begin

  • A terminal open on the server. Read The terminal: entering commands.
  • Know which version you had before, such as v0.7.2. The steps show how to list the versions.

Steps if you used the installer

  1. Go to the Starboard folder:
cd ~/starboard
  1. List the versions you can go back to. The newest is last:
git tag -l 'v*' --sort=v:refname
  1. Install the version you want. Put its name in place of v0.7.2, with the v at the start:
./update.sh --to v0.7.2

The updater backs up your settings, installs that version and restarts Starboard. The last line says "Updated to" and the version you chose.

  1. Reload Starboard in your browser.

Steps if you used the ready-made image

  1. Go to the folder that holds compose.image.yaml:
cd ~/starboard
  1. Open the Compose file in the text editor nano:
nano compose.image.yaml
  1. Find the line that starts image: ghcr.io/themightytrex/starboard:. Change the word after the last colon, usually latest, to the version you want, without the v. For example:
image: ghcr.io/themightytrex/starboard:0.7.2
  1. Save with Ctrl and O, then Enter. Leave nano with Ctrl and X.
  2. Download that version:
docker compose -f compose.image.yaml pull
  1. Start Starboard with it:
docker compose -f compose.image.yaml up -d

Go forward again

  • With the installer: run ./update.sh on its own. It installs the newest release.
  • With the ready-made image: change the version in the image: line back to latest, then run the commands in Steps 5 and 6 again.

Going back for Reelix, apps and plug-ins

  • Starboard: when a new version does not start, Starboard goes back by itself, whether you used Update now, the automatic update or ./update.sh. Going back later is done on the server, with the steps in this article.
  • Reelix: when its automatic update, or an update through Starboard's API, is not healthy within five minutes, Starboard puts the version before back by itself. Its settings from before are in reelix-before-update.tgz beside the set-up files. Read Updates for Reelix.
  • Your other apps: an update through Starboard's API goes back by itself when the new version does not run within two minutes. Read Update your apps.
  • Plug-ins: select Roll back to on the plug-in's page at any time, with no download, and its settings go back to how they were. A plug-in also goes back by itself when its new version does not start or answer. Read Roll back to the version you had.

Things to note

  • Staying on an older version means you miss fixes, including security fixes. Go forward again once the problem is solved.
  • A newer version can change how settings are stored. When it does, Starboard keeps a copy of the old settings in data/backups first. If something is wrong on the older version, put back the backup from before the update. Read If it does not work.
  • Tell the people who make Starboard what went wrong, so it can be fixed. Read Read the log and report a problem.

If it does not work

  • "Stopped: there is no release called": the version name is wrong. Check it in the list from Step 2, including the v at the start.
  • Settings are wrong on the older version (installer): each update saved your data folder in the backups folder, in a file named with the date and time, such as starboard-data-2026-11-01-093000-a1b2c3d.tar.gz. To put one back: 1. List the backups. The names include the date and time:

    ls backups
  1. Stop Starboard:

    docker compose down
  2. Move the current settings aside, so nothing is lost:

    mv data data.newer
  3. Unpack the backup from before the update that caused the problem. The newest backup was made when you went back, so use the one before it. Put its file name in place of the example:

    tar -xzf backups/starboard-data-2026-11-01-093000-a1b2c3d.tar.gz
  4. Start Starboard again:

    docker compose up -d

If you installed with --native, use systemctl --user stop starboard and systemctl --user start starboard in place of the two docker commands. - Settings are wrong on the older version (ready-made image): do the same with the copy you made before updating, starboard-data-before-update.tar.gz, and the commands docker compose -f compose.image.yaml down and docker compose -f compose.image.yaml up -d.

Find out more

This page on GitHub, where the help is written.