Hi,

I’ve been trying to set up fail2ban for jellyfin both running in docker from compose and I’m doing something wrong.

Can someone tell me what path in the docker compose file you use for jellyfin logs and what path you use in the jail.d and the filter in filter.d?

Thanks

PS. Sorry for low detail, but I’m on phone and don’t have my current conf readily available. Will provide if necessary.

  • MaggiWuerze@feddit.org
    link
    fedilink
    English
    arrow-up
    29
    arrow-down
    3
    ·
    edit-2
    2 days ago

    If you plan to use fail2ban, I assume you want to make your Jellyfin accessible from the public internet. Please be aware, that large parts of the Jellyfin Backend are not properly authenticated and allow unauthorized, potential mapping of your library and even unauthorized streams.

    https://github.com/jellyfin/jellyfin/issues/5415

    • N0x0n@lemmy.ml
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      2
      ·
      10 hours ago

      The solution here is to use a wireguard (or similar technology) server and use it on all your devices. People already use VPNs for everything, so adding this layer isn’t that much of a hassle !

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

        That depends entirely on your target audience as well as the devices you want to use it on. Smart TVs don’t really support VPNs and my parents would not know how to even activate that let alone set it up on their end. I have a lot of non tech savvy users, so Plex is just way more convenient and accessible.

    • Zeoic@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      18 hours ago

      Wow, I tested out jellyfin every 6 months for the last few years to see if it was ready to replace plex yet, and I had no idea about such huge security issues. There should really be a big ass warning about making jellyfin publicly accessible in the app and in setup guides…

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

        The main issue for me is the way they react to it. Not only is there no warning about this, but they also refuse to fix it because it would break client support and they prefer backwards compatibility over security

    • basic_user@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      5
      ·
      2 days ago

      Thank you. I did see this list before. My jellyfin instance is not exposed to the net atm., but I’m thinking of exposing it in intervals and would like to have fail2ban working when/if I do.

    • Vendetta9076@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 days ago

      Would putting jellyfin behind authentik or googleSSO protect me? Trying to figure out how to replace plex for my extended family since theyre charging for external connections now

      • Appoxo@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 day ago

        Just be aware that putting Jellyfin behind a Reverse Proxy that redirects to external auth services, breaks client support that is not in a browser.
        Thus you either white-/blacklist specific server access paths or set up accounts that may relay the loging credentials.
        Maybe something like LDAP may work but I can’t say how well it works as I havent used that.

  • just_another_person@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    2 days ago

    Why? Fail2ban is best placed on the host closest to a network entrypoint. Unless you’re intentionally avoiding a bridged network, this isn’t going to do much for your security unless the containers are directly addressed by an attached interface and an open service.

    I won’t go into a whole diatribe, but you should be running containers as single-process instances of applications. You only cause issues by cramming other process to run inside a container.

    What are you using it to block, exactly?

    • basic_user@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 days ago

      Oh I can see how my title could be misunderstood - what I meant is that both jellyfin and fail2ban are running in (separate) docker containers. Not both services crammed.into one.

  • 3aqn5k6ryk@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 days ago

    Are you using nginx proxy manager as reverse proxy? SWAG has one built in. I’d use that instead.