yeah, thanks. but thats not gonna work for me. i live in a big city and none of us (me and my server included) have static IPs nor am I gonna get them (at all) and I dont want to pay for them either (because ISPs here want you to pay for them). in any case, thanks for trying to suggest something. it might help someone else who has a different setup. :)
Thats not what I meant. I of course have wireguard set up for administration and my own streaming needs. But friends of mine who were able to use plex by just making an account but now they cant because of course there is no relay server etc. I'll have to think of a way to make it available to them (easily!) without putting my network at risk.
And the next wrong assumption. It's beginning to get really tiring. Maybe try to stop individualizing systemic problems. I know it is counter to our society but it is the only healthy way.
I'm building networks for a living. The situation I'm in has zero to do with my skills and assuming so is highly disrespectful.
But yes, as others have pointed out, it is likely that a configuration back when setting the service up years ago led to it using an outside connection which has only now become an issue because of plex's switch to blocking remote streaming.
Good point. I wanna point out that plex is not foss. Its closed source software which makes those moves even more idiotic because they could have paywalled new servers and accounts instead or weaned people off from their servers if they use local only, etc.
But yes, one only needs to look at foss projects like lemmy, pixelfed, kde, gnome to see how it is done. This absolutely means you have to have more people than just yourself or you will definitely burn out.
Tldr: some use gov funding, kickstarter, additional features, turnkey hosting, explain and ask for donations, etc.
I have it set up in a way. That does not make it wrong. This is an option that plex gives you without warning so its their problem in the first place. They also just paywalled that feature that worked for years and they're not considering the consequences or they dont care. The least they could have done is put a link "if youre seeing this on your home network, you need to do THIS."
Which has nothing to do with this local setup being suddenly paywalled. As others have pointed out, it seems like plex has led me to set it up in a way that always uses the remote connection and since they now paywalled that, i cant use it anymore until i either pay or change my setup.
The big difference here is freedom of association. In the real world, your life depends on being accepted into that group or migrating to another place while having huge losses and problems due to it later on.
I'm not sure i agree because an admin can also be protested against and they can share ownership (i did that as well). Its not as black and white imo.
You're assuming something that you just cant. I run this network alongside 5 others, some of them professional, for years. My configuration is standard and i'm using the software the same way i did for years.
If plex redirects my call to their server, that is their problem, not mine. I dont care what their inner workings are. I use a local address and this has happened for the first time.
Is it possible that it is an honest mistake on the side of plex? Yes.
yeah, thanks. but thats not gonna work for me. i live in a big city and none of us (me and my server included) have static IPs nor am I gonna get them (at all) and I dont want to pay for them either (because ISPs here want you to pay for them). in any case, thanks for trying to suggest something. it might help someone else who has a different setup. :)