Unable to Add IPTV XMLTV (m3u works fine)

[add45]

Tried doing searching everywhere but apparently nobody has the exact same error as me. Logs don't give much useful info either unfortunately.

Situation: Trying to add m3u/ xml tv (.xml.gz) and getting errors for reading the XMLTV file. M3u adds fine if no xml tv is provided.

Further info: file is formatted fine, can't see any obvious errors in the xml. am able to access from multiple machines without read errs.
Running docker amd64, showing current version as Version: 5.1.1.210328

Logs:


[312] Got request [x.x.x.x]: /services/service (setting.scan.status)
[312] method=setting.scan.status
[312] parameters:
[312]    method: setting.scan.status
[312]    format: json
[312]    sid: 88744af3-c8de-4cf7-993b-3660e550d7c0
[312]    client_ip: x.x.x.x
[312]    user_agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0
[312]    host_callback: myhost.redacted
[312] setting.scan.status
[312] {"stat":"ok",
"complete":false,
"status":"Unable to read https://tinyurl.com/.../yh6a2hvp?....  [maZ76IC8XmvRzs2Nejaf/j5QIz4eo3OyAjZd8...snip...



I can provide the URLs if necessary as well. Any idea what the issue could be or how to further research? Feeling like at a dead end here.

[mvallevand]

Does it work better if you use the real URL and not the tinyurl redirection?

Martin

[add45]

Unfortunately not. Have tried combinations of this already. The m3u is a tinyurl as well and works without issue.

[mvallevand]

Note that m3u and epg logic are not the same. I suspect you need to post the full logs for sub to look at using the full url as the source.

Martin

[add45]

I suspect you need to post the full logs for sub to look at using the full url as the source.

Martin

Sorry I don't follow... here is all the logs related to the xml downloading. Using the full url as source:

Code:

2021-05-14T17:34:44.453807265Z "status":"Downloading xmltv Listings",
2021-05-14T17:34:44.453816143Z "channels": [
2021-05-14T17:34:44.453824409Z ]
2021-05-14T17:34:44.453832472Z }...snip...
2021-05-14T17:34:44.999236481Z [30] Got request [asdf]: /services/service (setting.scan.status)
2021-05-14T17:34:44.999293369Z [30] method=setting.scan.status
2021-05-14T17:34:44.999321118Z [30] parameters:
2021-05-14T17:34:44.999446686Z [30]    method: setting.scan.status
2021-05-14T17:34:44.999473786Z [30]    format: json
2021-05-14T17:34:44.999491011Z [30]    sid: 88744af3-c8de-4cf7-993b-3660e550d7c0
2021-05-14T17:34:44.999499833Z [30]    client_ip: asdf
2021-05-14T17:34:44.999508340Z [30]    user_agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0
2021-05-14T17:34:44.999517531Z [30]    host_callback: nextpvr.myhost.asd
2021-05-14T17:34:44.999525795Z [30] setting.scan.status
2021-05-14T17:34:44.999533775Z 2021-05-14 17:34:44    Renewing session: 88744af3-c8de-4cf7-993b-3660e550d7c0
2021-05-14T17:34:44.999542561Z [30] {"stat":"ok",
2021-05-14T17:34:44.999551168Z "complete":false,
2021-05-14T17:34:44.999559665Z "status":"Unable to read https://drive.google.com/.../uc?....  [XbyxOgVHc1hRfrrtepXl6FQLwlHb4xE+zVUJ2Q...snip...

There is no further logging detail related to downloading XMLTV which makes it so hard to diagnose.

[mvallevand]

The zipped logs from NextPVR is what I want, not snippets. However since you can't typically do a direct download from a google drive there probably are redirects that NextPVR isn't following. I will leave it for sub at this point.

Martin

[add45]

The zipped logs from NextPVR is what I want, not snippets.  However since you can't typically do a direct download from a google drive there probably are redirects that NextPVR isn't following.  I will leave it for sub at this point.

Martin

I understand, was hoping not to share the full zip as it contains plenty of sensitive data that I will have to go through and redact. For what it's worth, have gone through all the files in the zip, there isn't any further logging detail in there as well. I can respect you not taking my word for it though .

FWIW2 - the m3u is also following the same redirect without issue. I know you say that the logic is different from parsing the xml, but would the actual http request be that different as well?

Attached logs

[mvallevand]

If you do a head command on the xmltv file with curl what do you get

curl -I https://drive.google.com/....

Martin

[add45]

If you do a head command on the xmltv file with curl what do you get

curl -I https://drive.google.com/....

Martin

Here is the output looks like bad request for some reason..

HTTP/2 400
content-type: text/html; charset=UTF-8
x-chromium-appcache-fallback-override: disallow-fallback
p3p: CP="This is not a P3P policy! See g.co/p3phelp for more info."
content-security-policy: script-src 'nonce-uCf6hT4U61agQX/7BuWTnQ' 'unsafe-inline' 'strict-dynamic' https: http: 'unsafe-eval';object-src 'none';base-uri 'self';report-uri https://csp.withgoogle.com/csp/drive-explorer/
date: Fri, 14 May 2021 19:06:25 GMT
expires: Fri, 14 May 2021 19:06:25 GMT
cache-control: private, max-age=0
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
server: GSE
set-cookie: NID=215=OkGoLmntNigoImz6iXSdMoPPECM6emhKLoC5Sb4duP6PAoCvXVgiYtIgvUHJplzBo0xCDwVCAgf8xkzDTIUN_EzFKhS4wySUut2dd3XtsER6S2CZEeP5zL0Em1pOY2UNn1nFCW5t68INYWgCzxcN_CDO-UXLbFFkJlpVHlyyi6U; expires=Sat, 13-Nov-2021 19:06:25 GMT; path=/; domain=.google.com; HttpOnly
alt-svc: h3-29=":443"; ma=2592000,h3-T051=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"
accept-ranges: none
vary: Accept-Encoding

[mvallevand]

I am not sure how NextPVR can determine if a file is gz compressed then. If your source is text does it work?

Martin