this post was submitted on 25 Apr 2025
37 points (95.1% liked)

Selfhosted

46290 readers
458 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.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
37
Sharing Jellyfin (poptalk.scrubbles.tech)
submitted 13 hours ago by scrubbles@poptalk.scrubbles.tech to c/selfhosted@lemmy.world
63 comments fedilink hide all child comments
 

Hi folks. So, I know due to a myriad of reasons I should not allow Jellyfin access to the open internet. However, in trying to switch family over from Plex, I'll need something that "just works".

How are people solving this problem? I've thought about a few solutions, like whitelisting ips (which can change of course), or setting up VPN or tail scale (but then that is more work than they will be willing to do on their side). I can even add some level of auth into my reverse proxy, but that would break Jellyfin clients.

Wondering what others have thought about for this problem

you are viewing a single comment's thread
view the rest of the comments
[–] daniskarma@lemmy.dbzer0.com 27 points 13 hours ago* (last edited 12 hours ago) (3 children)

You can share jellyfin over the net.

The security issues that tend to be quoted are less important than some people claim them to be.

For instance the unauthorized streaming bug, often quoted as one of the worst jellyfin security issues, in order to work the attacker need to know the exact id of the item they want to stream, which is virtually impossible unless they are or have been an authorized client at some point.

Just set it up with the typical bruteforce protections and you'll be fine.

[–] possiblylinux127@lemmy.zip 1 points 1 hour ago

Fine is a relative term

You probably are fine but the company who is getting attacked by your compromised machine isn't

[–] MaggiWuerze@feddit.org 3 points 6 hours ago (1 children)

It's not impossible, Far from it. The ids are not random uuids but hashes derived from the path. Since most people have a similar setup to organize their media, this gets trivial very fast

[–] synestine@sh.itjust.works 2 points 6 hours ago

If you're worried about it, make sure to not use a default path. Then legit clients are fine but these theoretical attackers get stymied.

[–] BlackEco@lemmy.blackeco.com 12 points 12 hours ago* (last edited 12 hours ago)

This. Just setup fail2ban or similar in front of Jellyfin and you'll be fine.