[Bug] DAZN VOD and live streams no longer start #1773
Comments
werimail
added
the
Triage: Needed
|
Logfile from Android Tablet. Kodi version 21.1 - Inputstream version 21.5.9 Could it be that the TLS verifications declined our request? Is there any possibility to deactivate it like with verify=False in requests-libraray of phyton? |
what means exactly "no longer start"? anyway the attached log file dont contains the video played attempt,
maybe missing or wrong headers in the license request, but could be also other PS. |
|
It's still working on Windows still with kodi 21. However, since last friday it isno more working via Amdroid. Header looks. For other requests within the addon we had to set verify-false to the requests to make it runable again. This was blocked about 2 weeks ago without. I will try it with inputstream.adaptive.config. |
|
Unfortunatelly the deactivation of ssl verification at inputstream.adaptive.config did not fix the issue. I do not understand why it's working with Kodi at Windows without any issue and with kodi at android the same addon with the same header information does not work. The data directly on the dazn website is still the same :-( Same URL is sent to inputstream via License server url |
this doesn't sound good... however you should try check the network flow generated by the original dazn app or try use dazn website on the android, sound more something changed on the dazn service |
CastagnaIT
added
Resolution: External
|
I have tried now a lot of difference settings but nothing works on Android, only via Windows. Kodi-Addon: `item.LaUrl = 'https://drm.playback.indazn.com/widevine/v1/license?legacyContentId=prod-live1&contentId=247Channel202_catchup&platform=web&manufacturer=microsoft&model=unknown&appVersion=0.64.0&uid=0012400000jSLLcAAO&accountStatus=ActivePaid&assetId=bj5o60qt6uoe1clfdsev239pr&tid=b9e12a7b-f582-4b9f-bca8-b84b0cca6c7a&uexp=1739091958209&mediaType=live&mediaId=247Channel202_catchup&metadata=country%3Dde%26ftv%3Dfalse&hash=4f36d5017349f7ae356d1a7d32aad5ccd51e7f9b0ee79033f00ee55dcac7f3dd' listitem = xbmcgui.ListItem() the License server url has the same paramater like sended via Windows. But with Kodi on windows it works, with Kodi on Android it does not. I always get http error 401 at android. for me it looks like a bug in inputstream-addon and not in my header. Otherwise, why it should work with windows but not with android? |
the http error 401 is some kind of denied access that come from dazn license server its not new that video services could use differents behaviours or apis between android and non-android operative systems, talking about ISA for kodi 21 nothing is changed on last months about how the license request is done, this from 21.5.0 of near the end of july 2024, so if you think that's an ISA regression you should test each version from 21.5.0 and older versions, another thing that you can check is via kodi Curl debugging, verify if the license requests contain the right data (i.e. headers, data format) and so check if android app sends the same data to the license server |
Hi @CastagnaIT with your advice, I tried the current DAZN addon under Kodi 20.5 (Nexus) on an Android 10 Device and lo and behold, it works without any problems!!! Greetings Weri |
|
then the first thing is that you provide me a kodi full debug log of kodi 20 and 22 with curl debugging enabled i need also that you link here the GH sourcecode of the dazn addon (better the py file that make the video callback to kodi) so that i have a better understanding of variables configured being, theoretically, a problem that goes back years it probably won't be easy to understand |
|
Indeed, with Kodi 20.5 it's working fine via Android. Addon available here:: Here already the logfile with Kodi 20.5 via Android: I will try to create the other logs during today evening/night. "curl debugging enabled" - you mean the normal kodi debugging - or is this something else? |
|
PS: |
|
@MRLB It is under Logging - debug loggimg is topmost toggle but debug categories is the toggle below the topmost one and category selection dialog is below that one. Click on that toggle, arrow down and enter the dialog and select cUrl. |
|
Kodi 20.5 - Android: |
|
Kodi 21.2 - not working: |
|
19:28:29.316 and 19:51:14.954 are the interessting lines Could it be an issue that the letters are no longer lower cases? |
|
And Log via Windows - Kodi 21.2 (working) |
|
The only difference what is visible is that the header_output has now capitels letters. Could this be an issue? Kodi 20 - Android (working) Windows (working): Kodi 21 - Android (not working) |
|
next time please use our paste service to post logs
http headers are case-insensitive, so no its not a problem i noticed that you are using two different android devices, another thing, on the if self.plugin.get_kodi_version() >= 21:
drm_cfg = {
'DRM KeySystem': 'com.widevine.alpha',
'License server url': item.LaUrl,
'License headers': urlencode(license_headers)
}
listitem.setProperty('inputstream.adaptive.drm_legacy', '|'.join(drm_cfg.values()))
else: |
|
"sure that the playback with kodi 20 works also on the android device used for kodi 21?" I will test it with urlencode |
|
Change code to following: Windows - Kodi 21: Working Same Log-files |
|
Could this be an issue? Edit: Android with Kodi 21 has other three extra lines: Android with Kodi 20: "Using HTTP2, server supports multi-use"-lines are missing with Kodi 21 at Android. Using Stream ID: 1 is also missing |
no idea but it could also depend on something else i don't know... |
|
Hi, I'm following the discussion for a few days now. My mind is still struggeling with the different responses to the To recap: the working one responds with whereas the broken one reads I want to emphasize the response header @MRLB already noted that the request headers are lower-case in the working example and upper-case in the broken one; @CastagnaIT already noted that HTTP headers are case-insensitive. My train of thought: Let's assume for a moment that HTTP are only supposed to be case-insentive, but the receiving end treats them in a case-sensitive manner. In other words: let's assume that the receiving server violates the HTTP standard. Let's further notice that the requests are made with a So maybe there is some kind of (new) "request sanity check" at CloudFront: if one advertises as being a Windows agent but sends the headers in some non-Windows way (here: mixed-case), maybe CloudFront treats this as some kind of spoofing and immediately responds with 401 Unauthorized? (Being a backend developer myself, I could implement such a server feature if requested.) As a last piece of information: my Linux-based browser (in which DAZN is working) sets the Widewine parameter The conclusion would be: either ensure that headers are sent lower-case all the way, or advertise as Linux (with all headers and request parameters) if you're running in a Linux-like environment. (TBH: I don't know if that would address the ISA addon or the DAZN one, therefore: just my 2¢) |
|
I would like to test it. With Kodi 20.5 and lower-case headers it is still working. With Windows and Kodi 21.2, also with lower-case headers it is also working. Only where upper-case headers are sent it is currently not working. |
|
Jumping into the discussion :) Did anyone try capturing official DAZN app / website and see if they specifically use lowercase headers as a primitive form of protection from unofficial clients :) |
|
According to firefox no: I can't replay it btw |
|
someone can test on kodi 22? and post the log with debug enabled and kodi curl debug enabled? |
|
Kodi 22 (kodi-20250215-cd3f2e08-master-armeabi-v7a.apk)- Android: Still: |
|
Is curl using the urllib3 library for the requests? |
|
I am asking because in the urllib3 library an if-statement in the ssl.py-file was changed and with the current version already the request for https://api.playback.indazn.com/v5/Playback fails. |
no, "curl" its itself a library |
|
Thanks for the information @CastagnaIT. (https://reqbin.com/req/c-ug1qqqwh/curl-ignore-certificate-checks) |
Describe the problem
DAZN VOD and live streams no longer start. An error message does not appear. A possible indication of this can be found in the log file.
Possible fix
No response
Steps to reproduce
No response
Debug log
kodi.log
Stream manifest file(s)
No response
Additional info
No response
Operating system(s)
Android
Operating system version(s)
Android 10
InputStream Adaptive version(s)
22.1.12
Kodi version(s)
22 Alpha (Piers)
The text was updated successfully, but these errors were encountered: