Well I already have jellyfin running in a container, just have to figure out how to get mum’s TV to work with it I guess
<edit> log in on a local IP and not the network name and it’s working again. but I’ll be moving to jellyfin from now
Well I already have jellyfin running in a container, just have to figure out how to get mum’s TV to work with it I guess
<edit> log in on a local IP and not the network name and it’s working again. but I’ll be moving to jellyfin from now
I know it’s fashionable to shit on Plex here, but OP either has his server misconfigured or is just trying to stir the pot:
https://support.plex.tv/articles/202526943-plex-free-vs-paid/
Right, the $2 is to use the relay service, which costs Plex bandwidth. They can’t just do it free for everyone forever, bandwidth costs money.
They charge for remote access whether it’s through their relay service or not, and you can’t opt out of fallback to their relay service.
If you connect with the IP address it doesn’t charge you. You can use ZeroTier to connect from anywhere.
That’s not quite the same - that gives you the appearance of being a local device, which is enough to fool the restriction.
Their policy and technology enforcement is to charge for remote access, not relaying.
Can you give me an example of remote direct access that would be blocked? You can use nginx to forward your public IP to your Plex and it’s fine, you can forward ports directly on your router and connect to your public IP, you can use a VPN to connect from a different network; what are they limiting? It’s the same hurdle you have to overcome with Jellyfin. Relays are convenient, but they also cost money.
Yes, however using the relay is not a prerequisite to being required to pay for a Plex subscription. That is what he is trying to say.
I can run Plex on the open internet and not use their relay at all, however if the IP of the viewer is not an interal IP on the same subnet as Plex (I assume the same subnet is required) then you’ll be greeted with the Plex paywall.
You are absolutely correct that it costs money to run a relay, but the relay has nothing to directly do with the paywall.
That isn’t how it used to work.
Why would they care what subnet the request is coming from? That’s wack.
Correct. Remote streaming used to be free. That changed…in April? I don’t remember the exact date but it was announced earlier this year and has been slowly rolling out. Now you either have to have a Plex pass for your server or each user who wants to remote stream has to pay for a remote watching subscription and show in OPs screenshot.
There are of course ways to get around this such as all your users being on a VPN so as far as Plex can see its “internal”. I suppose if you use a reverse proxy but didn’t pass X-forwarded-for headers then that may get around it as well? I never messed with it as I was looking for an excuse to dump Plex anyway. Now I’m finally jellyfin only.
Thank you! That is exactly my point.
But there are dozens of people in this very thread who if I am understanding correctly are willing to offer the same service for free to prove their point that Plex is evil.
People are free to take some rando on the Internet up on their offer.
except not via mobile devices. you have to pay for the app to work.
It means the same specific subnet. If you have multiple subnets (one for wired, one for wireless for example) it will also trigger that limitation unless you go in and manually tell it hey these are local.
I have always connected via a FQDN, for some reason last night it decided to shit it’s self. Resolved by accessing via local IP, then the FQDN worked again
I’ll shit on Plex as much as anyone, but I wouldn’t rule out some kind of DNS nonsense here.
Yes, but they’re still sending emails to people even when it doesn’t apply. I had a Plex pass and still all of my users received emails and freaked out. They’re trying to trick people into thinking they need to pay, that’s the asshole move here.
Think they worked out that using the IP instead of the hostname solved it.
I have always connected via a FQDN, for some reason last night it decided to shit it’s self. Resolved by accessing via local IP, then the FQDN worked again