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
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 (?).
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.
No, I was getting a 401 directly from nginx. Where is that last screenshot from?
https://websockets.readthedocs.io/en/stable/topics/authentication.html
Maybe your proxy didn’t have websockets enabled? Jellyfin does require websockets to function correctly.
Edit: https://github.com/jellyfin/jellyfin/issues/13511
another issue with same “problem” with a major contributor saying “unsupported”
There are solutions though… Yes, it’s not native and adds some little extra work but it’s already possible: https://docs.goauthentik.io/integrations/services/jellyfin/
I haven’t tried it though, it’s on my todo list and saved bookmark, just though I would share :)
An other solution would be to make a tiny wireguard server and make a VPN to your homeserver. Just put something like a bananaPi (or something else) into your grandparents house :) they won’t see any difference !
A plus could be to even add your own dns+pihole onto their network and block some of those nasty ads :) !
Solution for what? This thread is talking about basic auth breaking jellyfin.
Adding an auth layer IN jellyfin will not fix the unauthed endpoints. We’re talking about adding an auth layer BEFORE jellyfin here.
They also won’t know how to use it… how to debug it when it inevitably goes down… etc.
Yay! more support!