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
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!