Setting up a reverse proxy and dynamic domain is not one click. Jellyfin has also yet to resolve the unsecured api so I wouldn’t expose it on the clear
Setting up a reverse proxy and dynamic domain is not one click
Maybe not for the server administrator, but for users, it’s mega easy. Download Jellyfin app on TV. Enter URL for server. Login like a normal streaming service. Done. As far as I know, Plex requires these same steps, so if Plex works for your 89 year old grandparents, Jellyfin would as well.
Jellyfin has also yet to resolve the unsecured api
In what way is the API insecure? What types of attacks are you concerned about?
Setting up a reverse proxy and dynamic domain is not one click. Jellyfin has also yet to resolve the unsecured api so I wouldn’t expose it on the clear
Maybe not for the server administrator, but for users, it’s mega easy. Download Jellyfin app on TV. Enter URL for server. Login like a normal streaming service. Done. As far as I know, Plex requires these same steps, so if Plex works for your 89 year old grandparents, Jellyfin would as well.
In what way is the API insecure? What types of attacks are you concerned about?
Here is the primary writeup of the issues. My main problem is the way jellyfin staff handled this critique by downplaying and refusing to fix it
https://github.com/jellyfin/jellyfin/issues/5415