But what about this? I can spin up a Docker image of Plex, log in, and it just works. My tech illiterate family members and friends can access it and I don't have to deal with setting all of these other items up. Plex will just use UPnP out of the box whereas I'd need to set up DLNA or some other means to get remote Jellyfin access working.

Maybe I am wrong but this is why myself and others opt to just use Plex for family and friends and Jellyfin locally. 🙂

[–] ILikeBoobies@lemmy.ca 1 points 4 weeks ago (1 children)

If it's in your own LAN then there's no setup. Just point to the internal IP after spinning up the docker image.

[–] JoyfulCodingGuy@lemmy.ml 1 points 4 weeks ago (1 children)

Sure but that's not the scenario I was describing. Internally on my LAN is fine but I share Plex with friends and family throughout the world. Plex setup just works whereas Jellyfin requires more.

[–] ILikeBoobies@lemmy.ca 1 points 4 weeks ago (1 children)

More work to port forward?

[–] JoyfulCodingGuy@lemmy.ml 1 points 4 weeks ago

While I could go through doing that, I personally do not want to have it be my public IP address and that port. I would want to set up a reverse proxy with HTTPS and a domain or something if that sort.

[–] FreedomAdvocate 0 points 4 weeks ago* (last edited 4 weeks ago) (1 children)

90% of the TVs out there. Not everyone has an android tv.

What url are you giving me for jellyfin? You’ve exposed jellyfin to the open internet? You know how stupid that is?

[–] ILikeBoobies@lemmy.ca 0 points 4 weeks ago* (last edited 4 weeks ago) (1 children)

You think 90% of TVs don't use Roku, webOS, Android, or Apple?

No different than exposing any other port service, like Plex for example. However it's my reverse proxy.

[–] FreedomAdvocate 0 points 3 weeks ago* (last edited 3 weeks ago)

No, they don’t.

Very different to that, actually. Someone with this poor knowledge of networking absolutely should not be exposing their server to the open internet.