SOLVED: Stream stopping every 20-30mins - Help required

[xanor]

Hey there!

I've got an issue with my jellyfin setup. First, about the setup:

VM on Proxmox
Running official jellyfin docker container through a reverse proxy
Version: 10.10.3
RAM: 8GB
CPU: 8 Cores AMD Ryzen 5 2600


Client: Jellyfin Client for LG webOS
Network: All connected to Gigabit LAN


Every time I watch a 4k HDR stream on my TV, the stream crashes after roughly 30mins. According to logs, yesterday it was after 33mins, then 31mins, 37, 15, 24, and 23mins when the movie finished. I've attached logs and screenshots from it, but as I don't really know that much about jellyfin and video streaming, I require some help to get to the bottom of this. Please tell me what else I need to attach to find the issue!


There's no hardware transcoding as my server doesn't have a GPU, but it's not running on 100% CPU utilization. And once I restart the stream, it works fine for another ~30mins. Not sure what's causing this.

Thanks a lot for all help!

[TheDreadPirate]

How much free space does your storage have? The partition where /cache is mounted.

[xanor]

It's a 40GB partition. But I just checked it and dangling docker files were reducing it to just 10G free space...
I'm guessing this could be a culprit? To prevent this in the future, I'd add a second partition and only mount the cache on it, how big should that be?

[TheDreadPirate]

Yes. Transcodes are written to disk. If these 4K HDR movies are like 70-80 GB, the transcode would take up AT LEAST that much space. You can enable transcode throttling and Delete segments in the transcode settings to reduce the amount of disk space needed.

Dashboard > Playback > Transcoding. They're located at the bottom.

[xanor]

Thanks a lot! I'll give this a try!

[Jaga srini]

Yeah, that’s a frustrating one. From what you’ve described, it doesn’t sound like your CPU is choking, so I’d lean more toward a network or buffering issue rather than raw processing power. Even without hardware transcoding, if Jellyfin is doing HDR→SDR tone mapping or bitrate tweaks, it can still cause hiccups over time. I’ve seen some setups drop around that 30‑minute mark because of client buffer limits or a tiny network drop that kills the session.

If possible, try forcing direct play by matching your file format and bitrate to your TV’s native capabilities. Also, test on wired Ethernet to rule out Wi‑Fi flakiness.

On my end, I’ve avoided these headaches by using a VPlayed‑powered setup—lets me fine‑tune adaptive bitrate, buffering, and segment size so 4K HDR runs smoothly without random drop‑offs.