-
-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This client isn't compatible with the media and the server isn't sending a compatible media format #166
Comments
Please post the ffmpeg log. The first one. The 2nd and 3rd are retries with forced transcoding. Side note. I sanitized the |
Thanks for the API key, I revoked it. |
😕 |
Wow you are right, it works. Didn't think such an error could have anything to do with NGINX, I guess it fails to stream the media properly? Though I don't get why it only happens with my TV... Thanks a lot, I'll try to debug my NGINX config. By any chance, do you have any idea where I should look at? |
Here it was caching of wrong MIME type. |
After hours of struggling I found out that even without NGINX, direct play was working but not transcoding. When I try to play HEVC, it produces the same error. It's a bit strange, sometimes I managed to see the first seconds of the video playing properly but then it stops and displays the error. Sometimes it just black screen when I try to play it but if I try to forward or anything it displays the error too. I tried on my main instance without NGINX (using Ngrok TCP proxy), but I also tried to launch a fresh Jellyfin instance on my laptop with Docker and accessing it locally and it did the same. If it helps, here are the server logs of my local reproduction : https://code.litarvan.com/acipayug.yaml ; [12:57:40] is the moment I tried fowarding since it was just stuck on a black screen. The client logs are here : https://code.litarvan.com/iqisaxiv.sql . Again, it works seamlessly from my computer, these issues are only on webOS :/ I'm starting to think it's just not possible to make this work under webOS 1 |
And also, here are all the FFMPEG logs produced :
|
I'm facing the same issue as above. Behavior are the same. It only occur if jellyfin is behind proxy. Direct ip:port did not cause this issue. I found that issue occur only for mkv formats on Android device. |
Had the same issue, interface worked well, no video playback when using reverse proxy. |
I am using an old LG TV (55EC930V) with webOS 1.4. I managed to make everything work (though it was pretty hard) but I'm stuck at video playback.
Though I have transcoding enabled (which works well on a regular PC using a browser), when trying to play any media (x246, HEVC, ...) on my TV using the webOS application, it tries out for a moment then tells me that this client isn't compatible with the media.
Client-side logs show that several media are tried without success:
And for the server-side ones:
The text was updated successfully, but these errors were encountered: