Skip to main content

03-emby.md

kstack: book: Centerpoint Home Lab chapter: Media & Entertainment page: Emby (Offline) tags: [emby, media, offline]

Overview

Status: OFFLINE — The Emby container is present on Centerpoint but is not currently running. It has been superseded by Jellyfin for open-source media serving needs. The container and its configuration are retained.

Emby was previously used as an alternative media server. Its configuration and data remain intact and the container can be restarted if needed, subject to the port 8096 conflict with Jellyfin (see Notes).

Access

Type URL Notes
Internal https://emby.home.local Traefik labels present — not routed while offline

Configuration

Image: emby/embyserver:latest Status: exited (container stopped)

Traefik Labels (inactive while container is stopped)

traefik.enable: "true"
traefik.http.routers.emby.rule: Host(`emby.home.local`)
traefik.http.routers.emby.entrypoints: websecure
traefik.http.routers.emby.tls.certresolver: step-ca
traefik.http.services.emby.loadbalancer.server.port: 8096

Volumes / Bind Mounts

Host Path Container Path Purpose
/home/jeeves/docker/emby/config /config Emby database and library config
/mnt/Multimedia/ST /data Media files (same NFS as Stash)

Notes / Gotchas

  • Emby and Jellyfin both use port 8096 internally. Only one can be host-bound at a time — starting Emby while Jellyfin is running will fail with a port conflict.
  • If reactivating Emby, stop Jellyfin first or remap Emby to a different host port.
  • The emby/embyserver:latest image tag pulls the latest release — verify compatibility with the existing config before restarting after a long pause.

Last Updated: 2026-06-16

No comments to display

Back to top