Skip to Content
Seerr

Seerr

Unified request management for Plex, Jellyfin, and Emby

Overview

Seerr is the unified media request manager that merges Overseerr and Jellyseerr into a single application, maintained by the seerr-team. It provides native support for Plex, Jellyfin, and Emby media servers with an intuitive interface for users to discover and request movies and TV shows. Requests are automatically forwarded to Sonarr and Radarr for download. User quota management, approval workflows, and extensive notification support (Discord, Slack, email, Telegram, Pushover) make Seerr the definitive content request tool for shared media servers.

QuickBox Pro installs Seerr per user from the official seerr-team/seerr GitHub repository, selecting Node.js and pnpm from the chosen Seerr release and raising Node.js to the QuickBox security minimum when needed. The installer creates isolated virtual environments, configures a per-user systemd service (seerr@username), and allocates a unique public port and internal port for each user so multiple users on the same server can run Seerr side by side without collisions.

Replaces Overseerr and Jellyseerr
Info

Seerr is the canonical replacement for both Overseerr and Jellyseerr in QuickBox Pro. Running qb update overseerr -u username or qb update jellyseerr -u username automatically migrates to Seerr. New installations should use qb install seerr -u username directly.

Multi-user and group-gated
Note

Seerr is a multi-user installable application — each user on the server can have their own Seerr instance with its own port, data directory, and optional subdomain. Whether a given non-admin user is permitted to install Seerr is controlled by their assigned user group. Your server administrator decides which user groups are allowed to install Seerr; administrators can install Seerr for any user regardless of group. If a user attempts to install Seerr and their group does not include it, the install will be blocked with a “package not allowed for user’s group” message.

Key features

Multi-Server Support

Native integration with Plex, Jellyfin, and Emby with automatic library scanning

Sonarr/Radarr Integration

Automatic request forwarding to media management tools with quality profile selection

User Management

Request quotas, approval workflows, and granular permissions per user

Rich Notifications

Discord, Slack, email, Telegram, and Pushover notifications for requests and approvals

Media Discovery

Browse popular, trending, and upcoming content from TMDb with rich metadata

Built-in Migration

Migrate from Overseerr or Jellyseerr with --migrate --from preserving settings, database, and ports

Per-User Service

systemd unit seerr@username with isolated Node.js venv and a unique randomized public port per user

Multi-User Installable

Multiple users on the same server can each run their own Seerr instance without port collisions

Reverse Proxy Ready

nginx fronts each user's public port and proxies to an internal localhost port with automatic path rewriting

TLS Domain Support

Optional per-user subdomain via the v4 dashboard SSL Control page (or qb install lecert --seerr -d domain -u username)

When to use it

Prerequisites

  • Need a unified media request app supporting Plex, Jellyfin, and Emby
  • Want to consolidate separate Overseerr and Jellyseerr installations
  • Require user quota management and approval workflows for content requests
  • Need automated notifications for request status updates across multiple channels

What you get

  • Install via qb install seerr -u username to clone seerr-team/seerr and build with pnpm
  • Each user is assigned a unique public port (randomized from the 5055 base) and a derived internal port for the Node.js process
  • Optional per-user subdomain via the v4 dashboard SSL Control page, or directly with qb install seerr -u username -d domain / qb install lecert --seerr -d domain -u username
  • Per-user systemd service seerr@username with an isolated, security-maintained Node.js environment and auto-start on boot

Installation

Who can install Seerr
Info

Administrators can install Seerr for any user at any time. Non-admin users can install Seerr themselves only if their assigned user group includes Seerr in its allowed software list. If you are a regular user and the install command returns “package not allowed for user’s group”, ask your server administrator to add Seerr to your group’s software permissions. Installs triggered from the v4 dashboard’s Package Management page enforce the same group-based access rules.

Install from the Dashboard

Open App Dashboard → Package Management (/dashboard?mode=packages), find Seerr in the catalog (browse Media Requests or search), and click Install. The dashboard streams the install log live and Seerr appears in your Application Control panel when it finishes. Reinstall and Remove are in the same Package Management panel. To update, use the amber Update badge on the Seerr row in the App Dashboard.

What you see is gated by your account: admins manage any user’s apps; regular users manage their own (subject to their group’s allowed software, as noted above). See App Management for the full flow.

To publish Seerr on a subdomain with a TLS certificate, use the SSL Control page in the dashboard after install (covered below).

Install from the CLI (automation)

