LXC Jellyfin start and jellyfin service stop after a few moment is almost always a container config problem, not a Jellyfin bug. Check the journal inside the container, match the exit signal, and fix the LXC setting that’s causing it.
Read the journal first
Jellyfin logs to journald inside the container. Run this right after it stops:
journalctl -u jellyfin -n 50 --no-pagerYou’re looking for the last lines before it died. If you see something like signal: terminated or status=1/FAILURE, that tells you it wasn’t Jellyfin crashing on its own — something told it to stop.
Match the exit signal to the LXC config
If the journal shows a SIGTERM or SIGKILL, the container’s resource limits are the usual suspect. Open the container config on the Proxmox host:
nano /etc/pve/lxc/<CTID>.confLook for lines like memory, swap, or cores. If Jellyfin hits the memory limit, the OOM killer inside the container will kill it. Same with CPU — if you’ve set cpulimit too low, systemd might consider the service hung and kill it.
But the one that bites people is features: nesting=1. Jellyfin sometimes needs it for hardware acceleration or certain plugins. If it’s missing, add it:
features: nesting=1Then restart the container. That alone has fixed the “starts then stops” thing for a lot of people.
Check the service file itself
Inside the container, look at how the service is defined:
systemctl cat jellyfinIf there’s a Restart=always but no RestartSec, systemd might be restarting it too fast and giving up. Or if the ExecStart points to a binary that doesn’t exist after an update, it’ll fail immediately. Make sure the path is right.
My take
Don’t go reinstalling Jellyfin or blaming the LXC template. Nine times out of ten it’s a resource limit or a missing feature flag. The journal tells you what signal killed it — match that to the config and you’re done. If you’re still stuck, check Proxmox container no internet: diagnose from host to CT because sometimes a network hiccup makes Jellyfin’s web server fail to bind and the service exits.
