Comment on What's the security situation when opening a jellyfin server up for casting?

• dogs0n@sh.itjust.works ⁨1⁩ ⁨week⁩ ago

  The default configuration for Jellyfin is good. I mostly mean as long as you follow best practices in general you should be fine (keep your system and jellyfin updated, have some type of firewall in place, make sure you aren’t accidentally exposing jellyfins port directly to the internet).

  jellyfin.org/docs/general/…/reverse-proxy/

  source

  • mic_check_one_two@lemmy.dbzer0.com ⁨1⁩ ⁨week⁩ ago

    Also, don’t use the default “data/media/{library name}” (or whatever the suggested format is) folder setup that the Trash Guide has you set up. At least change the “tv”, “movies”, etc name to something different. Jellyfin has a known vulnerability where an attacker can get access to media without valid credentials if they already know the file path. Jellyfin devs have stated that they have no intention of ever fixing this, because it would require completely divesting from the Kodi branch that everything is built on. And since everyone follows the Trash Guide to set their *Arr stack and library up, guessing file paths is laughably easy.

    You’re using the suggested file naming in your *Arr stack, so Jellyfin can automatically match media? Congrats, so is everyone else. You’re using the suggested folder layout so your *Arr stack can use hardlinks? Congrats, so is everyone else. At least change the library folder names. Since your library folder doesn’t need to match the name of your Jellyfin library, you can literally have your “tv”, “movies”, and other folders be named whatever you want. Hell, name your tv folder “peepee” and your movies folder “poopoo” for all I care.

    source

    • planish@sh.itjust.works ⁨1⁩ ⁨week⁩ ago

      That certainly sounds like a thing you would want, nay need, to fix.

      source

      • victorz@lemmy.world ⁨1⁩ ⁨week⁩ ago

        This sounds like a blocker for me to not switch to Jellyfin… What else is in there that’s equally severe?

        source
    • Wolf314159@startrek.website ⁨1⁩ ⁨week⁩ ago

      This needs to be copypasta’d as a reply to every comment suggesting that opening up jellyfin to the internet is easy and everyone should do it to get away from Plex.

      source
  • victorz@lemmy.world ⁨1⁩ ⁨week⁩ ago

    having your ssh port blocked in the firewall being second

    So like if I want to access my PC from outside, is it enough that I don’t have a firewall installed but that I open up some random port and redirect it to my PC’s port 22, and then connect to it via the random port?

    make sure you aren’t accidentally exposing jellyfins port directly to the internet

    Same thing for Jellyfin?

    source

    • dogs0n@sh.itjust.works ⁨1⁩ ⁨week⁩ ago

      If you don’t want to worry too much, you can setup a vpn (like wireguard) on your server for ssh access.

      Using a non standard port is a good idea, but not entirely foolproof because bots might still port scan (even if unlikely that they do that for ssh I’m not sure). At a mininum, you probably want to use keys for login like the other commenter on the main comment said.

      Personally, using a vpn for when I want access to SSH when I’m out is worth the couple hours setting it up the one time (very simple setup with wireguard-easy for example). Maintenence time spent on upgrading is very low.

      (Tl;dr I’d use a vpn to access ssh specifically rather than exposing it to the internet)

      Same thing for Jellyfin?

      Not 100% sure what you mean, but to clarify: Don’t accidentally expose jellyfins port to the internet (eg the default port 8096). Make sure it is only accessible from outside your network through your reverse proxy.

      source

      • victorz@lemmy.world ⁨1⁩ ⁨week⁩ ago

        Could you explain a bit more?

        Like, right now, I have two machines in my local network. Both are running sshd on port 22.

        In my router, I’ve set the port forwarding to be some high port number in the 19000’s to forward to port 22 on the first machine, and then the same high port number incremented by one (1) to forward to port 22 on the second machine.

        Also key based login only of course.

        Is this insecure in some way?

        Would a VPN make connecting to my computers more secure somehow? I’m not sure I understand how if so.

        ---

        What I meant with the Jellyfin question was kind of, how is having it exposed via a reverse proxy different from exposing its port right away? It’s it because the only allowed connection would be HTTPS/encrypted etc, maybe?

        I’ve never set up a home network apart from physical cables and using routers and switches before, no advanced site/network configuring. Definitely interested to learn more though for when I want to serve a real media center using a NAS and like a Pi.

        source

        • -> View More Comments