Comment on Plex has paywalled my server!

• mic_check_one_two@lemmy.dbzer0.com ⁨3⁩ ⁨days⁩ ago

  To set it up “correctly”, yes. It’ll require owning your own domain, being able to configure it properly, knowing how to automate https certificate refreshes, and a few other things. Plex just requires forwarding a port in your router.

  source

  • RaccoonBall@lemm.ee ⁨3⁩ ⁨days⁩ ago

    I thought self hosting was about learning networking basics like DNS and setting up let’s encrypt.

    So much whining in here about the most simple stuff being too complex.

    source

    • mic_check_one_two@lemmy.dbzer0.com ⁨3⁩ ⁨days⁩ ago

      I disagree; Self-hosting is for a variety of things, and plenty of people (in fact, I’d say probably the majority of Plex users) just want to be able to pirate Netflix without a ton of setup.

      Is learning some networking inevitable? Yeah, probably. But I also think this xkcd is apt. The reality is that what may be simple for you and me actually requires a lot of studying for a complete novice. Plenty of people will need to google what a port is, let alone how to forward one. And that’s assuming they even know the word “port” to google. Plenty of people won’t even know where to start.

      And true novices are hopefully going to be extremely wary of any info they find online; It’s easy to fuck something up without even realizing it, and leave your entire system exposed. Especially when the braindead “lol just forward your Jellyfin port and use your public IP” advice is posted somewhere in every single advice thread.

      source
  • druidjaidan@lemmy.world ⁨3⁩ ⁨days⁩ ago

    Worse. Exposing Jellyfin to the internet is a bad idea given the teams stance on security. github.com/jellyfin/jellyfin/issues/5415#issue-82…

    The only safe way to host jellyfin is with a vpn.

    source

    • mic_check_one_two@lemmy.dbzer0.com ⁨3⁩ ⁨days⁩ ago

      Lots of those issues have been blown out of proportion, and would never be a real concern for the “just a dude running a server in his closet for his friends” setups. Which, to be clear, is the vast majority of setups.

      For instance, virtually all of the worst issues require that the attacker already has a valid login token. So unless they stole your buddy’s credentials, the only one to truly worry about would be your buddy directly. But yes, Jellyfin has some gaping holes, and letting it touch the WAN at all is always a risk. You’re giving attackers a new potential vector of attack that didn’t exist before, so that’s worth noting.

      source

      • mobotsar@sh.itjust.works ⁨2⁩ ⁨days⁩ ago

        unless they stole your buddy’s credentials

        Thank God trolls never steal people’s credentials so they can hack a small server because they’re bored.

        source
  • AtariDump@lemmy.world ⁨3⁩ ⁨days⁩ ago

    Right.

    Even though I could do those things, I just want something that works.

    Plex (or even Emby) fits that request.

    Plus they both have an AppleTV app for fee that doesn’t suck.

    source