Plex is locking remote streaming behind a subscription in April
-
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.
Hellooooo jellyfin!
Only use open source software
-
How is it irrelevant? Plex offers a bunch of services that cost them money that we don't use, so they jacked up prices for streaming our own data.
It's irrelevant because even Plex themselves made no mention of their in-house streaming stuff. The discussion is about being charged to view your videos, hosted on your own self-hosted server, viewed on your own device.
-
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.
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 for jellyfin and other applications like sonarr, radarr, transmission, ombi and lists of others.
-
I don't really have a problem with this. I paid for a lifetime quite a long time ago. Right now I only use Plex for plexamp and everything else is on jellyfin.
Is finamp at a point that it can replace plexamp yet?
-
Or you just get a smaller version to begin with and save your hard drive space and your compute time.
You've kind of keyed in on one of the things I was hesitant to say:
There are two big uses for an "offline" media library.
Some people just use it for all the stuff they grabbed off the pirate bay (probably avoid TPB in 2025 but...). You don't really care about quality and just want to consume media.
Others, like myself, primarily use it to rip/back up their blu rays and UHDs and the like. If I am watching on my TV in the living room? I want that to be the highest quality I have available and I want to revel in every shadow gradient and so forth. If I am watching it on my computer? I don't need anywhere near that much detail. And on a tablet? Compress that shit like an exec at netflix just saw the storage arrays.
That is the benefit of transcoding and offline caching. It means you, as a "server", just focus on backing up your library/finding the best quality rips or whatever. And you, as a "user", don't have to worry about figuring out how many different versions to keep so that you always have an appropriate version for whatever your use case is that week.
-
It's irrelevant because even Plex themselves made no mention of their in-house streaming stuff. The discussion is about being charged to view your videos, hosted on your own self-hosted server, viewed on your own device.
I disagree. Sometimes you need to look at the situation as a whole in order to understand the motivation.
-
If I reverse proxy does the video stream itself travel via the proxy too?
In case this helps as a reference point, I use a $5 digital ocean droplet as my Plex and Jellyfin reverse proxy and it seems to handle the traffic of 3-5 simultaneous streams just fine. I use Haproxy in tcp mode (so no http interpreting, just passing packets) in an attempt to keep the CPU load minimal and just make it a pure I/O task.
-
The reality is that we need more resources to continue putting forth the best personal media experience
How stupid do they think we are?
Wait, why do you say this? I’m no Plex shill, this is disappointing news to hear and is the strongest push toward Jellyfin I’ve had yet. But they’re certainly a business with employees they need to pay, and their app has an objectively large feature set that needs to be maintained. Their employees deserve raises and benefits, and if costs are rising at the grocery store, they’re probably rising for businesses too. Why are we stupid to believe their financial burden is growing?
-
In case this helps as a reference point, I use a $5 digital ocean droplet as my Plex and Jellyfin reverse proxy and it seems to handle the traffic of 3-5 simultaneous streams just fine. I use Haproxy in tcp mode (so no http interpreting, just passing packets) in an attempt to keep the CPU load minimal and just make it a pure I/O task.
i'm fairly familiar with reverse proxies and how to set them up, but I'm mostly worried about the monthly bandwidth limits here. especially with hetzner's recently lowered limits. since I have a life time plex pass i might be able to hold off from switching until I figure something else out, at least.
-
Why would you expect this to NOT be paid? It requires them to be running servers to stream the media through, I wouldn't expect this to be a free feature.
I dislike Plex for several reasons, but asking for payment for stuff that costs them money is completely justified.
Wait a moment. I always thought that Plex’s servers only facilitate authentication (to verify your account) and discovery (to help your device find your server). They do not handle the actual media data. And if there is no Direct Remote Access, Relay usage is capped at 1 minute per day for free users. This looks like a cash grab to me.
-
Because of the Wife Factor. Getting people to convert requires getting past a lot of social inertia. It requires you to first convince them that the convenience of streaming services isn’t actually worth paying for. Then it requires an elegant onboarding experience. Lastly, Plex simply makes remote access easy. Sure, you could fiddle with reverse proxies for Jellyfin. But that’s easy to mess up. Instead, it’s much smoother to simply sign into Plex.
I can talk my tech-illiterate “My google chrome desktop icon got moved, and now I don’t know how to check my email” mother-in-law through Plex’s sign-up process over the phone. In fact, I did. It’s familiar enough that anyone who has signed up for a streaming service can figure it out. I can’t do that with Jellyfin, because their eyes glaze over as soon as you start talking about custom server URLs or IP addresses. Hell, my MIL’s TV doesn’t even have a native Jellyfin app available on the App Store. If I wanted to install it for her, I would need to sideload it.
Jellyfin does a lot of things right. But by design, the setup process will never be as elegant as Plex’s, because that elegant system requires a centralized server to actually handle it. And centralized servers are exactly what Jellyfin was built to rebel against.
To be clear, I run both concurrently; Jellyfin for myself, and Plex for friends/family. I got the lifetime Plex Pass license a decade ago, and it has more than paid for itself since then. But it sounds like a bunch of my friends and family may end up switching to Jellyfin if they don’t want to deal with the PlexPass subscription.
100% agree with the reverse proxy set up, it's not hard but it is intimidating at first and just fyi, reverse proxy set up is a ton easier if you're using swag with the drag, drop, run for of apps including SSL certificate renewal.
-
That works but is pretty insecure as you have nothing protecting your server outside of a basic password.
I'm pleading full ignorance here. Because I opened the port for JF, doesn't that mean the only thing exposed would be my jellyfin? I thought having the rest of my ports closed would not allow access to the rest of my system?
-
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.
My home connection is behind cgnat so I got a free VPS from oracle, 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.
-
So far I've had no problems using jellyfin on basicly anything that exists in my house which includes a Apple TV, Xbox SX and a Xiaomi TV Box S.
But I can see there's probably no Tizen app for things like Samsung TV's.
https://github.com/Georift/install-jellyfin-tizen
Samsung is being a bit of a dick apparently.
-
i'm fairly familiar with reverse proxies and how to set them up, but I'm mostly worried about the monthly bandwidth limits here. especially with hetzner's recently lowered limits. since I have a life time plex pass i might be able to hold off from switching until I figure something else out, at least.
Gotcha, I've never actually considered the bandwidth limits. It looks like digitalocean includes 1TB per month and I used 242GB last month. If I ever get close to the limit I will just spin up another droplet. I don't think I would even need to load balance unless the first one is struggling since the bandwidth allowance across all droplets is pooled together.
If you aren't already using a reverse proxy, then do you currently just port forward or use the Plex relay? The only reason I use one is because of CGNAT. Before I moved to a place with only CGNAT I port forwarded for both Plex and Jellyfin.
-
That exposes Jellyfin to the internet, so it's my option 1.
-
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 for jellyfin and other applications like sonarr, radarr, transmission, ombi and lists of others.
That exposes Jellyfin to the internet, so it's not the same feature
-
My home connection is behind cgnat so I got a free VPS from oracle, 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.
That exposes Jellyfin to the internet
-
Alright, so I have had Jellyfin installed for years now, but my primary issue is that most devices myself or my users use lack official, readily-available clients. For example, the Samsung TV app is a developer mode install. Last I looked, nobody has put a build into the store.
I really want to use Jellyfin, but I feel like my users simply can't. I'm interested in others' experiences here that could help.
I run an Android TV box on my Smart TV, because I don't trust them on the internet.
-
Gotcha, I've never actually considered the bandwidth limits. It looks like digitalocean includes 1TB per month and I used 242GB last month. If I ever get close to the limit I will just spin up another droplet. I don't think I would even need to load balance unless the first one is struggling since the bandwidth allowance across all droplets is pooled together.
If you aren't already using a reverse proxy, then do you currently just port forward or use the Plex relay? The only reason I use one is because of CGNAT. Before I moved to a place with only CGNAT I port forwarded for both Plex and Jellyfin.
I just port forward right now, so Plex’s system is basically an overpowered dynamic dns. I guess my next option is to self host a dynamic dns on a numbered xyz domain (yk the $1/yr ones)
