Skip to content

Jellyfin (Core Service)

Jellyfin is an open-source media server for organizing and streaming your media library. It can be used as an alternative to Plex or Emby.

At a glance

Use the same curated library folder in your collector and media server. A running server is only the first check.

flowchart TD
    A["Open Jellyfin and finish sign-in"] --> B
    B["Choose the curated library folder"] --> C
    C["Check the mount before scanning"] --> D
    D["Scan a small library"] --> E
    E["Play and seek through one item"]

First start

  1. Select Jellyfin during DUMB onboarding. Open its service card and, on DUMB Config, use Start if stopped. Select Embedded UI to open Jellyfin.
  2. Complete Jellyfin's setup wizard and create the administrator account, or sign in to your existing server. Keep the account credentials for future library and playback changes.
  3. Add a library for each media type and browse to the curated folder used by your download workflow. These are paths inside DUMB, usually below /mnt/debrid, rather than paths from your computer. Use the folder saved in Sonarr/Radarr or your collector's settings.
  4. Review scan and automatic removal settings before scanning a remote library. Confirm the provider mount is available, then run the first library scan.
  5. Open the library, play one item and seek to another point. If it is missing, compare the library folder with the workflow's saved folder; if playback fails, check the provider connection and whether Jellyfin needs transcoding.
  6. Configure remote access, sharing and hardware acceleration after local playback works. Host GPU access and the application's transcoding settings are separate setup steps.

Setup checklist and remaining work

The checklist guides supported fresh-administrator setup and explicit library creation/reuse. Existing initialized servers are not reinitialized. Supported new-library forms offer an optional initial scan, off by default; review the paths before enabling it. Existing libraries are not rescanned by this creation choice. Choose sharing, remote access, hardware acceleration and playback policy, then test real library access/playback.

Requires the backend setup-arrangement capability. See Setup checklist and automation for retained tasks, coverage and safe retries.

Service Relationships

Classification Role
Core Service Media server
Depends On Content in /mnt/debrid
Optional None
Exposes UI Yes (Web UI)

Technical details: configuration reference

Configuration in dumb_config.json

{
"jellyfin": {
  "enabled": false,
  "process_name": "Jellyfin Media Server",
  "suppress_logging": false,
  "auto_update": false,
  "auto_update_interval": 24,
  "auto_update_start_time": "04:00",
  "pinned_version": "",
  "port": 8096,
  "config_dir": "/jellyfin",
  "config_file": "/jellyfin/config/system.xml",
  "log_file": "/jellyfin/log/jellyfin.log",
  "command": [],
  "env": {}
}
}

Key configuration fields

  • pinned_version: Optional version pin for Jellyfin updates.
  • port: Web UI port (default 8096).
  • config_dir, config_file, log_file: Paths for config and logs.
  • command: DUMB rebuilds the data/config/cache/log arguments during setup. An explicit --ffmpeg selection is preserved; otherwise DUMB selects /usr/lib/jellyfin-ffmpeg/ffmpeg when installed.

Accessing the UI

Open the service from DUMB's Embedded UI tab when available. The native URLs below require the corresponding Docker host port to be published; use the port saved in your running configuration.

  • Navigate to: http://<host>:8096 (default Jellyfin port)
  • With service UIs enabled in DUMB, open Embedded UI on the Jellyfin service page and sign in to Jellyfin there.

If existing libraries appear at the direct address but not in the iframe, see Jellyfin and Emby embedded libraries.

Fresh Jellyfin installs add the official Jellyfin APT source directly. They do not require the add-apt-repository utility, which is intentionally absent from the minimized DUMB runtime image.

Hardware acceleration

For a supported GPU that has been made available to DUMB, open Dashboard → Playback → Transcoding in Jellyfin. Select the acceleration method and supported codecs, save, and test a short transcode. Passing a device into the container does not enable these settings automatically.

Host device mapping requires deployment access. See GPU setup for native Proxmox and Jellyfin's Intel GPU guide when preparing that access.

Geek details: GPU permissions, FFmpeg selection and driver defaults

DUMB launches Jellyfin as its configured puid/pgid. With /dev/dri present, DUMB adds its service account to existing render and video groups at startup. Managed processes receive those supplementary groups, including after a restart; Docker group_add grants are retained as well. The device's numeric group must still be accessible inside the container or LXC.

Jellyfin uses its packaged FFmpeg when available. Keep /usr/bin/ffmpeg owned by the distribution package; replacing it with a symlink affects other services. To use a custom build, supply --ffmpeg, followed by its absolute path, in jellyfin.command.

For an Intel-only render-device setup with an installed iHD driver, DUMB defaults LIBVA_DRIVER_NAME to iHD. An explicit value in jellyfin.env or the controller environment takes precedence. AMD and mixed-vendor systems retain driver autodetection. Select the acceleration method and supported codecs in Jellyfin's Dashboard → Playback → Transcoding settings; device passthrough alone does not enable transcoding.

See native Proxmox GPU setup and Jellyfin's Intel GPU guide.

Geek details: Intel OpenCL runtime and device diagnostics

Intel OpenCL tone mapping

AMD64 DUMB images include the distribution's current and legacy Intel OpenCL GPU runtimes, generic ICD loader and clinfo. They are installed when the image is built, so updating or recreating the container does not require reinstalling them manually. ARM64 images do not install these Intel GPU packages. This does not install a host kernel driver or provide AMD/NVIDIA runtime support.

The current and legacy packages cover different Intel GPU generations. Check the upstream supported-platform list and legacy platforms for your hardware. The host still needs a working GPU driver, a passed-through /dev/dri/renderD* device and permission for DUMB's configured service account to use that device. The runtime packages do not enable Jellyfin's transcoding settings automatically.

Replace dumb with your container name, and select the correct render device:

docker exec dumb clinfo -l
docker exec dumb /usr/lib/jellyfin-ffmpeg/ffmpeg -v verbose \
  -init_hw_device vaapi=va:/dev/dri/renderD128 -init_hw_device opencl@va \
  -f lavfi -i color=size=16x16:rate=1 -frames:v 1 -f null -

The second command checks device initialization and VA-API/OpenCL interoperability. Repeat device checks with the same user and GPU groups as Jellyfin; a successful root-run check does not verify the service account's access. Package installation or an empty clinfo result does not establish working GPU tone mapping. Configure OpenCL tone mapping in Jellyfin, then test a short HDR transcode and inspect Jellyfin's FFmpeg log before relying on it for playback. See Jellyfin's Intel guide for the current hardware and codec requirements.

Media Library Protection

Jellyfin requires an authorized API key before DUMB can inspect sessions and temporarily control scan tasks/library real-time monitoring. Create a key in Jellyfin's dashboard and save it under Library Protection on the Jellyfin service page. Review the configured mount scope and enablement. Without usable credentials, unattended storage maintenance is deferred because activity is unknown.

The guided first-administrator task can create a dedicated application key. Saving it for Library Protection is a separate explicit checklist choice; a new setup-created protection policy stays disabled until reviewed.

See Media Library Protection.


Resources