Skip to content

Emby (Core Service)#

Emby is a media server for organizing and streaming your media library. It is a commercial alternative to Plex and Jellyfin.


Service Relationships#

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

What Emby provides#

Endpoint Purpose Default
Web UI Emby browser UI http://<host>:8096/

Traefik access

If Traefik is enabled, the Emby UI is proxied at http://<host>:18080/service/ui/emby/; DUMB preserves Emby's internal /web path handling.


Configuration in dumb_config.json#

"emby": {
  "enabled": false,
  "process_name": "Emby Media Server",
  "repo_owner": "MediaBrowser",
  "repo_name": "Emby.Releases",
  "release_version_enabled": false,
  "release_version": "4.8.11.0",
  "use_system_ffmpeg": true,
  "suppress_logging": false,
  "log_level": "INFO",
  "port": 8096,
  "auto_update": false,
  "auto_update_interval": 24,
  "auto_update_start_time": "04:00",
  "config_dir": "/emby",
  "config_file": "/emby/config/system.xml",
  "log_file": "/emby/log/embyserver.txt",
  "command": [],
  "env": {}
}

Key Configuration Fields#

  • port: Web UI port (default 8096).
  • use_system_ffmpeg: Use the system ffmpeg binary when available.
  • release_version_enabled, release_version: Pin to a specific Emby release.
  • auto_update: Enable scheduled update checks (disabled when pinning releases).
  • config_dir, config_file, log_file: Paths for config and logs.

Release pinning

When release_version_enabled is set, DUMB treats the release as pinned and disables scheduled auto-updates for Emby.


Accessing the UI#

  • Navigate to: http://<host>:8096
  • Traefik proxy: http://<host>:18080/service/ui/emby/
  • With service UIs enabled in DUMB, open Embedded UI on the Emby service page and sign in to Emby there.

See Jellyfin and Emby embedded libraries for login and empty-library troubleshooting.

Media Library Protection#

Protection is enabled by default, but Emby requires a dedicated API key before DUMB can inspect sessions and temporarily control scan tasks/library real-time monitoring. DUMB does not create this key during Emby's first-run administrator setup. Create it in Emby's dashboard, then save it under Library Protection on the Emby service page. Until then, safe unattended storage maintenance is deferred because activity is unknown.

See Media Library Protection.


Health monitoring#

DUMB checks Emby's /emby/System/Ping endpoint. HTTP 200 with the plain-text reply Emby Server is a successful application ping. When the process and port checks also pass, DUMB displays Healthy.

Health details explain failed or unrecognized responses. The ping confirms server responsiveness; library access, media paths, and playback need their own checks. See health states and application probes.


Logs and data paths#

  • Config: /emby/config/system.xml
  • Logs: /emby/log/embyserver.txt

Terms of Service#

By enabling Emby, you confirm that you have read and agree to the Emby Terms of Service: * Emby Terms of Service


Resources#