Skip to Content
Tautulli

Tautulli

Monitoring and statistics tracker for Plex Media Server

Tautulli is a third-party application that runs alongside your Plex Media Server to monitor activity and track various statistics. It provides detailed insights into what has been watched, who watched it, when and where they watched it, and how it was watched. With beautiful graphs, user analytics, notification capabilities, and extensive customization, Tautulli is the essential companion app for Plex administrators.

QuickBox Pro installs Tautulli as a per-user, multi-instance application — each user gets their own independent installation with its own systemd service, configuration, database, and port. Multiple users can run Tautulli simultaneously, and each instance monitors one Plex server. This makes Tautulli ideal for monitoring a second Plex server by installing it under a dedicated sub-user.

Dual-mode install layout

QuickBox Pro uses two layouts depending on how many users have Tautulli installed on the server:

  • Single-user (first install) — the first user to install Tautulli on a box gets the legacy layout: URL path /tautulli, service name tautulli.service. This layout is preserved for the lifetime of that install — updates never migrate it.
  • Additional users (2nd, 3rd, …) — when Tautulli is already installed for another user on the same server, subsequent installs use the namespaced layout: URL path /<username>/tautulli, service name tautulli@<username>.service.

If you are the only Tautulli user on your server, you are on the single-user layout regardless of how many other QuickBox users exist on the box.

Watch Statistics

Comprehensive tracking of all Plex playback activity with detailed analytics

Beautiful Graphs

Visual representations of viewing habits, user activity, and library statistics

User Analytics

Per-user statistics showing watch history, top content, and playback patterns

Notifications

Webhooks, email, Discord, Slack, and more for custom playback notifications

Real-Time Activity

Live view of current Plex streams with bandwidth and transcode information

Library Insights

Track most popular content, recent additions, and library growth over time

Requires Plex Media Server

Tautulli requires a Plex Media Server installation to function. Install Plex first, then add Tautulli for monitoring capabilities.


Installation

Symptoms

  • QuickBox Pro v3 installed and configured
  • Plex Media Server installed and running (on this server or a remote one)
  • User account created on the server
  • Python 3.13 available (automatically installed)

Resolution

  • Each user gets an isolated Tautulli install — multiple instances run independently
  • Install under a sub-user to monitor a second Plex server without affecting your primary instance
  • Git-based installation from latest Tautulli source with per-user service and config
  • Automatic Python 3.13 setup (Debian 12 and earlier) with auto-incremented ports

Basic Installation

Install Tautulli for a specific user:

qb install tautulli -u username

Monitoring Multiple Plex Servers

Because each Tautulli instance monitors exactly one Plex server, you can monitor a second Plex server by creating a sub-user and installing Tautulli under it:

# Create a sub-user for the second Plex monitor qb adduser secondplex # Install Tautulli for the sub-user qb install tautulli -u secondplex

Each user’s Tautulli instance is completely independent — separate service, separate database, separate port, and separate configuration. The primary user’s instance is unaffected.

One Plex Server Per Instance

Each Tautulli instance connects to and monitors one Plex Media Server. To monitor two Plex servers, use two Tautulli instances under different users. There is no limit to the number of instances you can run simultaneously.

CLI Commands

CommandDescription
qb install tautulli -u usernameInstall Tautulli with automatic configuration
qb reinstall tautulli -u usernameReinstall Tautulli (preserves configuration)
qb update tautulli -u usernameUpdate to latest GitHub version with automatic health check
qb remove tautulli -u usernameRemove Tautulli and clean up files
qb help tautulliDisplay comprehensive help information
Automatic Port Assignment

QuickBox automatically assigns ports starting at 8181 (auto-incremented per user). Find your assigned port in the QuickBox dashboard or in ~/.config/Tautulli/config.ini.

Git-Based Installation

Tautulli is installed via git clone from the official repository at /opt/username/Tautulli. Updates pull the latest changes directly from GitHub for always up-to-date statistics and features.


Accessing Tautulli

After installation, access Tautulli in your browser. The URL depends on which install layout was used:

Single-user layout (first Tautulli install on the server):

https://your-server-ip/tautulli

Multi-user layout (second or later Tautulli install on the server):

https://your-server-ip/username/tautulli

Replace username with the QuickBox user account Tautulli was installed under. If you are unsure which layout applies, check the QuickBox dashboard — the LAUNCH link uses the correct URL for your install.

QuickBox Dashboard Integration

Tautulli is automatically integrated into your QuickBox dashboard. Find it in the Service Control panel with port and status information. Click the LAUNCH icon to open the web interface.

First-Time Setup:

  1. Complete the setup wizard
  2. Connect to your Plex Media Server
  3. Configure notification preferences
  4. Set up user accounts and permissions

Initial Configuration

1. Connect to Plex Media Server

On first access, connect Tautulli to Plex:

  1. Click Next on the welcome screen
  2. Select Sign in with Plex or Manual Configuration
  3. If signing in with Plex:
    • Sign in with your Plex account
    • Authorize Tautulli to access your server
    • Select your Plex Media Server from the list
  4. If using manual configuration:
    • Enter Plex IP: 127.0.0.1 (localhost)
    • Enter Plex Port: 32400
    • Enter Plex Token: Get from https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/
  5. Click Verify to test connection
  6. Click Next to continue

