Jellyseerr is the request-management front end for the media stack. It integrates with Jellyfin and the Arr services to turn user requests into managed acquisition workflows.
This page documents the jellyseerr service. It does not replace the pages for Jellyfin, Sonarr, Radarr, or the download clients it orchestrates.
- Container:
jellyseerr
- Image:
fallenbagel/jellyseerr:latest
- Stack: Smithflix Stack
- Compose path:
/opt/stacks/smithflix/docker-compose.yml
- Docker network:
smithflix_default
- Restart policy:
unless-stopped
- Health state: healthy on
2026-04-07
- Verified public hostname:
requests.better-than.tv
¶ Config and Data Paths
- Verified config root:
/srv/docker/jellyseer/config
- Note the path spelling:
jellyseer, not jellyseerr
- Primary settings file:
/srv/docker/jellyseer/config/settings.json
- Additional app directories:
/srv/docker/jellyseer/config/db, /srv/docker/jellyseer/config/logs, /srv/docker/jellyseer/config/cache
- LAN URL:
http://192.168.0.113:5055
- Public URL:
https://requests.better-than.tv
- Host port mapping:
5055 -> 5055
jellyseerr.better-than.tv was not verified as an active proxy host on 2026-04-07
¶ Authentication and Secret Locations
- App auth and integration settings are stored under
/srv/docker/jellyseer/config
- Jellyfin and Arr credentials are managed inside the application config, not in compose
- Requests proxy behavior includes custom buffering settings in NPM to keep login responses out of
proxy_temp
- Validate the app locally on
:5055 before debugging the proxy
- Keep Jellyfin, Sonarr, and Radarr integrations healthy because Jellyseerr depends on all three domains
- Document the nonstandard config path spelling accurately when changing backups, scripts, or mounts
- If request flows break, check Jellyseerr first for sync or upstream auth issues before blaming the users
¶ Monitoring and Logs
- Docker logging driver is
json-file
- The container healthcheck was healthy on
2026-04-07
- Recent logs showed normal Jellyfin sync activity and recently-added scans
- On-disk logs are available under
/srv/docker/jellyseer/config/logs
¶ Backup and Restore
/srv/docker/jellyseer/config is inside the documented Duplicati scope because it lives under /srv/docker- Restore should preserve the full config root so app settings, DB state, and logs stay aligned
- After restore, validate Jellyfin sync and a test request path
¶ Failure Modes and Recovery
- If Jellyfin or Arr auth breaks, Jellyseerr can remain healthy while request fulfillment stops working
- Misdocumenting the config root as
jellyseerr instead of jellyseer can cause backup and restore omissions
- Proxy issues on
requests.better-than.tv can surface as login or session problems even when LAN :5055 is healthy