Well I already have jellyfin running in a container, just have to figure out how to get mum’s TV to work with it I guess

<edit> log in on a local IP and not the network name and it’s working again. but I’ll be moving to jellyfin from now

  • xcjs@programming.devEnglish
    2·
    17 hours ago

    That’s not quite the same - that gives you the appearance of being a local device, which is enough to fool the restriction.

    Their policy and technology enforcement is to charge for remote access, not relaying.

    • absentbird@lemmy.worldEnglish
      2·
      16 hours ago

      Can you give me an example of remote direct access that would be blocked? You can use nginx to forward your public IP to your Plex and it’s fine, you can forward ports directly on your router and connect to your public IP, you can use a VPN to connect from a different network; what are they limiting? It’s the same hurdle you have to overcome with Jellyfin. Relays are convenient, but they also cost money.

      • themachine@lemmy.worldEnglish
        3·
        15 hours ago

        Yes, however using the relay is not a prerequisite to being required to pay for a Plex subscription. That is what he is trying to say.

        I can run Plex on the open internet and not use their relay at all, however if the IP of the viewer is not an interal IP on the same subnet as Plex (I assume the same subnet is required) then you’ll be greeted with the Plex paywall.

        You are absolutely correct that it costs money to run a relay, but the relay has nothing to directly do with the paywall.