• Jul (they/she)@piefed.blahaj.zone
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 days ago

    I mean, most people dont really understand what a reverse proxy is doing, and with dynamic IP addresses and other complications that residential customers often can’t control, it can be a challenge to configure properly. Not to mention if you want to use Jellyfin on a device that travels between home and outside you need to either modify the domain or IP Address each time you enter or leave the home Otherwise you just end up routimg all the traffic over the internet and back losing the advantage of LAN speeds and sucking down your ISP traffic quotas. Or you need to configure something much more robust like a local DNS server to properly route traffic to the LAN IP address instead of your WAN IP address. That might not be an issue if you’re lucky enough to have an IPv6 block of addresses from your ISP and assign one to your server, but at least in the US most ISPs still use IPv4 with workarounds like 6rd for a single dynamic external IPv6 address with all of the same issues of the dynamic IPv4 addresses. Anyway, for most users hosting a Plex server is simple (unless they have double NAT kinds of issues) compared to setting up everything correctly to TailScale.

    • potustheplant@feddit.nl
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      2 days ago

      Uhm, no? I just use the lan IP for my jellyfin server at all times. The only difference between being phisically in the same place and outside is that I enable tailscale when I’m outside. I’m telling you, this is far simpler than you’re making it out to be.