this post was submitted on 25 Apr 2025
81 points (96.6% liked)

Selfhosted

46341 readers
438 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
 

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 38 points 1 day ago* (last edited 1 day ago) (10 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 4 points 1 day ago (4 children)

Fine is a relative term

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

[–] daniskarma@lemmy.dbzer0.com 7 points 1 day ago* (last edited 23 hours ago) (1 children)

I don't think jellyfin vulnerabilities could lead to a zombified machine. At least I've not read about something like that happening.

Most Jellyfin issues I know are related to unauthorized API calls of the backend.

[–] possiblylinux127@lemmy.zip 1 points 20 hours ago (1 children)

I think it is a matter of time honestly.

Jellyfin has grown enough in popularity that it is likely a target for a state actor looking to create some minions. Just because there isn't any known remote code execution vulnerabilities doesn't mean there couldn't be one in the future.

Maybe I'm being paranoid but it seems way safer to just not expose Jellyfin.

[–] daniskarma@lemmy.dbzer0.com 2 points 15 hours ago (1 children)

Any software can have zero-day exploits for that matter.

[–] possiblylinux127@lemmy.zip 1 points 12 hours ago

That's is absolutely true

Avoid exposing things unless you really need to and follow best practices.

load more comments (2 replies)
load more comments (7 replies)