Updating and rollback

Updating briefly stops live viewing and recording. Choose a suitable maintenance window first. For what to back up and how to restore it, see Backup and monitoring.

Upgrade

1. Take a backup with the service stopped first, and note the current version number. The version number is on the first line of Settings → General → About → Third-party software.
2. Stop Rerinku View, replace the program file, and start it again. The built-in FFmpeg and recognition component are updated automatically with the new version. config.yaml isn’t overwritten, and new config options aren’t added to it automatically.
3. Database schema upgrades run automatically at startup. They only go forward, and each one runs only once.
4. Check the health check, device count, live video and historical playback.

Updating Docker

Run these commands from the directory containing your Compose file. Stop the container first, back up the entire directory or named volume mounted at /data (including configuration, database and secret.key), and keep the previous image version available for rollback.

docker compose stop
# Finish backing up the data volume before continuing
docker compose pull
docker compose up -d
docker compose logs --tail=100

Keep the existing mounts and configuration. Do not run docker compose down -v: it removes named volumes. If you pin image tags, change the Compose file to the published target version first.

Verify the update

Check that /healthz returns 200 and the device count matches the count before the update. Open a live camera, play a recording made before the update and confirm new recordings are appearing. If you use AI, remote storage or Quick Connect, also check recognition results, uploads and access from outside your LAN. Save logs if anything fails, then use Troubleshooting.

Rollback

Once the new version has started, the database schema has already been upgraded, so you can’t just switch back to the old program. Some upgrades remove old fields and tables:

1. Stop the new version, and keep its logs and a copy of the current data.
2. Restore the database backup from before the upgrade. The recordings directory can usually stay.
3. If, while running the new version, you added config options the old version doesn’t recognize, remove them first. Otherwise, the old version refuses to start.
4. Start the old version and check the health check, devices, recordings and playback.