Tautulli

Track playback and statistics for an existing Plex Media Server.

Choose your deployment and the way you want to use Selfhost. The instructions below follow that choice.

Deployment Use Selfhost with

Set up Tautulli

Editable Compose files in your own directory.

Complete Tautulli setup to authorize the Plex server and enable authentication.
Keep /config persistent for history, application configuration and backups.

selfhost app --directory ./tautulli init tautulli

Initialization writes portable files and does not start the app. Review compose.yaml, the private .env and any files in files/, then start it:

selfhost app --directory ./tautulli start

No Selfhost dashboard or background service is needed. You can also start these files directly:

cd tautulli
docker compose -f compose.yaml up -d

Connect an existing installation

Use Existing apps → Link an app in the dashboard, or the CLI’s existing-app commands. Choose Tautulli, its URL and, optionally, its exact Docker container on a connected server.

Save existing.json with your app URL. Add server_id and container for container inspection and actions.

{
  "profile": "tautulli",
  "name": "Tautulli",
  "url": "https://app.example.com"
}

selfhost existing link --file existing.json
selfhost existing list
selfhost existing inspect EXISTING_ID

Linking enables the existing-app profile’s supported inspection and actions. It does not import Compose or attach the new-deployment settings and onboarding profiles described below.

Existing app commands, permissions and unlinking

Actions for a linked container

Check health

Check the local Tautulli status endpoint.

selfhost existing action EXISTING_ID check-health

Before configuring integrations

The declared health action checks the local server.
Plex tokens, notification agents and scheduling are managed through Tautulli.
Changing container user/group settings can change ownership of existing files.

Tautulli integrations

Compose service: tautulli. These operations use the profile saved when this deployment is created.

Use Tautulli initial setup to connect a Plex server and enable authentication. Its native config.ini and history database remain under /config; environment settings do not rewrite Plex credentials.

Native settings

Changes use the app’s Compose environment. Unrelated settings are preserved.

Supported fields (3)

Time zone timezone: string
Container user ID user-id: The entrypoint updates ownership of /config. string
Container group ID group-id: string

Save a JSON map of the field IDs you want to change as changes.json. Replace FIELD_ID with an ID from the supported fields above, and use its declared value type. Review the plan and replace REVIEWED_REVISION with the revision it returns.

{
  "FIELD_ID": "YOUR_VALUE"
}

selfhost app --directory ./tautulli config tautulli
selfhost app --directory ./tautulli plan tautulli changes.json
selfhost app --directory ./tautulli apply tautulli changes.json --revision REVIEWED_REVISION

Saved changes need service recreation to become active. Existing interpolated environment values stay under your control in .env or Compose.

App actions

Check health

Check the local Tautulli status endpoint.

selfhost app --directory ./tautulli action tautulli check-health

App configuration reference

Versions and updates

This deployment uses the following images. Existing projects retain their saved recipe and images. A new catalogue version does not silently update them.

tautulli: ghcr.io/tautulli/tautulli:v2.18.1

Review compatibility and back up app data before an update. Choose an image version and review the change.

Keep control of your setup

Selfhost remains optional. Your app runs using ordinary Compose files, its own settings and persistent data. Keep the Compose project name and volumes to preserve storage. Configuration exports and setting backups do not include application data.

Standalone CLI guide · Backups and removal · Tautulli documentation