Self-host EmbyStat with Levelrail
Watch statistics and insight dashboards for your Emby or Jellyfin server.
- Authormregni
- LicenceMIT
- Memory256 MiB
- Archarm64
- Services1
How to self-host EmbyStat
-
Pull the images
One image is pulled on your server.
Show images
lscr.io/linuxserver/embystat:latest
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 6555.
-
Fill in the secrets
3 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
EmbyStat requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 6555
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 6555 on the host, so open them in the VPS firewall only if you want that.
- Review. Image is not pinned to a version tag, so a redeploy can pull different code (lscr.io/linuxserver/embystat:latest).
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then EmbyStat. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the EmbyStat docs page.
Deploy EmbyStat your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy EmbyStat from the CLI
levelrail-cli templates deploy embystat --name my-embystat Deploy EmbyStat with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/embystat/deploy EmbyStat configuration
EmbyStat services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| embystat | lscr.io/linuxserver/embystat:latest | 6555 | embystat_config -> /config |
EmbyStat environment variables
| Variable | Service | Value |
|---|---|---|
| PGID | embystat | Preset by the template |
| PUID | embystat | Preset by the template |
| TZ | embystat | Preset by the template |
Ports and volumes
- Ports
- 6555
- Volumes
- 1 named mount: embystat_config -> /config
EmbyStat FAQ
How much memory does EmbyStat need?
The catalog lists about 256 MiB of memory for EmbyStat.
Does EmbyStat run on arm64?
For EmbyStat, an arm64 image is published; amd64 is image published.
What licence is EmbyStat under?
EmbyStat is licensed under MIT, which is permissive, with few conditions on reuse.
Does EmbyStat need configuration before it starts?
No. The template fills in its own defaults.
Which ports does EmbyStat use?
EmbyStat listens on port 6555 inside the stack.
Where does EmbyStat keep its data?
In a named volume: embystat_config mounted at /config.
Can I deploy EmbyStat on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for EmbyStat, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image lscr.io/linuxserver/embystat:latest is what you deploy there.