this post was submitted on 16 Jun 2025
536 points (91.0% liked)
Selfhosted
60001 readers
664 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam.
-
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
-
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
-
Submission headline should match the article title.
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
Well, with Plex constantly changing allowed abilities and such, it seems to me that this is the expected outcome.
This is one change (which isn't the cause of OP's problem) that they announced months ago. I've been using it for well over a decade and while I have had major issues with it in the past going so far as to setup Emby and buying a lifetime license for that, I would hardly say that they're "constantly changing allowed abilities."
Most people's issue with them is that they focus too much on adding new stuff that nobody asked for while ignoring longtime bugs. I can't recall a time they've ever locked anything behind a paywall that wasn't a brand new feature prior to this.
I can't speak for OP, but I self host lots of stuff, have literally dozens of services running, have an Ansible repo to manage it all and routi some stuff through a VPS, not to mention my day job has included managing services in one way or another for a long while. This is to say, I know what I'm doing. I couldn't setup Plex to work the way I wanted to, they expect it to run in a docker with network set to host mode, I couldn't find any way to tell Plex that my living room TV was in the same network, it just wouldn't accept any connections as local. I know I shot myself in the foot here by not letting it run with network on host mode, but I shouldn't have to, the port was exposed, I could reach it through the local network IP, but I wasn't able to stream any content locally.
If you don't set it to host, the docker container is in a different ip range than your tv. That's why it assumes it's not in the same network (which it isn't)
Sure, but they have a setting to fix this by letting Plex know that 192.168.0.x range is local network (as if it needed it) except it's behind a paywall.