this post was submitted on 01 Apr 2026
49 points (96.2% liked)

Selfhosted

60093 readers
967 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam.

  3. Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.

  4. Don't duplicate the full text of your blog or git here. Just post the link for folks to click.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, and your account is at least 7 days old, your post is exempt from this rule as long as you continue to engage in comments.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

I tried "all" settings. I tried reading the logs and norhing helped. I had many months without issues. How do you guys debug it? The logs aren't too helpful for me and there are too many settings for me to play with. I've got an intel GPU with eirher QSV or VAAPI. Disabling does not work either. CPU is normal, GPU is normal. RAM is not full.

Edit:

  • one drive was failing. SMART showed a dying drive. I replaced it and everything is smooth again. That is why I couldn't find anything within the logs. And until today I didn't know how to read io properly and check for smart status.

Things to watch out for

  • cpu usage
  • gpu usage
  • right gpu tools. Properly passed to container. Properly used by jellyfin.
  • proper transcoding settings with the gpu within jellyfin
  • ram
  • storage of drives
  • io write/read speed
  • jellyfin folders on ssd, media on hdd
  • healt / smart status of drives
  • lan bottleneck
you are viewing a single comment's thread
view the rest of the comments
[–] statelesz@slrpnk.net 4 points 2 months ago (1 children)

How are you accessing Jellyfin? Local only, via VPN and/or reverse proxy? Anything else you have changed on the system in general?

[–] illusionist@lemmy.zip 2 points 2 months ago (2 children)

Local only via LAN.

I did not change much. Updates of fire tv stick, jellyfin. And now I changed so many settings that I don't know which ones I had before. But, I tried a new clean jellyfin instance and it's the same. Sometimes it works and I am happy to have found the right settings but then the next day it stutters again. There is no otherr service running.

[–] gdog05@lemmy.world 2 points 2 months ago (1 children)

Are you using wireless? I'm guessing your router is occasionally being oversaturated with traffic. I would turn your streaming quality down to around 2mb and then stream to your device. You can open up Jellyfin in a browser and check the steam information in the Jellyfin Dashboard to check the speed. Keep bumping it up if you want better quality.

If you're trying to prevent transcoding, then I suggest downloading or ripping lower bitrate content.

If you happen to have a spare router, I would try adding it as an access point and keep your Jellyfin source machine and streaming device on that access point. That should keep the traffic from going through your primary router.

[–] illusionist@lemmy.zip 2 points 2 months ago

A disk was failing, I updated my post

[–] JigglySackles@lemmy.world 1 points 2 months ago* (last edited 2 months ago) (1 children)

Try clean jellyfin but revert one version prior instead of the update you are on. At the very least, this will let you rule out version for jellyfin. The fire stick update may have broken it too. Updating and then having issues overwhelmingly points to the update being the primary suspect.

[–] illusionist@lemmy.zip 2 points 2 months ago (1 children)

A disk was failing, I updated my post

[–] JigglySackles@lemmy.world 0 points 2 months ago

Glad you found the root cause!