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

  • Possibly linux@lemmy.zip
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    4
    ·
    18 hours ago

    That’s a bad idea for so many reasons

    The internet is full of bots pounding at your machines to get in. It is only a matter of time until the breach Jellyfin. At the very least you want a reverse proxy with proper security.

    I don’t see why you would put something like Jellyfin in the internet. Use a VPN solution.

    • dogs0n@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      3
      ·
      7 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
        ·
        4 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

    • daniskarma@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      7
      arrow-down
      1
      ·
      10 hours ago

      I have had jellyfin exposed to the net for multiple years now.

      Countless bots probing everyday, some banned by my security measures some don’t. There have never been a breach. Not even close.

      To begin with, of you look at what this bots are doing most of them try to target vulnerabilities from older software. I have never even seen a bot targeting jellyfin at all. It’s vulnerabilities are not worth attacking, too complex to get it right and very little reward as what can mostly be done is to stream some content or messing around with someo database. No monetary gain. AFAIK there’s not a jellyfin vulnerability that would allow running anything on the host. Most vulnerabilities are related to unauthorized actions of the jellyfin API.

      Most bots, if not all, target other systems, mostly in search of outdated software with very bad vulnerabilities where they could really get some profit.

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

        Your IP address is what they are after

        They quietly compromise your system and then your IP gets used as a proxy for attacks against larger targets like government institutions.

        How would you know that you were compromised?

        I know this sounds far fetched but if you remember there was a Lastpass breach due to Plex. You need to very careful with the public internet.