MaggiWuerze

Having an https connection doesn’t do shit if the Backend is insecure. The issue with exposing Jellyfin are not man in the middle attacks, but badly managed access controls and unsecured endpoints.

Thede issues and the unwillingness of the devs to fix them because they are hellbent on keeping a maximum of client compatibility is what makes it hard to trust the overall security of the project.

That’s why basically everyone, including the devs, says to not do that and instead rely on a vpn to mitigate security risks.

An encrypted tunnel and a reverse proxy are two very different things. He (I) never talked about a tunnel and neither did the comment I (he) responded to

Reading comprehension and Jellyfin stanning don’t go well together

Feeling adventurous is exactly what you need if you decide to expose Jellyfin to the Internet (a reverse proxy adds nothing to security)

I never had the feeling the Jellyfin devs were were interested in outside contributions or ideas. A lot of the discussion in issues quickly gets passive aggressive from their side.

Since OP couldn’t be arsed to provide a link:

A self-hosted web news aggregator — own your feeds, your data, and your reading.

The crowd that claims that setting up an elaborate VPN scheme is fine has a problem entering an IP range?

Of course it is. That’s literally what it is made for

The state of Nextcloud is not in any way comparable to the mess Jellyfin calls a Backend

Thats why I said thread and not post. This thread was comparing the two

Theres a reason everyone uses a VPN to allow remote streaming for their Jellyfin. The things as open as a barns door, so you should not just open it to the public. Like I said, even the devs say not to do that, its just not secure enough

The fact that Plex does not even have settings for hardware encoding, besides on/off, tells me that’s bullshit

Running Plex locally is still perfectly viable without going through their servers

Surely you haven’t exposed your Jellyfin to the open net, since even the devs admit that that is a terrible idea

Surely you must be trolling at this point

(Assuming you have a Plex pass):

1. Setup for Plex isn’t just easier, its basically non existent. Run the exe, point to folder, done. HW encoding just works, transcoding just works, metadata gathering just works.

2. remote streaming. No need to setup an elaborate VPN scheme and install a client for it on every device you want to have remote access. It just works and even punches through CGNAT and the like

3. Clients. Plex has a client for every system under the sun. No need for sideloading or anything like that, they are everywhere

4. UI. Plex has a sane and good looking ui for the streaming client and the admin interface.

–

Jellyfin is not bad, but its just not a replacement for Plex. And the way the devs are acting, I doubt it ever will be

I also only paid 70€ for my Lifetime Plex, some 10 years ago. That was definitely worth it and continues to be, but this increase is pretty clearly a soft end for the lifetime licenses.

Would definitely have been the more honest approach

Because Jellyfin did not exist back then and does not have feature parity today? But I know you just wanted to show everyone how smart you are for using Jellyfin…

I, and I assume everyone on this forum who has one, paid around 50-100€ for their lifetime pass. My hardware encoding works great and doesn’t need me to tell it about each and ever codec in existence and how to handle each one.

The new price is insane, but that was not the topic of this thread.