2. Configure Activity Logging

Set up activity tracking:

  1. Go to Settings → Activity Logging
  2. Configure logging options:
    • Log played: Enable to track all playback
    • Log paused: Track pause events
    • Log stopped: Track stop events
    • Log resumed: Track resume after pause
  3. Set Logging Level:
    • Debug for detailed logging (troubleshooting)
    • Info for standard logging (recommended)
    • Warning for errors and warnings only
  4. Save settings

3. Set Up Notifications (Optional)

Configure notifications for Plex events:

  1. Go to Settings → Notification Agents
  2. Add notification agent (examples):
    • Email - Email notifications
    • Discord - Discord webhooks
    • Slack - Slack channel notifications
    • Webhook - Custom webhook endpoints
  3. Configure triggers:
    • Playback Start - When media begins playing
    • Playback Stop - When media stops
    • Watched - When media is marked as watched
    • Recently Added - New content added to library
  4. Customize notification templates with variables
  5. Test and save

Configuration and Files

Tautulli paths and files
/
opt/
└── {username}/
│ └── Tautulli/# Application install directory (git clone)
│ │ ├── Tautulli.py# Main application entry point
│ │ └── lib//# Bundled Python dependencies
home/
└── {username}/
│ └── .config/
│ │ └── Tautulli/# User data and configuration
│ │ │ ├── config.ini# Main configuration file
│ │ │ ├── tautulli.db# Statistics and history database
│ │ │ ├── logs//# Application log files
│ │ │ └── backups//# Automatic configuration backups
etc/
├── systemd/system/
│ ├── tautulli.service# Single-user layout: static unit with username baked in (first install on server)
│ ├── tautulli@.service# Multi-user layout: shared template unit, instantiated per additional user
│ └── tautulli@{username}.service# Multi-user layout: per-user service instance (e.g. tautulli@alice.service)
└── nginx/software/
│ └── {username}.tautulli.conf# Per-user nginx reverse proxy configuration

Service Management

The service name depends on which layout was used at install time.

Single-user layout (first Tautulli install on the server — service is tautulli.service):

systemctl status tautulli # Check status systemctl restart tautulli # Restart service journalctl -u tautulli -f # View live logs systemctl enable tautulli # Start on boot (already enabled) systemctl disable tautulli # Prevent auto-start

Multi-user layout (second or later install — service is tautulli@username.service):

systemctl status tautulli@username # Check status systemctl restart tautulli@username # Restart service journalctl -u tautulli@username -f # View live logs systemctl enable tautulli@username # Start on boot (already enabled) systemctl disable tautulli@username # Prevent auto-start

Replace username with the actual user account. If you are unsure which layout applies, run systemctl status tautulli first — if it exists and shows your username in the User= line, you are on the single-user layout. Additional multi-user instances run as tautulli@alice.service, tautulli@secondplex.service, etc.


Troubleshooting

Checking Logs

Tautulli has multiple log sources depending on the issue:

# Tautulli application log (most detailed) cat /home/username/.config/Tautulli/logs/tautulli.log # Systemd service journal — single-user layout journalctl -u tautulli -f # Systemd service journal — multi-user layout (replace username with the actual user) journalctl -u tautulli@username -f # QuickBox install/update operation log (v4 dashboard) # Located at: /opt/v4-dashboard/var/log/{username}/package-{action}-{jobId}.log

Tautulli Won’t Start

# Single-user layout systemctl status tautulli journalctl -u tautulli --no-pager -n 50 # Multi-user layout (replace username with the actual user) systemctl status tautulli@username journalctl -u tautulli@username --no-pager -n 50

Check Python installation:

python3.13 --version # Should show Python 3.13.x # Or on Debian 13 python3 --version

Verify file permissions:

ls -la /opt/username/Tautulli/Tautulli.py ls -la /home/username/.config/Tautulli/config.ini

Cannot Connect to Plex Server

Symptoms

  • Tautulli cannot connect to Plex Media Server
  • Plex token authentication fails
  • Connection refused or timeout errors
  • No activity data showing in Tautulli

Resolution

  • Verify Plex is running: systemctl status plexmediaserver
  • Check Plex port is 32400: netstat -tlnp | grep 32400
  • Get fresh Plex token from https://support.plex.tv/articles/204059436/
  • Test Plex accessibility: curl http://localhost:32400/web
  • Check Tautulli settings: Settings → Plex Media Server → Connection

No Activity Showing

# Verify activity logging is enabled # Settings → Activity Logging → Enable logging # Check Plex is generating activity # Open Plex and play something # Verify Tautulli can read Plex logs # Single-user layout: journalctl -u tautulli -f | grep -i "plex" # Multi-user layout (replace username with the actual user): journalctl -u tautulli@username -f | grep -i "plex" # Refresh activity page in Tautulli # Activity → Home → Refresh button

Notifications Not Working

