Plex has paywalled my server!
-
I have had great success with tailscale in this regard.
The same tailscale that announced last week that they are going to start charging?
-
In this thread:
- An OP that doesn’t understand how their network is working
- People rushing to suggest a solution that they fawn over because it’s open source. I have yet to see anyone recommend Emby.
- “Tailscale will solve all your problems!” Great - how do I make that work on an LG TV that’s 100 miles away?
wrote last edited by [email protected]- Open source has high immunity to devs making changes at the expense of the user for their benefit because anti-features can be removed. Recommending another proprietary alternative here would be like saying they aught to leave an abusive partner but then recommend someone with the same red flags.
-
I started down the Jellyfin path after they made that announcement. It's super easy to install, and in many ways the UI is nicer than Plex. But I ran into challenges getting my server safely accessible for users outside my LAN. And I haven't had the time to look into that further.
Would be great if there was a clean, easy way to set up the webserver portion so it's as easy to share content entirely as Plex. But I get they are a volunteer project with a lot on their plate.
But I ran into challenges getting my server safely accessible for users outside my LAN
FWIW:
- vps + domain (optional?)
- connect vps to home server with wireguard (eg Tailscale)
- reverse proxy on the VPS forwarding to jellyfin (eg Caddy)
Obviously not as trivial or seamless as Plex. Also I wouldn't try to complicate this setup by using docker for everything. But once its up you can basically host whatever you want on the WAN from your LAN.
-
What we should be asking is why “selling a product” is no longer a business model.
Because they're not selling a product, they're selling an ongoing service. They run the relay servers, and those cost money every month.
I bought a media management and consumption platform running on my own server using my own clients. For what reason do I need a relay service to watch content in my house on my server?
-
In this thread:
- An OP that doesn’t understand how their network is working
- People rushing to suggest a solution that they fawn over because it’s open source. I have yet to see anyone recommend Emby.
- “Tailscale will solve all your problems!” Great - how do I make that work on an LG TV that’s 100 miles away?
If #3 is your use case, then yeah, pony up the fees. Or learn to code I guess.
-
In other words, it's a dark pattern that tricks users into letting Plex MITM their connection.
It gets around port forwarding/firewall issues that most people don't know how to deal with. But putting it behind a paywall kinda kills any chance of it being a benevolent feature.
-
What we should be asking is why “selling a product” is no longer a business model.
Such a good question. Off the top of my head, I can think of two reasons: one cynical, one a little more practical.
Cynical first lol: Maxmize profits. Why charge once when you can charge monthly. I'll move off this bc it's a topic that's been beaten to death, esp. here on Lemmy.
The more practical reason is probably because most software interacts pretty directly with the internet in some way. When we were just installing MSOffice98 with clippy, software didn't need constant security updates, patches, etc. Remember when there was an update for MSOffice and you'd install Service Pack 1? That was one of the first patches I downloaded from the internet and it was a big deal back then. Now updates come out at least monthly, many times more often than that. I guess that means that you have multple product cycles occuring concurrently, which creates a financial model with a lot more unknowns... which in turn makes it harder to forecast what a product should cost, considering it would be the only revenue generated, per license for the life of the product.
I think selling a product is still a very viable business model, but you have to be a lot more accurate about revenue forcasting and product pricing. I guess it means you have a lot less room for error (from a business perspective).
This is not Microsoft. I haven’t updated my plex software in over six months and it runs fine.
Still, yes, I would expect updates to any software I purchase as new patches are needed for OS updates, etc. That shouldn’t be more than two updates a year for a given OS - if at all.Selling a product, generating revenue, using revenue to improve products or create new products is how we used to run businesses.
If they’re unable to maintain software updates with the revenue they get, then they should discontinue support of less popular products.
As I’ve stated on the plex forum, plex is no longer a media management and consumption platform. It’s a video on demand service. That’s their prerogative and that’s fine. The issue is that they’re discontinuing a product that people have purchased and use on a regular basis. I paid money for a product and that product can no longer be used if I change the device I use that product on. They should have left the existing product alone and released something wholly new.
-
The OP might disagree from what I'm seeing.
OP is also in the allegedly ultra rare camp of “successfully configured Jellyfin and lived to tell the tale.” Not what I’d expect of someone unable to configure Plex correctly. I’ve not set up a Plex server myself but my guess is it wasn’t clear that it was misconfigured - it did work previously, after all.
-
Considering both Plex and Tailscale are going toward VC exits, Headscale and Jellyfin is the only FOSS way atm.
I just use nginx on a tiny Hetzner vps acting as a reverse proxy for my home server. I dunno what the point of Tailscale is here, maybe better latency and fewer network hops in some cases if a p2p connection is possible? But I've never had any bandwidth or latency issues doing this
-
But I ran into challenges getting my server safely accessible for users outside my LAN
FWIW:
- vps + domain (optional?)
- connect vps to home server with wireguard (eg Tailscale)
- reverse proxy on the VPS forwarding to jellyfin (eg Caddy)
Obviously not as trivial or seamless as Plex. Also I wouldn't try to complicate this setup by using docker for everything. But once its up you can basically host whatever you want on the WAN from your LAN.
Awesome, thanks for the tips!
-
Why anyone still uses Plex for new setups is beyond me.
pretty much the only reason I still use Plex is because I like to be able to watch stuff during downtime at work and plex.tv isn't blocked on the work network while my private domain is.
And no, using a hotspot off my phone on a personal computer isn't an option, both because the security requirements of my job site prevent us from using personal devices in the main area where I work and because the building itself is a massive concrete structure that blocks most cell signals.
-
It gets around port forwarding/firewall issues that most people don't know how to deal with. But putting it behind a paywall kinda kills any chance of it being a benevolent feature.
Labeling it as "SECURE" (implying the other option is insecure) is enough to make it seem underhanded to me.
-
I bought a media management and consumption platform running on my own server using my own clients. For what reason do I need a relay service to watch content in my house on my server?
No idea, you're the one that bought it. I did the same thing for a few years and never bought a plex pass.
-
The same tailscale that announced last week that they are going to start charging?
Says personal is still free? Not seeing what you’re saying
-
The same tailscale that announced last week that they are going to start charging?
wrote last edited by [email protected]Took a quick look at the free tier,
- 3 users
- 100 devices
- Basically all tailscale features
That seems pretty reasonable to me. Main account and two accounts to share. With just friends and family, I doubt most people will reach the 100 device limit.
-
- Open source has high immunity to devs making changes at the expense of the user for their benefit because anti-features can be removed. Recommending another proprietary alternative here would be like saying they aught to leave an abusive partner but then recommend someone with the same red flags.
- It’s also the most complex to set up, and for many people the threshold is “walking your tech-illiterate mother-in-law through side loading it over the phone, because she lives 100 miles away… She’s afraid to touch her computer for anything except email and Facebook. And then resetting her password every 30 days, because she keeps locking herself out of it.” Suddenly the “just fucking sign into Plex and it automatically discovers your server” option becomes a lot more appealing.
-
- It’s also the most complex to set up, and for many people the threshold is “walking your tech-illiterate mother-in-law through side loading it over the phone, because she lives 100 miles away… She’s afraid to touch her computer for anything except email and Facebook. And then resetting her password every 30 days, because she keeps locking herself out of it.” Suddenly the “just fucking sign into Plex and it automatically discovers your server” option becomes a lot more appealing.
Jellyfin is the most complex to set up, right? (Just making sure I’m reading this correctly)
-
- Open source has high immunity to devs making changes at the expense of the user for their benefit because anti-features can be removed. Recommending another proprietary alternative here would be like saying they aught to leave an abusive partner but then recommend someone with the same red flags.
wrote last edited by [email protected]Welcome to “People rushing to suggest a solution that they fawn over because it’s open source.”
How do you personally 100% beyond a shadow of a doubt know that Jellyfin is the right solution? Why not a VPN, shared folder, and VLC? What about running a DNLA server?
Edit: All of you downvoting don’t know; and it makes you salty.
-
It gets around port forwarding/firewall issues that most people don't know how to deal with. But putting it behind a paywall kinda kills any chance of it being a benevolent feature.
port forwarding/firewall issues that most people don’t know how to deal with
This sort of thing makes me want to tear my hair out when I hear "Why bother rolling out IPv6 when IPv4 just WORKS!?"
NAT, port forwarding and the problems they cause are seen as expected, just the way the internet works instead of the dirty hacks they actually are. Most people aren't old enough to remember the time when everything connected to the internet had a routable IPv4 address.
-
I'll add to #2 (IDK if it's open source, though):
Give Stremio a try. Once you set it up (basically just add the Torrentio plug-in then whatever content catalogs you want), the workflow is much better and simpler than Plex.
You just browse it like Netflix: see something you want to watch, select it with your remote, then stream it immediately. No server to run, you don't have to build libraries, you don't even have download the content beforehand. Just select and watch. Could not be easier.
Is it torrenting in the background? Because, if it is, then you need a VPN and I don’t know how to set one up on my LG TV. Would you happen to have a guide?
