Configuration

Tracearr can be configured through the web interface and environment variables.

Web Interface

Most settings are available in the Settings page:

• Servers — Add and manage media server connections
• Real-Time Updates — Instant Jellyfin and Emby sessions with the SSE plugin
• Seerr Requests: link Seerr, Overseerr or Jellyseerr to see who requested each title
• Notification Destinations: the places alerts are sent to (see below)
• Email & Newsletters: send alerts over SMTP and schedule recently-added digests to members
• Sharing Detection — Set up account sharing detection
• Appearance — Customize the dashboard
• Tailscale VPN — Connect to your tailnet with the built-in Tailscale integration

Notification destinations

A destination is a named place notifications go. Mobile push and browser toasts are built in; you add the rest under Settings → Notifications: Discord, ntfy, Gotify, Apprise, Pushover, email, or a JSON webhook. You can have more than one of the same type. Two Discord webhooks pointing at different rooms is a normal setup. The kinds and their fields are on the Notification Destinations page.

A destination has one checkbox of its own, Receive violations, which sends it every violation. Everything else a destination hears about comes from an automation: a Send Notification action names the destinations it sends to, and it reaches them whether or not they asked for anything. The per-event checkboxes destinations used to carry are gone; upgrading turned each subscription into an automation that sends to the destinations that had it ticked.

Destination secrets (webhook URLs, API tokens, user keys) are encrypted in the database. The key is derived from JWT_SECRET unless you set ENCRYPTION_KEY to a 64-character hex string, which takes precedence.

Two things follow from that. Rotating JWT_SECRET while ENCRYPTION_KEY is unset leaves Tracearr unable to read the stored secrets; the destinations list flags each affected one so you can re-enter it. And a backup can only be restored with the same secret it was written under, so keep JWT_SECRET (or ENCRYPTION_KEY) alongside the backup file.

Environment Variables

For advanced configuration, see the Environment Variables reference.