cross-posted from: https://poptalk.scrubbles.tech/post/2333639
I was just forwarded this someone in my household who watches our server. That's it folks. I've been a hold out for a long time, but this is honestly it.
They want me to pay to stream content that I bought from my hardware transcoded also on my hardware.
I'll say it. As of today, I say Plex is dead. Luckily I've been setting up Jellyfin, I guess it's time to make it production ready.
Edit: I have a Plex Pass. More comments saying “Just buy a plex pass” are seriously not getting it. I have a Plex Pass and my users are still getting this.
And for the thousandth person who wants to say the same things to me:
- YES I know I'm unaffected as a Plex Pass owner.
- My users were immediately angry at it, which made me angry. Our users don't understand what plex pass is, and they shouldn't have to, that's why I had it. The fact that they were pinged even though it should have kept working is horribly sloppy
- Plex is still removing functionality. I don't care that "People should pay their fair share". If Plex wants to put every new feature behind a paywall, that's completely okay. They are removing functionality.
- "But they have cloud costs". Remote streaming is negligible to them. It's a dynamic DNS service. Plex client logs in, asks where server is, plex cloud responds with the IP and port of where server is located. That's it.
- "Good luck finding another remote streaming" - Again, Plex just opens up an IP and port. Jellyfin also just opens up an IP and port (Hold on jellyfin folks I know, security, that's a separate conversation). All "remote streaming" is is their dynamic dns. Literal pennies to them. Know what actually is costing them money? Hosting all of that ad-supported "free" content that they're probably losing money on.
In short, I don't care how you justify it. Plex is doing something shitty. They're removing functionality that has been free for years. I'm not responding to any more of your comments repeating the same arguments over and over.
It depends on how you're hosting Jellyfin. The easiest and most common way is via Docker in some form. You can also install a docker image of Cloudflare tunnel making sure it's on the same virtual network as Jellyfin (I think it will by default). However you're running Jellyfin, Cloudflare tunnel will need to be able to reach your local Jellyfin install.
Create a tunnel in the Cloudflare zero trust dashboard, create or edit the config file for your Cloudflare tunnel install using the code string from the zero trust dashboard, your tunnel will attempt to connect to the Cloudflare servers, when it does, you have a secure tunnel. Then you can add hostnames on the zero trust dashboard, using your local IP addresses and ports. For example, jellyfin.yourdomain.com points to 192.168.1.10:8096. The tunnel connects your local IP to the routing from your domain.
Be careful to not open this up to apps that don't have security in some form at least. There are ways to improve security on your tunnel end with SWAG and such. And I recommend turning on the security tools in Cloudflare so your domain can't be accessed outside of your country at the least, and maybe even whitelisting IP addresses for even more security.
SpaceInvaderOne on YouTube has a good video on creating a Cloudflare tunnel via Unraid. But everything is much the same in regular docker. I'm sure there's good videos on doing it however you're hosting Jellyfin. Feel free to reach out with questions, I'll gladly help if I can.
thanks for this
Amazing thank you, when I get time to sit down with this I will probably have more questions!