The CLI runs the same scripts as the Dashboard and is suited to automation and scripting:

bash
qb install seerr -u username
qb install seerr -u username -d 'seerr.example.com'        # with domain + TLS
qb reinstall seerr -u username
qb update seerr -u username
qb remove seerr -u username
Back up before reinstall or remove
Caution

Reinstall and remove delete Seerr’s configuration and request database. Keep a separate backup of /opt/username/Seerr/config/ before either operation.

The CLI also exposes the built-in migration utility (preserves settings, database, port, and nginx config):

bash
qb install seerr -u username --migrate --from jellyseerr
qb install seerr -u username --migrate --from overseerr

Full flag reference: CLI Reference.

Publish Seerr on a per-user subdomain

Each user can optionally have Seerr published on its own subdomain (e.g. https://seerr.user.example.com). The recommended workflow is the SSL Control page in the v4 dashboard, which an administrator uses to issue a Let’s Encrypt certificate and generate a per-user nginx vhost in one step. Under the hood, SSL Control invokes:

bash
qb install lecert --seerr -d domain -u username

The same command is available directly from the CLI, and you can also pass -d at install time:

bash
qb install seerr -u username -d 'seerr.example.com'

The lecert workflow reads the user’s internal port from /opt/username/Seerr/env.conf, copies the subdomain.nginx.conf template, and writes /etc/nginx/sites-enabled/username.seerr.conf with the provided domain and certificate paths. When DNS credentials are configured (for example Cloudflare, Route53, or DigitalOcean), the installer detects them automatically and uses DNS challenge validation.

Migrate from Overseerr or Jellyseerr

Seerr includes a built-in migration utility that preserves your settings, database, port assignment, nginx configuration, and URL overrides:

bash
# Migrate from Jellyseerr
qb install seerr -u username --migrate --from jellyseerr
 
# Migrate from Overseerr
qb install seerr -u username --migrate --from overseerr

The migration process:

  1. Backs up the source application
  2. Stops the old service
  3. Copies settings.json and db.sqlite3 to the new Seerr install
  4. Preserves the original port assignment
  5. Creates new nginx configs from Seerr templates
  6. Migrates URL override entries
  7. Removes old database entries, service files, and install directories
  8. Reloads systemd and nginx
Automatic Migration on Update
Tip

Running qb update jellyseerr -u username or qb update overseerr -u username automatically triggers migration to Seerr. No manual intervention is needed.

Initial Configuration

First-Time Setup

On first access, Seerr prompts you to connect your media server:

  1. Open Seerr web interface at http://host:port
  2. Select Media Server Type: Choose Jellyfin, Emby, or Plex
  3. Authenticate: Sign in with your media server account
  4. Select Server: Pick your media server from the list
  5. Library Sync: Seerr automatically scans your media libraries
  6. Admin Assignment: First user to sign in becomes the administrator
QuickBox Dashboard Integration
Tip

Seerr is automatically integrated into your QuickBox dashboard. Find it on the App Dashboard (the default control view), expand its row for port and status, and click Open to launch the web interface.

Connect Sonarr and Radarr

Configure media management integrations for automatic request handling:

  1. Navigate to Settings > Services in Seerr
  2. Add Radarr Server:
    • Default Server - Enable for primary Radarr instance
    • Server Name - Descriptive name (e.g., “QuickBox Radarr”)
    • Hostname or IP - localhost
    • Port - Your Radarr port (default 7878)
    • Use SSL - Uncheck (reverse proxy handles SSL)
    • API Key - Copy from Radarr’s row on the App Dashboard (API & Secrets section), or from Radarr > Settings > General > API Key
    • Quality Profile - Select default profile
    • Root Folder - Select default media path
    • Minimum Availability - Released, In Cinemas, or Announced
    • Click Test to verify connection, then Save
  3. Add Sonarr Server:
    • Follow same steps as Radarr
    • Port - Your Sonarr port (default 8989)
    • API Key - Copy from Sonarr’s row on the App Dashboard (API & Secrets section), or from Sonarr > Settings > General > API Key
    • Quality Profile - Select default profile (e.g., “HD-1080p”)
    • Root Folder - Select TV shows path
    • Season Folder - Enable for organized library structure
    • Click Test, then Save

Configure Notifications

Set up notification channels for request updates:

  1. Go to Settings > Notifications
  2. Discord Integration (recommended):
    • Create Discord webhook in your server
    • Enter Webhook URL
    • Enable notification types: Media Requested, Media Approved, Media Available, Media Failed
    • Click Test to send test notification
    • Save Changes
  3. Email Notifications (optional):
    • Configure SMTP Settings (host, port, credentials)
    • Set From Email Address
    • Enable desired notification types
    • Save Changes

Managing requests from the dashboard

Once Seerr is installed, its requests appear on the dashboard’s Media Requests page alongside every other Seerr and Ombi instance on the server — with posters, titles, and cast. You can review, approve, and deny requests there without opening each Seerr install separately, and the page discovers your instance automatically, with no URL or API key to configure. Access to that page is granted through a role; having Seerr installed does not by itself provide it.

Seerr requests on the Media Requests page
Note

Seerr does not store a denial reason against a request, so denying a Seerr request offers no reason field at all and the decision is recorded without one. Ombi, by contrast, keeps a reason and shows it to the requester, so denying an Ombi request does offer the field. Seerr also stores no title against a request, so the dashboard resolves titles and artwork itself; a request whose title has not resolved yet shows an identifier and picks it up on a later load. Request submission, quotas, notifications, and automation stay in Seerr itself; the dashboard page is a review-and-decide surface over what Seerr already holds. See Media Requests for the full reference.

Access and authentication

URL / route

  • Default: https://host:<your-public-port> — nginx in /etc/nginx/apps-http/username.seerr.conf listens on the user’s randomized public port and proxies to the internal Node.js port on 127.0.0.1. The exact public port is unique per user and recorded in the QuickBox database.
  • Path-based access: some installations also expose Seerr at /seerr through /etc/nginx/software/username.seerr.conf alongside the per-user public port listener.
  • With a subdomain: https://domain/ served by /etc/nginx/sites-enabled/username.seerr.conf when installed with -d domain from lecert or via the v4 dashboard’s SSL Control page.
Dashboard Quick Access
Tip

Install or remove Seerr from the Package Management tab; to open it or read its assigned port, use the App Dashboard (the default control view) and expand the Seerr row for the port and a direct Open button. You can also read your assigned port from the software_port column of the user_software table or directly from /opt/username/Seerr/env.conf (which stores the internal Node.js port — add or subtract 10000 to map between internal and public).

Security notes

  • The service runs as username via seerr@username.service and reads environment settings from /opt/username/Seerr/env.conf
  • Each user gets a unique public port and a unique internal port; the internal port is public_port + 10000
  • TLS is provisioned when lecert installs certificates into /etc/nginx/ssl/domain/ and binds them in the generated vhost
  • First user to sign in becomes the administrator with full permissions
  • Additional users inherit permissions based on their media server role
  • Webpush notifications are enabled by default during installation

Configuration and files

Path
Description
/opt/username
Seerr/
Application root
env.conf
Holds PORT=<internal> — the localhost port the Node.js process binds (public port + 10000)
config/
Persistent app data
settings.json
Primary application settings
db/
SQLite database storage
db.sqlite3
Application database
dist/
Built application served by Node
lib/
Isolated runtime environments
nodejs/
Seerr/
.venv/
Per-user Node.js environment with the release-required pnpm
python/
Seerr/
.venv/
Python helper environment for the Node.js setup
Path
Description
/home/username/.config
Seerr/
Symlinks to /opt/username/Seerr/config/ contents
Path
Description
/etc/nginx
apps-http/
username.seerr.conf
Per-user public port listener; proxies to the internal Node.js port on 127.0.0.1
software/
username.seerr.conf
Optional path-based reverse proxy (exposes Seerr at /seerr)
sites-enabled/
username.seerr.conf
Domain vhost created by lecert (when -d domain is used)
Path
Description
/etc/systemd/system
seerr@username.service
Per-user systemd service unit

Common tasks

Service Management

Seerr runs as a per-user systemd service seerr@username:

bash
# Start/stop/restart service
systemctl start seerr@username
systemctl stop seerr@username
systemctl restart seerr@username
 
# Check service status
systemctl status seerr@username
 
# View live logs
journalctl -u seerr@username -f
 
# Enable/disable auto-start on boot
systemctl enable seerr@username
systemctl disable seerr@username

Application Management

Use QuickBox CLI for application updates and maintenance:

bash
# Update to latest release
qb update seerr -u username
 
# Reinstall (removes app data; back up first)
qb reinstall seerr -u username
 
# Remove application
qb remove seerr -u username
 
# View help
qb help seerr
How qb update seerr protects your port assignment
Info

Every Seerr update needs to know which public port your instance already owns so nginx, the database row, and the running service stay consistent. The updater resolves that port from multiple sources in priority order and refuses to proceed if none of them yield a valid value:

  1. /opt/username/Seerr/env.conf — the PORT= value written by the last successful install or update. This is the most authoritative source because it is exactly what the running seerr@username service binds to.
  2. QuickBox database (user_software.software_port for this user) — used when env.conf is missing or unreadable.
  3. /etc/nginx/apps-http/username.seerr.conf — the public port parsed from the listen directive. Fallback of last resort.

Each candidate is validated as a positive integer before it is accepted. If all three sources are missing, empty, or invalid, the update aborts cleanly — no files are rewritten, no services are restarted, and the install lock is released so you can retry after investigating. This guarantees qb update seerr will never silently re-assign your port or corrupt your deployment if the state on disk is partially damaged.

nginx Management

Reload nginx after configuration changes:

bash
# Test configuration
sudo nginx -t
 
# Reload nginx
sudo systemctl reload nginx

FAQ

Best practices

Do

  • Use qb install seerr -u username for new installations (add -d domain when needed)
  • Run qb update jellyseerr -u username or qb update overseerr -u username to auto-migrate existing installations to Seerr
  • Check service health with systemctl status seerr@username and tail logs with journalctl -u seerr@username -f
  • Reload nginx after adding or removing a domain: sudo systemctl reload nginx
  • Set up Discord or email notifications for request updates to keep users informed
  • Configure user quotas to prevent request spam (5-10 requests per week is a good starting point)
  • Enable approval workflows for non-admin users to moderate content requests
  • Regularly sync media server libraries to keep Seerr metadata updated
  • Take a manual backup before major changes: create one in Content → Asset Management Center → Application Backups on the v4 dashboard (restore it from the app's row on the App Dashboard, see <a href="/docs/dashboard/app-management">App Management</a>), or run qb manage software -o backup -o app -u username -s seerr for a Full Backup. A manual backup also replaces settings.json in /home/username/.QuickBox/software/seerr/backup/, so the install/reinstall/update copy there is not independent of it, and a reinstall deletes that whole folder: copy backups you want to keep elsewhere.

Don't

  • Avoid changing generated nginx files without a backup; ask support to reconcile a broken proxy with the saved port assignment
  • Keep the internal PORT=, database public port, and nginx listener consistent; preserve configuration and contact support if they disagree, rather than reinstalling and deleting data
  • Don't install both Seerr and Jellyseerr/Overseerr for the same user -- use migration instead
  • Don't grant admin access to all users -- use request quotas and approval workflows
  • Don't configure multiple default servers in Sonarr/Radarr settings -- causes request routing conflicts
  • Don't ignore failed notifications -- check logs and fix webhook/SMTP issues
  • Don't forget to configure root folders in Sonarr/Radarr -- requests will fail without valid paths

Node.js security minimum

Seerr selects Node.js from the chosen release’s requirements and raises it to the QuickBox security minimum when necessary. pnpm is selected from the same release, rather than a fixed version in this guide. The current QuickBox policy sets 22.23.4 as the minimum for Node.js 22. This is a security minimum, not a permanent version pin; later QuickBox updates can raise it.

QuickBox checks existing app copies during qb update quickbox and attempts to raise copies below the security minimum. An app update also applies the policy. Check the app-specific copy as the affected account:

bash
sudo -u username /opt/username/lib/nodejs/Seerr/.venv/bin/node --version

The shell’s node --version may report a different system or user-managed installation. It does not identify the copy QuickBox provisions for Seerr. Do not downgrade Node.js to match an older example or replace the system Node.js package as a workaround.

Troubleshooting

”The Node.js security floor list cannot be read”

If an install or update reports The Node.js security floor list (/opt/quickbox/config/software/node-security-floor) cannot be read, QuickBox could not validate its security policy. The file can exist and still fail validation: unreadable contents, a malformed entry, or a missing min= entry all cause this error. The application step stops rather than choosing an unverified Node.js version.

Run these read-only checks as the server administrator:

bash
ls -l /opt/quickbox/config/software/node-security-floor
sed -n 'l' /opt/quickbox/config/software/node-security-floor

The list contains a min=x.y.z entry and release-line entries such as 22=22.23.4; each numbered key must match the major in its version. Comments and blank lines are allowed. The sed output also exposes unexpected characters and line endings, so send its exact output rather than only a directory listing.

If QuickBox has not finished updating, complete qb update quickbox first and retain any update errors. If that succeeds but this error persists, send support the two checks above, the exact failing command, OS and QuickBox versions, and the relevant package-log excerpt. Retry qb update seerr -u username only after the policy issue has been resolved; use the install command instead for an installation that never completed.

Do not bypass the security check
Warning

Do not create or edit the policy file manually or bypass the check.

Node.js security update could not finish

If the QuickBox update says the app still runs a version below the security floor, the attempted move failed and the old runtime may still be in use. Resolve the logged failure, then retry qb update seerr -u username. Keep any further error output for support.

If the update specifically says seerr@username.service could not restart after replacing Node.js, inspect its journal, then run systemctl restart seerr@username. Confirm the app opens from the App Dashboard after the restart. The version command above checks the copy on disk, so it alone does not prove a previously running process switched to the new binary.

Restore-failed warning
Warning

A restore-failed warning means the app may not start. Do not delete recovery directories or use reinstall as the first repair.

Install hangs waiting for settings.json

The installer starts seerr@username and waits up to 60 seconds for /opt/username/Seerr/config/settings.json. A timeout means first launch did not produce that file; the journal and build output explain why. Replace username with the affected QuickBox account and run these read-only checks as the server administrator:

bash
systemctl status seerr@username --no-pager
journalctl -u seerr@username -n 100 --no-pager
tail -n 200 /opt/quickbox/logs/qb.log
ls -la /opt/username/Seerr/config/
ls -l /opt/username/Seerr/dist/index.js
sudo -u username /opt/username/lib/nodejs/Seerr/.venv/bin/node --version
df -h /opt /home
df -i /opt /home
free -h

MODULE_NOT_FOUND or a missing dist/index.js points to an incomplete build. EACCES points to an access problem; ENOSPC can mean either disk blocks or inodes are exhausted. A missing Node.js binary means the runtime setup did not finish. Resolve the specific error before retrying. Check the Node.js security minimum for the expected runtime rather than the shell’s node --version.

For an existing registered install, back up your settings and database, then retry the update:

bash
qb update seerr -u username

For a fresh installation that never completed, retry qb install seerr -u username after addressing the logged failure. If it still times out, send support the exact failing command, QuickBox version, OS version, journal, and relevant build-log excerpt. Redact credentials, API keys, and private URLs.

General install and update troubleshooting

Use the same checks for a failed update or a service that exits immediately. The update builds the new release separately before replacing the live app; if it reports rollback, inspect the reported error before retrying. A service marked active is only one check: open Seerr from its row in the App Dashboard and confirm the page loads and your settings are present.

Reinstall removes Seerr data
Caution

Both qb reinstall seerr -u username and qb remove seerr -u username remove the application, isolated environments, and configuration. Copy /opt/username/Seerr/config/ and any existing recovery backups to a separate location before either command. Reinstall is not a data-preserving repair for a missing module or failed runtime update.

Service will not start

Check systemctl status seerr@username --no-pager and journalctl -u seerr@username -n 100 --no-pager first. Check the exact Node.js binary and dist/index.js using the commands above. For a port conflict, read only the port line and compare it with the listeners:

bash
grep '^PORT=' /opt/username/Seerr/env.conf
ss -ltnp

The internal port in env.conf belongs to the Node.js process; the public nginx port is 10000 lower. Do not replace either with a guessed default. After resolving the cause, retry qb update seerr -u username; if it fails, retain the error and contact support before removing the install.

404 on the Seerr URL

404 on Seerr URL
Warning

Symptom: Accessing Seerr through the reverse proxy returns 404 Not Found.

Checks:

  1. Verify the apps-http nginx config exists: ls -la /etc/nginx/apps-http/username.seerr.conf
  2. Look up the user’s internal port: grep PORT /opt/username/Seerr/env.conf
  3. Confirm the nginx config’s proxy_pass target matches that internal port
  4. Test nginx config: sudo nginx -t
  5. Check service status: systemctl status seerr@username (should be active)
  6. Verify the Node.js process is listening on its internal port: ss -tuln | grep "$(grep -oP 'PORT=\K\d+' /opt/username/Seerr/env.conf)"

Resolution: Reload nginx with sudo systemctl reload nginx. If the internal or public port drifted, preserve your configuration and ask support to reconcile the saved port with nginx before retrying qb update seerr -u username. If a domain was installed, ensure /etc/nginx/sites-enabled/username.seerr.conf references the active certificate paths under /etc/nginx/ssl/domain.

Cannot connect to Sonarr or Radarr

Cannot connect to Sonarr/Radarr
Caution

Symptom: Seerr reports “Failed to connect to Radarr” or “Failed to connect to Sonarr”.

Checks:

  1. Verify services are running:
    bash
    systemctl status sonarr@username
    systemctl status radarr@username
  2. Test API connectivity:
    bash
    curl http://localhost:7878/api/v3/system/status?apikey=YOUR_RADARR_API_KEY
    curl http://localhost:8989/api/v3/system/status?apikey=YOUR_SONARR_API_KEY
  3. Verify API keys match in Seerr settings
  4. Check hostname configuration: use localhost (not 127.0.0.1 or server IP)

Resolution: Update Seerr connection settings with correct API keys and ensure “Default Server” is checked for your primary Sonarr/Radarr instance.

Requests not sending to Sonarr or Radarr

Requests not sending to Sonarr/Radarr
Warning

Symptom: User requests are approved but not appearing in Sonarr/Radarr.

Checks:

  1. View Seerr logs: journalctl -u seerr@username -f | grep -i error
  2. Verify “Default Server” is configured: Settings > Services > Radarr/Sonarr > Check ‘Default Server’
  3. Ensure quality profiles exist and are selected
  4. Verify root folders are configured and paths are valid

Resolution: Test manual request from Seerr UI and watch logs. Ensure quality profile and root folder are properly configured.

qb update seerr aborted with a port resolution error

qb update seerr aborted — could not determine port
Warning

Symptom: Running qb update seerr -u username stops early with a message that the public port could not be resolved. The install lock is released automatically — you can retry once the underlying state is fixed.

What this means: The updater intentionally refuses to continue if it cannot recover a valid public port from any of its trusted sources. This is a safety guard that prevents a partially-corrupt deployment from being rewritten with an invalid port (for example, listen 0 ssl; in nginx or a 0 in the database). No files are touched when this guard fires.

Checks:

  1. Check env.conf: cat /opt/username/Seerr/env.conf — expect a line like PORT=15055. If the file is missing, empty, or the value is 0, the first source has failed.
  2. Check the database port: inspect user_software.software_port for this user in the QuickBox database. A value of 0, NULL, or a missing row means the second source has failed.
  3. Check the nginx listener: grep -E '^\s*listen' /etc/nginx/apps-http/username.seerr.conf — expect a real port followed by ssl. A listen 0 ssl; line means the third fallback is also corrupt.
  4. Look for a prior failed install/update that may have left partial state behind.

Resolution: Preserve /opt/username/Seerr/config/ and the diagnostic output, then open a Discord support ticket  to reconcile the saved port sources. Reinstall removes the configuration directory, so do not use it as a port repair without an independent backup and a recovery plan.

Seerr is missing after an interrupted update

An update builds the new release in /opt/username/.Seerr-staging, moves the live install to /opt/username/.Seerr-rollback, then moves the new release into place. If the update stops between those two moves, /opt/username/Seerr is missing, Seerr is down, and your previous install is waiting in the rollback folder. Check which folders exist:

bash
ls -ld /opt/username/Seerr /opt/username/.Seerr-rollback

If /opt/username/.Seerr-rollback exists, run the update again. It moves the install back from the rollback folder before it reads the port or clears old folders, then carries on with the update:

bash
qb update seerr -u username

When it finishes, confirm the service is running and open Seerr from its row in the App Dashboard:

bash
systemctl status seerr@username --no-pager

If neither folder exists, the application and its configuration are gone. What is left is in the backup folder: the settings.json and db.sqlite3 that Seerr saves at install and at the start of each update, and any Full Backup archives named seerr-VERSION-application_DATE.tar.gz. List it:

bash
ls -la /home/username/.QuickBox/software/seerr/backup/

A Full Backup is normally restored with qb manage software -o rollback -o app -s seerr -u username, but that command stops with an install-directory error while /opt/username/Seerr is missing. A reinstall also clears the list of backups that rollback reads, so rollback cannot see archives copied back afterwards. Recover the settings and database from the files instead, using whichever copy is newer.

Save the backup folder before reinstalling
Caution

Copy /home/username/.QuickBox/software/seerr/backup/ somewhere outside .QuickBox before reinstalling. Reinstall deletes that folder, including every Full Backup archive and the saved settings and database, and it clears the rollback list. The new install saves first-boot defaults in its place.

QuickBox still lists Seerr for the account, so install refuses and reinstall is the command. Copy the backup folder, then reinstall Seerr:

bash
sudo -u username cp -a /home/username/.QuickBox/software/seerr/backup /home/username/seerr-backup-saved
qb reinstall seerr -u username

When the reinstall finishes, stop Seerr, put the settings and database back, and start it again. To use the saved settings.json and db.sqlite3:

bash
systemctl stop seerr@username
sudo -u username rm -f /opt/username/Seerr/config/db/db.sqlite3-wal /opt/username/Seerr/config/db/db.sqlite3-shm
sudo -u username cp /home/username/seerr-backup-saved/settings.json /opt/username/Seerr/config/settings.json
sudo -u username cp /home/username/seerr-backup-saved/db.sqlite3 /opt/username/Seerr/config/db/db.sqlite3
systemctl start seerr@username

To use a Full Backup instead, unpack its settings and database from the saved copy, replacing VERSION and DATE with the values in the archive name, then copy them in:

bash
sudo -u username mkdir /home/username/seerr-backup-saved/unpacked
sudo -u username tar -xzf /home/username/seerr-backup-saved/seerr-VERSION-application_DATE.tar.gz -C /home/username/seerr-backup-saved/unpacked ./config/settings.json ./config/db/db.sqlite3
systemctl stop seerr@username
sudo -u username rm -f /opt/username/Seerr/config/db/db.sqlite3-wal /opt/username/Seerr/config/db/db.sqlite3-shm
sudo -u username cp /home/username/seerr-backup-saved/unpacked/config/settings.json /opt/username/Seerr/config/settings.json
sudo -u username cp /home/username/seerr-backup-saved/unpacked/config/db/db.sqlite3 /opt/username/Seerr/config/db/db.sqlite3
systemctl start seerr@username

The rm line removes the db.sqlite3-wal and db.sqlite3-shm files that belong to the new, empty database. They must not be paired with the restored db.sqlite3.

Open Seerr from the App Dashboard and confirm your settings and requests are back. Use the saved copy for this restore: qb manage software -o restore -u username -s seerr reads only the backup folder, which the reinstall has just replaced, and it restores settings.json alone, not the database. If a file is missing from the saved copy or Seerr does not start, keep /home/username/seerr-backup-saved and send support its listing together with journalctl -u seerr@username -n 100 --no-pager.

Take a manual backup

For guaranteed point-in-time snapshots, take a manual backup
Info

The automatic copy written to /home/username/.QuickBox/software/seerr/backup/ only runs at install, reinstall, and at the start of an update. If you want a snapshot of your Seerr configuration and request database on demand — before editing settings, before a reinstall, or just on a schedule — take a manual backup.

From the v4 dashboard: to create a backup, open Content → Asset Management Center (shown as AMC in the sidebar), choose the Application Backups tab, expand the Seerr row and click Back up now. The menu offers Full Backup, Config Only and, when the app has an nginx config, Nginx. The same row lists each saved file with download and delete buttons, plus Delete all. Files that are not archives also have a view button; Full Backup archives offer download and delete only. The tab is shown to administrators and to accounts granted Asset Management Center access. To restore, open the App Dashboard, stay on Application Control, expand the Seerr row and click Restore in the Operations section. The Restore backup: Seerr window lists config, nginx and full backups, and the window’s Restore button reads Rollback when you pick a full backup. Restore appears only when your account is allowed to restore backups. See App Management for the full App Dashboard flow.

From the CLI: run qb manage software with the backup operation:

bash
# Back up Seerr's settings file only (settings.json, not db.sqlite3)
qb manage software -o backup -u username -s seerr
 
# Back up the install directory, including its config folder with settings.json and db.sqlite3, as timestamped tarballs
qb manage software -o backup -o app -u username -s seerr

Both variants write to /home/username/.QuickBox/software/seerr/backup/ with a timestamped filename. The first saves settings.json only and never db.sqlite3. Both also replace settings.json in that folder, which is the copy -o restore reads, so neither leaves the install or update copy untouched. Use qb manage software -o restore -u username -s seerr to restore the most recent configuration backup, or -o rollback -o app to restore a full-application backup.

Media Servers

3

Media Management

2

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