this post was submitted on 29 Mar 2025
104 points (85.6% liked)

Selfhosted

45448 readers
304 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 9 points 5 days ago* (last edited 5 days ago) (1 children)
  1. This hasn’t been a notable issue in a while. That’s why Plex’s https-by-default was such a big deal. With https, even your ISP can’t see what you’re streaming. They can see that something is being streamed, but not what specifically.

Also, you totally glossed over the fact that Plex is simply easier for non-savvy people to set up. Plex provides a unified login experience similar to major streaming services, which Jellyfin simply can’t provide; If your mother-in-law can figure out how to log into Netflix on her TV, she can figure out how to log into Plex too.

And the unfortunate truth is that Plex’s remote access is much easier for 90% of users to figure out. It doesn’t require VPNs or reverse proxies at all. You just forward a port and anyone with access can easily see your server. But my MIL’s TV doesn’t even have access to a Jellyfin app without sideloading. Not to mention the fact that I’d need to walk her through actually setting the app up once it is installed, because there is no unified system for logging in. And if I’m not using a reverse proxy for my Jellyfin server, then I also need to walk her through setting up Tailscale, assuming her TV is even capable of using it at all.

Any single one of those hurdles would make Jellyfin a non-starter if I want to walk my MIL through the setup over the phone, and they’re all currently present. And some of them will never be fixed, by design. For instance, the lack of a unified login page is by design, because a unified login would require a centralized server for the app to phone home too. That centralization is exactly what Jellyfin was made to rebel against, so it’s a problem that will never be “solved”; It is seen by the devs and FOSS enthusiasts as a feature, not an issue.

From a FOSS perspective, Jellyfin is a modern marvel. But it’s definitely not at the same level as Plex when you compare ease of setup or remote access. Jellyfin is fine if you’re just using it locally, or are willing to run Tailscale to connect back to your home network. But if you’re looking for true seamless remote access and need to consider the mother-in-law factor, then Plex is hard to beat.

[–] [email protected] -2 points 5 days ago* (last edited 5 days ago)

You definitely do not want to expose Plex or Jellyfin to the internet.

That's a great way to get PWD as Plex has had its fair share of vulnerabilities

Port forwarding is almost is to easy to do as people do it without understanding the risk. That's one of the ways you end up with massive botnets.