

Yea, they were extremely vague about what the nature of their problem was, but they mentioned it was running on the same media library as their plex install. They insisted that it was because jellyfin was poorly designed and definitely not user error. Could have been a bunch of things, but it was almost certainly a config error. They said the server ‘locked up’ and all the other services became unresponsive any time jellyfin was scanning. They also did not like the way jf wrote metadata files to the media library volume. It was among their other complaints, such as ‘i didn’t like that you could reskin it’ and ‘it was too complicated to use for managing my book collection’.
sounded like a usergroup mapping issue to me but hard to say for sure. They said they weren’t interested in troubleshooting it so, whatareyagonnado? They seem really invested in not liking it though.
Yea, I don’t disagree, and I don’t actually fault anyone for using plex for it’s simplicity of remote configuration.
I do think a lot of people overlook simple workarounds to doing straight reverse proxies. I’ve used a VPN to access my remote services without issue for a long time. Granted, that’s still a prerequisite skill a lot of people don’t have, but I think a lot of people already inside the self-host space already have that knowledge. And frankly, self-hosting as a concept stems from this idea that with a little bit of effort, we can free ourselves from corporately owned SAAS companies - it shouldn’t be so divisive to be advocating for self-sufficiency.
There’s absolutely a place for plex. It’s a lot of people’s first foray into selfhosting. But I think people miss the opportunity to learn a new skill when they decide they’re willing to put up with abuse instead of taking the hint that it’s time to migrate.