- cross-posted to:
- piracy@lemmy.dbzer0.com
- cross-posted to:
- piracy@lemmy.dbzer0.com
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.
You must log in or register to comment.
Hellooooo jellyfin!
Only use open source software
I’m surprised by the resistance to Jellyfin in this thread. If you are using Plex, you’re already savvy enough to use bittorrent and probably the *arrs. If you can configure that stuff, Jellyfin is absolutely something you can handle. If you like Docker, there’s good projects out there. If you’re like me and you don’t understand Docker, use Swizzin community edition. If you can install Ubuntu or Debian, and run the Swizzin script, you’re in business.
I think I represent a huge portion of Plex users; I am tech savvy enough to follow a simple walkthrough on YouTube to get my server setup. But the arrs, jellyfin, and docker both look like graduate level chemistry to me.
Plex has been around for ages and they have put money into making things easier for users like me to understand with events such as Pro Week and directly paying content creators to dumb things down for me.
I’ve got to admit that I’ve never used Plex (I’m a cantankerous open software fanatic), but how do you get your media on there? You’re hosting your own server so presumably you’re downloading the media somehow. Are you doing it manually? If so, you can do the same with Jellyfin. Is it automated with some tool built into Plex?
I’m ripping it with makemkv, actually. I have a fairly large blu ray collection that is slowly going onto my DAS.
Me too. Docker isn’t hard if you use a compose file. It’s easy to read syntax.
Linux server.io has great documentation for their images.
I have Jellyfin and Plex running from the same virtual machine pointing at the same media. If it wasn’t for the one crappy TV I have in my house with no Jellyfin client, Plex would be gone.
Docker isn’t hard if you use a compose file. It’s easy to read syntax.
This is giving me “yaml isn’t hard to use if you use a compose file!” It is, actually. It’s easy for you because you understand the technology. The vast majority of people do not.
Wireguard so you are always seen as being on the local network. This bit of assholery is easily defeated.
I used to use Plex, then one day my internet was down and since Plex couldn’t phone home, it wouldn’t let me log in to watch media ON MY LAN.
So yeah it’s inherently broken. That’s before you even consider the licensing.
Bro what
I moved on to jellyfin after I found out the hard way Plex servers need to authenticate for use. I’m sure by now there are ways to set up offline authentication but I already didn’t like the idea of paying monthly to stream my own content from my own machine. It just didn’t make sence to me. Jellyfin isn’t perfect, or as flashy as Plex, but it works, looks fine, and its free, not counting a much deserved donation to the devs .
Plex Media Server- Settings : Network : List of IP Addresses and Networks that are allowed with Auth : 192.168.4.0/24, e.g.
As someone looking to get into self hosting and was researching plex. What’s been the experience like using jellyfish with non techy people? This is mainly something I want to set up for my parents
Jellyfin needs to partner with someone people can pay a very low and reasonable and/or one-time fee to enable remote streaming without the fuss of setting up either dangerous port-forwarding or the complexity of reverse proxies (paying for a domain-name, the set-up itself including certificates, keeping it updated for security purposes).
And no a VPN is not a solution, the difficulty for non-technical users in setting up a VPN (if it’s even possible, on smart-tvs it’s almost always not, and I don’t think devices like AppleTV and other streaming boxes often support them) is too high and it’s an unwanted annoyance even for technical users.
I’m not talking about streaming video’s through someone else’s servers or using their bandwidth. I’m talking about the connection phase of clients and servers where Plex acts like an enhanced dynamic DNS service with authentication. They have an agent on the local media server which sends to the remote web service of the third party the IP address, the port configured for use, the account or server name, etc. When a client tries to connect they go to this remote web service with the servername/username info, the web service authenticates them then gives them the current IP address and any other information necessary. It then sends some data to the local Jellyfin server about the connecting client to enable that connection and then the local media Jellyfin server and the client talk directly and stream directly.
Importantly the cost of running this authentication and IP address tracking scheme would be minimal per Jellyfin server. You could charge $5/year for up to 20 unique remote clients and come out ahead with a slight profit which could be put back into Jellyfin development and things like their own hosting costs for code, etc. Even better if they offer lifetime for this at $60-$80 they’d get a decent chunk of cash up-front to use for development (with reasonable use restrictions per account so someone hosting stuff in Hetzner or whatever and serving 300 people with 400 devices will need to pay more because they’re clearly doing this for profit and can afford to throw some more money at Jellyfin).
Until Jellyfin offers something that JUST WORKS like that it’s not going to be a replacement for Plex, whatever other improvements they offer to users it’s still a burden for the server runner to set up remote streaming in a way that isn’t either incredibly dangerous (port forwarding) OR either involves paying money to third parties AND/OR the trouble of running your own reverse proxy and/or involves walking users through complicated set-up process for each device that you have to repeat if you change anything major like your domain name when using a VPN.
Authelia maybe?
Interesting project. Thanks for the link and I do appreciate it and could see some very good uses for that but it’s not quite what I meant.
Unfortunately as it notes it works as a companion for reverse proxies so it doesn’t solve the big hurdle there which is handling secure and working flow (specifically ingress) of Jellyfin traffic into a network as a turn-key solution. All this does is change the authorization mechanism but my users don’t have an issue with writing down passwords and emails. Still leaves the burden of:
- choosing and setting up the reverse proxy,
- certificates for that,
- paying for a domain so I can properly use certificates for encryption,
- making sure that works,
- chore of updating the reverse proxy, refreshing certs (and it breaking if we forget or the process fails), etc
Which is a hassle and a half for technically proficient users and the point that most other people would give up.
By contrast with Plex how many steps are there?
- Install (going to skip media library setup as Jellyfin requires that too so it’s assumed)
- Set up any port settings, open any relevant ports on firewall, enable remote access in setting with a tickbox
- Set up users
- Done, it now works and doesn’t need to be touched. It will handle connecting clients directly to the server. Users just need to install Plex client, login to their account and they have access.
By contrast this still requires the hoster set up a reverse proxy (major hassle if done securely with certificates as well as an expense for a domain which works out to probably $5 a year), to then have their users point their jellyfin at a domain-name (possibly a hard to remember one as majesticstuffbox[.]xyz is a lot cheaper than the dot com/org/net equivalents or a shorter domain that’s more to the point), auth and so on. It’s many, many, many more steps and software and configurations and chances for the hosting party to mess something up.
My point was I and many others would rather take the $5 we’d spend a year on a domain name and pay it for this kind of turn-key solution for ourselves and our users even if provided by a third party but that were Jellyfin to integrate this as an option it could provide some revenue for them and get the kinds of people who don’t want to mess with reverse proxies and certificates into their ecosystem and off Plex.
I’m seeing a lot of negativity but I think they offer a great service and deserve to be paid for their work. I bought a lifetime pass many years ago and I almost feel guilty how much value I have received over that time.
You need an internet connection to connect to a offline LAN Plex server… Just so unessessery, otherwise it doesn’t find your server (I was quite confused on that one, when that started happening) Plus having to pay for multiple user accounts, all just seemed like it was heading towards user extortion. It also lacked hardware transcoding at that point in time, which isn’t a huge issue, but did make it harder to run if you had a client that didn’t support a specific codec.
While jellyfin requires zero internet to be functional and login, supported hardware transcoding before plex and has multiple user accounts usage out of the box, at zero cost.
One does not need an internet connection for offline use. Check this if you’re having issues.
One does not need to pay for multiple user accounts. As per this update, they are actually removing the one-time fee for non family member mobile apps. Now it’s all free, provided the server owner has a Plex Pass.
Plex has been supporting hardware transcoding since 2017.
To be clear, I’m not saying Jellyfin is bad. I think it’s great to have competition and I understand plenty of people like it.
ur getting what u paid for, why the guilt
I feel like I’m getting more than what I paid for. I understand it was a legal contractual exchange. I’m merely commenting on the value I’ve received relative to what I paid. Especially given the continued improvements over time.
Can’t say I have a huge issue with this - Plex isn’t FOSS and the infrastructure to make this happen isn’t free. Other options are available if you don’t want to pay the fee.
But what infrastructure does this feature require? I’m direct connecting to my own personal server with perhaps credential handling and a handshake handled by Plex servers to connect. None of the media is passing through their servers - or it shouldn’t be if it is.
In a nutshell, if your app isn’t able to make a direct connection to your Plex Media Server when you’re away from home, we can act as sort of a middle man and “relay” the stream from your server to your app. To accomplish this, your Plex Media Server establishes a secure connection to one of our Relay servers. Your app then also connects securely to the same Relay server and accesses the stream from your Plex Media Server. (In technical terms, the content is tunneled through.)
So, your Plex Media Server basically “relays” the media stream through our server so that your app can access it since the app can’t connect with your server directly.
Source: https://support.plex.tv/articles/216766168-accessing-a-server-through-relay/
It’s not a requirement to stream and it’s sort of dumb they are lumping this relay service as a part of the remote streaming. Remote streaming should be allowed for free - if you are not a subscriber. The relay should just be a paid service, which makes sense. But if it’s a direct connection to my server, it should be free.
That being said, I understand how Plex may have built some technical debt into this relay system. It might be hard for them to decouple the relay from the remote streaming. What they should have done is:
We are removing the relay service as a free service, but you can still do remote streaming with a direct connection.
And they should have built their architecture in a way that’s easy to decouple the two services.
Thanks for that - I wasn’t aware of the relay service, but completely agree that this is what they should be charging for and not the remote play feature in its entirety. I’ll probably drag it out for a while by refusing to update the app and server… Might be able to make it work with Tailscale as others have suggested.
In the past I’ve paid for a month or two when I wanted to download to my devices remotely (and I think that’s the singular feature that I’ve ever cared about in the Plex pass). But to take features away and then try and charge me for them is a bridge too far, I can’t support that bad behavior.
I paid for the lifetime membership ~6 years ago so I’m going to stick with it. Plus I just use it for my own home. It’s not like I’m serving a bunch of other clients. But I’ll switch to Jellyfin if the lifetime membership ever gets taken away.
