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

  • MaggiWuerze@feddit.org
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    4
    ·
    19 hours ago

    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
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      2
      ·
      19 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.

      • MaggiWuerze@feddit.org
        link
        fedilink
        English
        arrow-up
        3
        ·
        2 hours ago

        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