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

  • dogs0n@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    3
    ·
    9 hours ago

    The internet is full of bots pounding at your machines to get in. It is only a matter of time until the breach Jellyfin.

    If you are talking about brute force attacks for your password, then use a good password… and something like fail2ban to block ips that are spamming you.

    This point doesn’t exactly match, but: public services like google auth don’t require users use vpns. They have a lot more money to keep stuff secure, but you may see my point… auth isn’t too trivial of a feature to keep secure nowadays. They implement similar protections, something to block spammers and make users have good passwords (if you dont use a good password, you are still vulnerable on any service).

    • Possibly linux@lemmy.zip
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      6 hours ago

      The password is totally irrelevant for the most part. The worst case is that they get access to the dashboard

      The problem is when major security vulnerabilities are found like remote code execution