# Test notification agent # Settings → Notification Agents → [Agent] → Test # Check notification triggers are configured # Settings → Notification Agents → [Agent] → Triggers # Verify webhook URL or credentials are correct # Check logs for notification errors # Single-user layout: journalctl -u tautulli -f | grep -i "notif" # Multi-user layout (replace username with the actual user): journalctl -u tautulli@username -f | grep -i "notif"

Permission Issues

sudo chown -R username:username /opt/username/Tautulli sudo chown -R username:username /home/username/.config/Tautulli # Single-user layout: systemctl restart tautulli # Multi-user layout: systemctl restart tautulli@username

Configuration Reset

# Backup current configuration cp -r ~/.config/Tautulli ~/.config/Tautulli.backup # Stop service # Single-user layout: systemctl stop tautulli # Multi-user layout (replace username with the actual user): systemctl stop tautulli@username # Remove configuration (will be regenerated) rm ~/.config/Tautulli/config.ini # Restart service # Single-user layout: systemctl start tautulli # Multi-user layout: systemctl start tautulli@username

Best Practices

Do

  • Enable all activity logging for comprehensive statistics tracking
  • Set up notifications for server events (new users, playback issues)
  • Regularly review user statistics to identify most active users
  • Use graphs to track library growth and viewing trends over time
  • Configure webhook notifications for integration with other services
  • Keep Tautulli updated via qb update tautulli for latest features
  • Create backups of ~/.config/Tautulli before major Plex upgrades
  • Monitor bandwidth usage to identify network bottlenecks

Don't

  • Don't delete the ~/.config/Tautulli directory—contains all statistics data
  • Don't manually edit config.ini while Tautulli is running
  • Don't share your Tautulli admin credentials with untrusted users
  • Don't disable activity logging—you'll lose historical statistics
  • Don't ignore notification errors—check logs and fix configuration
  • Don't expose Tautulli directly to internet without authentication
  • Don't expect Tautulli to work without Plex Media Server running
  • Don't delete Plex activity logs—Tautulli relies on them for tracking

Frequently Asked Questions

All Tautulli data — including the statistics database, configuration, logs, and backups — is stored in /home/{username}/.config/Tautulli/. The application itself is installed at /opt/{username}/Tautulli.
Ports start at 8181 and auto-increment per user. Check your assigned port in the QuickBox dashboard Service Control panel, or look in ~/.config/Tautulli/config.ini under the http_port setting.
No. Tautulli is specifically designed as a monitoring companion for Plex Media Server. It requires an active Plex installation to function. For Emby or Jellyfin monitoring, consider the built-in QuickBox Streaming Dashboard.
Yes. Each user gets an independent Tautulli instance with its own service, configuration, database, and port. The first user to install Tautulli on the server uses the tautulli.service unit; every additional user gets a namespaced tautulli@username.service instance. Instances do not share state and do not affect one another.
Run systemctl status tautulli. If the unit exists and its User= line shows your username, you are on the single-user layout and your URL is /tautulli. If the command returns 'Unit tautulli.service could not be found', you are on the multi-user layout and your URL is /username/tautulli. You can also check the QuickBox dashboard — the LAUNCH link uses the correct URL for your install.
Because each Tautulli instance monitors exactly one Plex server, create a dedicated sub-user and install Tautulli under it: qb adduser secondplex then qb install tautulli -u secondplex. Since another user already has Tautulli installed, this second install will use the multi-user layout and be accessible at /secondplex/tautulli. During Tautulli's first-run setup, point that instance at the second Plex server's IP and port. Your primary user's Tautulli instance is unaffected.
Run qb update tautulli -u username. The update process pulls the latest code from GitHub, re-deploys the service configuration, and verifies the service starts successfully afterward.
No. Statistics are stored in ~/.config/Tautulli/tautulli.db, which is separate from the application directory. Updates only affect the application code at /opt/{username}/Tautulli.
Copy the entire ~/.config/Tautulli directory. This contains your database, configuration, and logs. QuickBox also creates automatic backups during reinstall operations.
On Debian 11, Debian 12, Ubuntu 22.04, and Ubuntu 24.04, QuickBox uses Python 3.13 (compiled to /usr/local/bin/python3.13). On Debian 13 (trixie), the system Python 3 is used directly.

Use Cases

Server Monitoring

  • Track all Plex activity in real-time with live stream information
  • Monitor bandwidth usage and identify transcoding bottlenecks
  • View server health and resource utilization
  • Get alerts for server issues or playback errors

User Analytics

  • Analyze viewing habits per user (most watched, favorite genres)
  • Track user activity patterns (peak hours, device usage)
  • Identify inactive users or heavy streamers
  • Generate watch reports for billing or quota management

Content Insights

  • Discover most popular movies, TV shows, and music
  • Track recently added content and library growth
  • Identify unwatched content for removal decisions
  • Analyze genre popularity and viewing trends

Required Application

Media Management

Media Requests


Additional Resources


Join the Community

Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.

Dedicated Support
Feature Previews
Community Configs
Active Discussions
Join Discord Server
Last updated on