Skip to Content
Upgrading

Upgrading

Tracearr uses the latest Docker image tag by default, so upgrading is straightforward — pull the new image and recreate the container.

TimescaleDB and Redis are persisted in a volume, so your database and configuration will be preserved during the upgrade process.

If you run Jellyfin and plan to upgrade it to version 12, upgrade Tracearr to 1.4.29 or newer at the same time. Jellyfin 12 disables legacy authorization, and older Tracearr versions can no longer connect to it. Tracearr 1.4.29+ works with both Jellyfin 12 and 10.11. See the FAQ for details.

Authentication Changes

The latest release replaces Tracearr’s authentication system. The upgrade itself requires nothing from you: no new environment variables are needed, and database migrations run automatically when the new version starts. What changes:

  1. Jellyfin login is removed. Signing in to Tracearr with Jellyfin credentials is no longer supported. Jellyfin and Emby servers are still fully supported for monitoring; only the login method is gone. If your install only ever logged in via Jellyfin, recover with either:

    • the admin CLI: docker exec -it tracearr node apps/server/dist/scripts/cli.js reset-password (works even when the account has no existing password), or
    • Sign in with Plex, when a Plex account is linked.

    See Account Recovery for details.

  2. All web users must log in once after upgrading. Existing web sessions are not carried over.

  3. Mobile devices paired after upgrading use a 30-day rolling session. Any use within 30 days extends it; a device idle for more than 30 days pairs again. Devices paired before the upgrade keep working on their existing tokens until they are re-paired; nothing expires them at 30 days.

Reverse proxies that rewrite the Host header must forward X-Forwarded-Host (or set CORS_ORIGIN to the public URL) for cookie login to work. See Reverse Proxy.

Docker Compose

This guide assumes you followed the Quick Start instructions to set up Tracearr with Docker Compose.

From the directory containing your docker-compose.pg18.yml file, run:

docker compose -f docker-compose.pg18.yml pull tracearr docker compose -f docker-compose.pg18.yml up -d

This will:

  1. Download the latest Tracearr image
  2. Recreate the container with the new image
  3. Preserve your database and configuration

If you are using a different compose file, make sure to update the commands accordingly.


Docker UI

If you deployed Tracearr through a Docker UI like Portainer, Dockge, or TrueNAS’s built-in Custom App feature, look for an option to re-pull images or redeploy your stack. The exact label varies by tool — see the Docker UI updating guide for details.


Supervised

From the directory containing your docker-compose.supervised-example.yml file, run:

docker compose -f docker-compose.supervised-example.yml pull tracearr docker compose -f docker-compose.supervised-example.yml up -d

Railway

Railway supports both automatic and manual updates. See the Railway updating guide for how to configure auto-updates or manually trigger an upgrade from the dashboard.


Proxmox VE

If you installed Tracearr using the Proxmox VE community helper script , you can update by logging into the Tracearr LXC container console and running:

update

This command is created automatically during installation. It pulls the latest version of the update script from the community-scripts repository, checks for a newer release, and applies the update.

You can also update all community-script containers at once from the Proxmox host shell using the update-apps  tool.


Unraid

In the Unraid web UI, go to the Docker tab, find Tracearr, and click Check for Updates or Update. Unraid will pull the latest image and recreate the container.


Cleaning Up Old Images

After upgrading, you can remove unused images to free up disk space:

docker image prune

Make sure to review the images being removed before confirming, as this will delete all dangling images.

Last updated on