Starting with the Roku app, you need to pay up to watch media from remote servers.

Plex has confirmed that it will require a Remote Watch Pass or Plex Pass for remote streaming on its TV apps. The change is going into effect for the Roku app first, followed by all other TV apps and third-party clients in 2026.

Earlier this year, Plex increased its pricing for Plex Pass and stopped supporting all options for free remote streaming in the Plex apps, such as adding a custom server connection in the app settings. The company said at the time, “The reality is that we need more resources to continue putting forth the best personal media experience, and as a result, we will no longer offer remote playback as a free feature.” That’s also when Plex introduced the Remote Watch Pass as a less expensive way to enable remote streaming again.

Plex is now rolling out the remote watch changes to its Roku TV app. If you have Plex Pass, or the owner of the server you’re streaming from has Plex Pass, you don’t need to do anything. Otherwise, if you are streaming on a different network from the server’s home network, you need Plex Pass or Remote Watch Pass.

    • CmdrShepard49@sh.itjust.worksEnglish
      2·
      2 hours ago

      Note that opening a port gives full access to that port to the next higher Network. Opening a port directly to the Internet is therefore insecure and not recommended.

      It says so right there.

      There are multiple ways of exposing Jellyfin to the outside - the most common ones are:

      forwarding its Ports directly to the internet (not recommended!)

      forwarding through a Reverse Proxy

      using a VPN connection to enter the Network

      use a VPS to Reverse Proxy to your home network

      And there.

      This smug mentality that security is unnecessary when exposing ports to the open internet reminds me of people who think its fine to drive drunk because “I’ve done it dozens of times before and nothing happened!” It also reminds me of the mentality of tech company VPs right before they have a massive data breach. It’s quite absurd to read.

      • turdas@suppo.fiEnglish
        1·
        30 minutes ago

        For some reason they recommend against directly forwarding Jellyfin’s ports, but reverse proxies are fine. I expect this is because the default configuration doesn’t use SSL.

        This smug mentality that security is unnecessary when exposing ports to the open internet reminds me of people who think its fine to drive drunk because “I’ve done it dozens of times before and nothing happened!” It also reminds me of the mentality of tech company VPs right before they have a massive data breach. It’s quite absurd to read.

        I think you’ll find without exposing ports to the open internet we would not be having this conversation right now. Which, I suppose, wouldn’t be such a bad thing.

    • brewery@feddit.ukEnglish
      2·
      8 hours ago

      This is good to know, thanks for sharing. I’ve only got it local for now after installing at the weekend and wasn’t sure how secure it was for external access.

      • Pika@sh.itjust.worksEnglish
        4·
        6 hours ago

        I’m just chiming in to say that while the documentation gives you information on how to do external access, there are multiple issues open on the github about unauthenticated endpoints that if you know what is on the server already, you can confirm that it’s there

        So I wouldn’t use a standard naming convention because using that knowledge, someone who cares could use common names that could be on the server, followed by common standards of formats they would be in, and be able to confirm it’s their via the end points.