In todays episode of “Plex enshittifies” Plex employee breaks ToS.
Source: https://forums.plex.tv/t/fake-reviews-on-play-store-by-plex-staff/917736
In todays episode of “Plex enshittifies” Plex employee breaks ToS.
Source: https://forums.plex.tv/t/fake-reviews-on-play-store-by-plex-staff/917736
Oh cool so you’re ok with opening ports on your server to the internet with no authentication. Good for you. Most of us with the technical knowledge of hosting a media server know better.
And Plex your opening 32400 not sure what your argument is.
What’s not authenticated? Run it through nginx and cloudflare, what exactly am I missing?
https://github.com/jellyfin/jellyfin/issues/5415
A reverse proxy won’t help (unless you’re doing authentication with it). A cloudflare tunnel would help, if it requires authentication.
Ah, let’s hope these get fixed then… 😬
Neither helps because jellyfin doesn’t work with auth in front of it. https://github.com/jellyfin/jellyfin/issues/13751
And any auth mechanism breaks EVERY app even if you implement one that doesn’t break the web UI. (short of VPN or other similar type of auth’d tunneling).
This is misinformation.
I run my jellyfin behind reverse proxy and use SSO pretty well. There is a OIDC plugin for jellyfin that just works with your preferred SSO.
Indeed Plex is easier to use, and manage all that for you, but this is self hosted community after all, there is smart people capable of running a reverse proxy and a proper SSO.
For the others, Plex indeed is forth paying for (?).
No it’s not.
The idea is putting an auth layer in a reverse proxy IN FRONT OF jellyfin. Not adding OIDC into jellyfin itself. Adding any plugin into jellyfin won’t fix the unauthed endpoints which would be the whole point of adding another layer of auth.
Sounds like it works fine in the scenario I was discussing.
Ah yes, single cherry picked sentence… Care to read the very next line? Where “unfortunately, […]”… Is that “shit doesn’t load right?” Weird.
Do you know of any apps that support basic auth input for jellyfin? No… Weird? What did I say again?
Oh right, I can just scroll up and read it.
I just tested and was able to get to the login page with an nginx proxy in front of jellyfin. A login attempt causes nginx to throw an error, but jellyfin itself seems fine. If I disable http basic auth, I’m able to log in and play video. This looks like an nginx configuration issue, and if I cared enough to actually get it working I’m sure it would.
Try logging in.
This is all you’ll see. Even if you setup a “guest” account with NO password… it’s all you’ll see. This is not a Nginx issue.
Edit:
The error appears in Jellyfins toast mechanism… so you know it’s not nginx.
Edit2: oh and don’t forget to downvote this comment too. I see you :)
Edit3: actually I just realized that you think THIS is nginx’s fault…
It is, but it isn’t… It requires the wss target on the server to handle it.
Jellyfin doesn’t do this. Nginx is passing it properly.
Edit4:
Thanks dad!
No, I was getting a 401 directly from nginx. Where is that last screenshot from?
Oh no, Chinese hackers know I only like the first 8 seasons of The Simpsons!
They would, I suppose, were my Jellyfin available to anyone living outside of my own state via geoblocking. You can’t even connect to it from the country I host the proxy from, not that they’d do anything if they could, all of the data shared is read-only.
I would’ve just let my setup be open, but, like you said, most of us with the technical knowledge of hosting a media server know better.
edit: chill with the downvotes, lads. Season 9 isn’t completely terrible.