Selfhosted

60076 readers

631 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Sharing Jellyfin (poptalk.scrubbles.tech)

submitted 1 year ago by scrubbles@poptalk.scrubbles.tech to c/selfhosted@lemmy.world

30 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

[–] MaggiWuerze@feddit.org 0 points 1 year 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 0 points 1 year ago (1 children)

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.

[–] MaggiWuerze@feddit.org 0 points 1 year ago (2 children)

What? Why would I have to make my library harder to manage just because Jellyfin devs can't get their act together? They should just start a api/v2 and secure it properly while allowing to disable the old one

[–] synestine@sh.itjust.works 0 points 1 year ago (1 children)

Ah, so you're the kind who loves bitching about things online, but won't lift a finger to defend themself, gotcha.

What I mentioned prior doesn't change anything about library management in the slightest, you just wanted an excuse.

[–] MaggiWuerze@feddit.org 1 points 1 year ago

No, I'm the kind who thinks security by obscurity is bullshit. But you do you

[–] blitzen@lemmy.ca 0 points 1 year ago

I’m with you that you shouldn’t have to, but putting your media directory one level up in a randomly generated directory name isn’t too bad. ~/[random uuid]/media/… may not be a terrible idea in any case.