-
-
Notifications
You must be signed in to change notification settings - Fork 259
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
MSLerror - This title is not available to watch instantly #1278
Comments
Same on my side, I run kodi on Ubuntu 21.10 and a same error occurred. |
as explained in wiki the main cause (or more causes) of this error currently still to be unknown
is this a random theory of yours or a kind of suggestion to change something in specifics? |
these are some some info collected over the time, if can help: |
I don't have the "Force L3" in my raspberry pi 4, Kodi installation (Linux). Under "Widevine - Force security level" it says "Disabled" in red color. Is there a way to change this? |
While @guy99au might have made a guess, I must say that it would be a very strange coincidence if all of us started getting the same error today out of the blue. I'd be inclined to believe something must have changed as well. Is there a difference between the logs you have seen for this error before and those seen today @CastagnaIT ? |
I can't play no movie. Even those which runed just fine last week. |
Would this be where it fails?
Based on the logs from @Tony763 |
@fedevx only android could have L1 all other devices are always L3, then you cannot force L3 because you are already L3 your posted log is inacessible then i have no idea if it is really the same issue of @Tony763, where in the past was: this could means a lot of thing and nothing... example recently i have check the license request and i have not found new changes |
Same issue here, South East US.
Tried logout & login. Tried via settings to reduce to 576p, no change. Same sha1 for libwidevinecdm.so on Raspberry Pi OS, LE, & CE. So I am guessing it is Kodi-centric, whatever it is. |
Happened simultaneously on Kodi 19 (different package name) & Kodi 20 on Shield TV Pro 2019. Yesterday I was able to play it normally. This is definitely not a coincidence, there is some reason for the problem. Reinstalling ISA and re-logging into Netflix did not help. (at least for me) Based on what others have reported, the problem is likely unrelated to the device, the network, and the settings. |
i have now tried on my ARM amlogic CoreElec 20 (not updated old nightly) but works without errors (tested also on Linux Mint)
could be, and if this is a new change could also be applied in specified countries only before a worldwide rollout, |
maybe trying to update the useragent could solve, who wants try to update and give a feedback: |
I tested using Kodi 18.9 + Netflix Add-On v.1.12.8-Leia with Shield TV Pro 2017. @CastagnaIT |
@CastagnaIT |
@CastagnaIT I tried this UA below earlier and it didn't make a difference. Looking at the cadmium player, it appears the manifest request has a few new parameters:
Tried to throw in a hardcoded manifestVersion: v1, but no change on that. desiredSegmentVmaf seems to be the same as desiredVmaf. Don't know what the browser is actually sending, so it may not be relevant yet, would need to either add debugging to cadmium player or setup the proxy.
Edit: Tried the attachment, with your UA changes and it also didn''t work. |
@Liqianyu the only difference between the addon for Kodi 18 and 19/20, is that on 19/20 we use the new manifest request version @wagnerch is possible that that some parameters are changed but to check you have to add a break point in browser debugger |
@CastagnaIT Yeah, that's what I was thinking as well. I'll see about setting up the mitm proxy again and run it from Chromium on Raspberry Pi OS. |
I got this same error. CE on Odroid N2 running nightly updates. I should note that this happened right after an update on both the plugging and the nightly update. --removed-- And goes in hand with previous reported issues EDIT: Added the kodi.old.log entry |
I did mention on the forums that I'm getting an MSL error only when HDR is enabled on my Firestick 4K Max. If I disable HDR (device, not addon or Kodi) the addon can still play 2160p correctly. I can provide some logs of both in a couple hours. |
to all, if you want add logs that you think that report different data from the log posted on first comment of this thread, |
@CastagnaIT Sent a proxy log, logging in, selecting a video "Small Crimes" and playing a few seconds, on Pi 4. Sent to your Paypal e-mail address. |
@wagnerch found thanks! I try to see |
same here - Android 10 arm64, Kodi 19.3, won't play anything as of circa 12 hours ago, no problems before. Thanks and looking forward to solution! |
@CastagnaIT This is what I get in my debug log: https://paste.kodi.tv/idixukidog.kodi
|
@wagnerch not found changes in license request but manifest only as you mentioned i have adapted the changes: plugin.video.netflix_1.18.1+matrix.1_20211211_t1.zip |
@CastagnaIT Yep, appears to work with this update. |
This is working for me too. |
we are lucky we surpassed speed records in solving a problem :) |
Hi, thanks for the great plugin! I've downloaded above version but Kodi (19.3) gives error when trying to install 'failed to install add-on from zip file' - any ideas? Could file name matter? (Random name after saving the download)? Thanks! |
Confirmed, this fixed it for me also. Great Plugin! Thanks. |
@pfrieske |
Thank you!
…On Sun, Dec 12, 2021, 12:34 Liqianyu ***@***.***> wrote:
@pfrieske <https://github.com/pfrieske>
This is a test version, which I think requires kodi nightly builds.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1278 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AULGXTDKE4GYW5ZZHDB3KE3UQQX7TANCNFSM5J2V4KJA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
I tried updating to this version, using libreelec 10.0, with Matrix v19.1, updated the plugin to latest version, but I'm still receiving the same error as above. I verified the patch is in place, by searching the patched files for the code changes and they are in place. Can I provide any more info to assist on debugging the issue? |
Many thanks for your hard work. Working well. |
@ziporah you have to provide the full kodi debug log by following the instructions in readme |
installed off USB key version from above on my km3 android 10 box and after changing Force Widevine security level L3 I'm watching some as we speak! It might be worth mentioning my kodi (on android 10) has APK lowered to 28 to run elementum as described here Thanks again! |
@CastagnaIT didn't have time yesterday to get the debug log. Meanwhile problem is solved. For those who still have problems: in Expert settings:
|
Got the issue today and the version posted here made it work again. Thanks @CastagnaIT |
I've got the same issue with v.1.12.8-Leia. Any chance to backport the fix? |
I also have the same issue on a RPi4.arm / LibreELEC 9.2.8 / Kodi 18.9 (Leia) / Netflix addon v1.12.8. I have tested LibreELEC 10,0 with this fix and can confirm this issue is resolved there, but the Raspberry Pi 4B+ has other issues with LibreELEC 10 that means I am unable to upgrade permanently at this time. I would be very grateful if this fix could be added to Leia also. Thanks kodi.log |
Yes, please backport to Leia 👍 |
I can't find the L3 setting but had this issue today. Reinstalled widevine in plugin, and rebooted. Then I saw a notification of other updates inlcuding Netflix. Did work after another reboot |
Bug report
Your Environment
Used Operating system:
Describe the bug
Videos will not play, return error: MSLerror. This title is not available to watch instantly.
The debug log can be found here:
https://pastebin.com/TZJH8Mf7redacted -> wrong link or deletedOther information
Tried logging out, then in again, restarting TV box, checked ESN (both OK) and changed Expert setting to L3 - nothing worked. The fact this has only happened today on two different boxes suggests a change at Netflix or maybe inputstream.adaptive?
The text was updated successfully, but these errors were encountered: