this post was submitted on 26 Sep 2025
719 points (95.9% liked)

Selfhosted

53743 readers
349 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 posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

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

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Well I already have jellyfin running in a container, just have to figure out how to get mum's TV to work with it I guess

log in on a local IP and not the network name and it's working again. but I'll be moving to jellyfin from now

you are viewing a single comment's thread
view the rest of the comments
[–] TrickDacy@lemmy.world 5 points 2 months ago (23 children)

Imo Plex is worth the lifetime pass if you get it on sale.

All the comments saying Jellyfin is better always puzzle me. I've given it like three chances now and each time it feels just as buggy as the last. And that doesn't even consider the fact that you'll need more steps to expose it to the Internet for remote viewing or the fact that there's literally a list of unaddressed security holes https://github.com/jellyfin/jellyfin/issues/5415

[–] Strit@lemmy.linuxuserspace.show 20 points 2 months ago (9 children)

From one of the Jellyfin devs in the issue you linked, posted in April this year:

Now, let's address this clearly once and for all. What is possible is unauthenticated streaming. Each item in a Jellyfin library has a UUID generated which is based on a checksum of the file path. So, theoretically, if someone knows your exact media paths, they could calculate the item IDs, and then use that ItemID to initiate an unauthenticated stream of the media. As far as we know this has never actually been seen in the wild. This does not affect anything else - all other configuration/management endpoints are behind user authentication. Is this suboptimal? Yes. Is this a massive red-flag security risk that actively exposes your data to the Internet? No.

At this point, this over-4-year-old issue has gotten posted to HackerNews more than enough times and gotten quite enough unhelpful peanut-gallery comments like those above.. We are limiting this issue to Jellyfin collaborators only at this point. Most of the big items are already tracked elsewhere (specifically, unauth playback) or have already been fixed. And many other options are now open to us in a post-10.11 landscape now that we have a proper library database ready.

[–] TrickDacy@lemmy.world -2 points 2 months ago (8 children)

That only addresses one of several items.

[–] scrubbles@poptalk.scrubbles.tech 1 points 2 months ago

Feel free to go read the multiple writeups from the maintainers that go over each one, we don't need to copy them all here into the comments for you.

load more comments (7 replies)
load more comments (7 replies)
load more comments (20 replies)