SOLVED: Inconsistent media playback behind oauth or basic auth - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting) +---- Forum: Networking & Access (https://forum.jellyfin.org/f-networking-access) +---- Thread: SOLVED: Inconsistent media playback behind oauth or basic auth (/t-solved-inconsistent-media-playback-behind-oauth-or-basic-auth) |
Inconsistent media playback behind oauth or basic auth - urogna - 2024-04-09 Hi everyone I recently set up jellyfin for personal and family use. I then added a caddy reverse proxy for certificate handling and an oauth reverse proxy (oauth2-proxy). Everything runs and I can access jellyfin securly behind my google login (as well as my family) over my domain with https. I also set up an endpoint that can only be accessed through my home IP for tv use (since to my knowledge there's no way to set up oauth in the TV app, or any native app). The Problem: On my android phone, some movies and shows dont play, I get: "Playback Error: The client isn't compatible with the media and the server isn't sending a compatible media format" But this only happens when using my endpoint with oauth, and when I connect through my wifi and use the endpoint with the whitelisted IP, everything works fine. I get the exact same behavior when setting up basic auth with the caddy reverse proxy. I've dug into the problem quite a bit now, I even set up my own reverse proxy with oauth (with nextjs and next-auth) for debugging, and it looks like some calls don't reach the client because the secure environment gets stripped away from http headers and cookies, especially when the server want's to get info on how to transcode the media. I get no errors from the server, so I guess the server really just sends the wrong transcoded media I want to reiterate, every media plays perfectly fine when my reverse proxy directly communicates without any special cookies or https headers needed Other devices work fine, on desktop every call reaches the client, ipad runs media fine, but some calls are blocked, I guess it just can play the delivered media... It looks like only android web has this problem. Somehow I didn't find much on this issue... I'm stuck and could need some help Thank you guys for the awesome community and app Calls that get blocked look like this, it retries 3 times, before the playback error alert, as you can see, my session isn't present at that time, only the csrf token and callback: Code: const nextUrl = { RE: Inconsistent media playback behind oauth or basic auth - niels - 2024-04-09 The Android apps do not support cookies. It might be possible cookies are stored in the webview but those are not shared with the video player. RE: Inconsistent media playback behind oauth or basic auth - urogna - 2024-04-09 (2024-04-09, 12:03 PM)niels Wrote: The Android apps do not support cookies. It might be possible cookies are stored in the webview but those are not shared with the video player. Thanks for the reply I didn't clarify it well enough, I have this problem on android web browsers, but maybe on browser it has to do something with the video player as well, removing some cookies and headers. RE: Inconsistent media playback behind oauth or basic auth - urogna - 2024-04-10 (2024-04-09, 12:03 PM)niels Wrote: The Android apps do not support cookies. It might be possible cookies are stored in the webview but those are not shared with the video player. Thanks @niels this surely pointed me to the right direction. I ended up letting traffic through the /Videos/* path, pass by my oauth proxy. |