We are also changing how remote playback works for streaming personal media (that is, playback when not on the same local network as the server). 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. This—alongside the new Plex Pass pricing—will help provide those resources. This change will apply to the future release of our new Plex experience for mobile and other platforms.

    • Nibodhika@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      13 hours ago

      How do you do this on Jellyfin? The only ways I’m familiar with is to expose Jellyfin to the internet or access it through Tailscale, would love to hear alternatives.

      Edit: From the replies I think that either I don’t understand how this feature works or many people here don’t, so I’ll give an overview of my understanding and explain why this is different from anything you can do on Jellyfin and what’s the closest you can come.

      You are running Plex-home in your house, Plex-home connects to Plex-server hosted by Plex and establishes a reverse connection that’s only accessible by Plex-server, i.e. you can’t access your Plex-home outside of your house. When you login on Plex you’re logging in to Plex-server and if you’re in the same network as Plex-home you get redirected to form a direct connection with it, if not (and for me Plex keeps failing this verification) you connect to Plex-server and every request you make gets forwarded to Plex-home and when you ask for media it gets routed through Plex-server. This is very different from exposing Plex-home directly to the internet, in order for someone online to access your Plex-home they need to have taken control of Plex-server and then they’re limited by the API between those two (whichight be different from the Plex-home API) to try to escalate into your machine.

      With Jellyfin there’s no server side component, you access Jellyfin directly every time, so in order to access Jellyfin outside of your house it needs to be accessible for everyone. The closest you can come up with is using a third party authentication server, for example by having a VPS running Authentik/Authelia/etc and hosting Jellyfin behind that authentication. This gets you a similar level of security because someone would need to compromise your Auth and then your Jellyfin to get into your server. However I’m not sure Jellyfin clients would know how to handle a third party authentication service, and would probably just crap their pants and prevent you from logging in. You could still access it in a browser, but not on native clients like the one on your TV or Fire Stick.

      If you don’t have this VPS with authentication you’re exposing Jellyfin directly to the internet, which means that any flaw in Jellyfin security immediately compromises your home server. And while I don’t expect there to be many big or obvious flaws, there’s a reason why stuff like Authelia or Authentik exists, and besides the convenience of a SSO they exist because proper authentication is hard and has many pitfalls, and they offer security in the knowledge that their main focus is authentication, whereas on most other services authentication is just one of the features they offer so it might not be as secure.

      • couch1potato@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        7
        ·
        edit-2
        1 day ago

        My home connection is behind cgnat so I got a free VPS from oracle (provides a public ip address), install caddy on VPS, install tailscale on VPS and router, expose routes from LAN to tailscale network.

        Now you can use caddy to expose, for example, a docker container (jellyfin) at 192.168.1.100 to subdomain.exampledomain.com with ssl cert provided by caddy.

        VPS also requires some other stuff like ddclient and fail2ban.

        I pieced this all together myself… it’s doable if you spend some time reading.

      • inclementimmigrant@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        1 day ago

        It’s not that hard to get a reverse proxy up, get a free DDNS, and a SSL certificate from let’s encrypt.

        https://www.linuxserver.io/blog/2020-08-21-introducing-swag

        This is a pretty solid one stop shop for handling all reverse proxy with SSL certificate generation and renewal for jellyfin and other applications like sonarr, radarr, transmission, ombi and lists of others that are pretty much drag and drop configuration files if you’re not mucking with the application’s default ports.

          • inclementimmigrant@lemmy.world
            link
            fedilink
            English
            arrow-up
            11
            ·
            1 day ago

            And somehow you think that Plex isn’t exposing your server to the Internet for streaming while not on your local network?

            Okay there Mr. Madison.

            • Nibodhika@lemmy.world
              link
              fedilink
              English
              arrow-up
              2
              ·
              13 hours ago

              It’s not, not directly at least, and that’s what everyone is ignoring here. You probably understand the value on Authelia/Authentik but you’re failing to see that the Plex relay server is taking that same mantle here, so even if someone managed to compromise the relay server it’s still not on your home server, whereas exposing jellyfin directly to the internet only requires one service to be compromised.

          • LeninOnAPrayer@lemm.ee
            link
            fedilink
            English
            arrow-up
            10
            ·
            1 day ago

            My dude if you are connecting from outside your local network you are “exposed” to the Internet in some way. What magic are you thinking Plex is doing? Is someone hand deliverying the packets via USPS?

            • Nibodhika@lemmy.world
              link
              fedilink
              English
              arrow-up
              2
              ·
              13 hours ago

              In some way is different from directly, on Plex you’re behind a relay server so it’s akin to being behind a VPS running Authentik/Authelia in front of the service on your home. Compromising the relay server does not necessarily compromises your home server, so it’s not direct like putting Jellyfin on a reverse Proxy would be.

            • myliltoehurts@lemm.ee
              link
              fedilink
              English
              arrow-up
              3
              ·
              20 hours ago

              Plex runs relay servers where your Plex server will connect to the relay and your player will also connect to the relay, making both ends of the connection egress type as far as routing and access control goes. https://support.plex.tv/articles/216766168-accessing-a-server-through-relay/

              It’s optional and likely not everyone uses it, but this provides a way for Plex to do remote streaming without the Plex server being reachable directly from the internet.

              Separately, it costs money for Plex to run.