I always wonder why some people are so dedicated to Jellyfin. Even if JF had full feature and experience parity, it would still not have secure remote access the way Plex does. There is no need to port forward or NAT Plex for external access if you use app.plex.tv to access. With the threat landscape the way it is today, that is worth a lot.
I haven’t used Plex in a while, but I’m confused how Plex handles WAN connections without using any port forwarding? how is that possible?
I think there’s a misconception.
Plex can “hide” (not really) your own server because you can direct your users on Plex.tv (they can login there, etc. without ever typing your IP address).
But Plex can also use an internal reverse proxy that lets you see your content from outside even without port forwarding. However, quality and speed will be decreased.
I think Jellyfin should work to ease the process of setting up your server as much as they can, but unless they start managing a SaaS like Plex does, they’ll never be able to offer the same simplicity for the end user.
I’m trying to switch to Jellyfin I really am. With Plex I could just throw a file bot at my files normalize the names and it was fine. I can’t mark things watched or unwatched from the Roku client. I’ve now tried three separate times to get the Doctor who specials to show up with names. Plex is by no means perfect but it’s so much easier to keep Plex goomed
I was fretting over Doctor Specials, season numbers, eras and naming a few weeks back. In fairness it has been running since black and white times so not too bad considering. Whats a filebot by the way and whats a good one?
You know, I’ve heard this gospel before, I might still have the pamphlet…
Honestly, I haven’t really looked into jellyfin yet. I hear it’s superior in some way… But I already have Plex all set up and I have 4 friends with servers and we all share content. So it would take a lot for me to switch.
Plex is a privacy nightmare that’s slowly trying to faze out you having a server all together in favor of feeding you commercialized content from other providers; and many people find Jellyfin is far too unpolished/disorganized for a lot of debatable reasons I won’t go into.
I’ve been quite happy with the middle ground: Emby. It’s not FOSS, but is well polished with consistent development, great feature parity across platforms, excellent clients for pretty much every device I’d want to use, and a helpful community ready to assist with any problems you come across. They also have a heavy focus on privacy; with no third party partners collecting your info like Plex, and no telemetry sent from servers/clients.
The lifetime premier license I bought 7 years ago was well worth it.
Wasn’t Jellyfin developed using the Emby source code as a starting point?
Yes. Emby was originally open source, but people would regularly fork it to remove the licensing. When they chose to go closed source; jellyfin forked that final release and has built from there.
Emby has a premier licencing system to support their development, instead of selling user data and making deals with content providers like Plex, or depending on OSS development/contributions like Jellyfin.
As far as I understand almost 80% of jellyfins current code is the original Emby code (called ‘media browser’ or ‘MB’ at the time), though to be fair, I haven’t verified that claim.
Jellyfin is a bitch to get working outside my network. I don’t get how Plex made it so easy
really? I never had an issue with just sticking it behind a reverse proxy, doing some port forwarding, and setting an apex domain record, that was it. curious what wasn’t working for you?
