Watch now issue

[bader77uk]

Edit: Thanks for your checks and comments..Yes you're right, i was testing a channel which keep returning an error code 403. but i dont think its the issue, this testing was an hour and 27 mins before the block occurred if so why not block me instantly.

i am re-testing timer recording again for 40mins length with live buffer value = 5 mins

Edit: Tested passed no issues

[bader77uk]

I've made a changed for the next build to not retry if it receives a "(401) Unauthorized" when attempting to reconnect.

i would also suggest to make a delay between retries if receives HTTP  "(403) Forbidden" longer delay more chances to get 200 response back, currently its retries too often and hundreds of times which makes it even worse and might occurs a block from provider

Note: i got this issue last night and figured out when i checked the logs also i checked the channel manually after sometime when nextpvr stopped retries and i got 200 response.

[mvallevand]

I never saw hundreds of 403 I saw many 401's which sub says he fixed. Ultimately if 403 is turning to 200 you need to contact your provider to fix their service.

In the log you provided the 403 continued for quite a while and this is not something NextPVR can fix with a dealy, although it probably shouldn't be going to ffmpeg and sub can look at that.

Martin

[bader77uk]

This issue just happens recently please check the new logs.

i have contacted providers about this error and they have nothing to do about it as i have understand its the source issue.

but based on my experience if you implement a delay between retries it will get more chance to receive HTTP 200 response, i have checked the channel after half an hour of last retry by nextpvr and it works. and it may work in less time

Edit: "Forbidden" 652 Matches

[mvallevand]

Ok you are now getting a 403 where sub said he fixed the 401 so I assume both cases will be handled. Unfortunately you didn't include all the logs to do a proper root cause analsys and I am getting tired of asking so good luck.

Martin

[bader77uk]

Thanks for your checking

Edit: full logs added

[bader77uk]

just a confirmation with web app

in Recording Scheduler section:

is it work to edit the Scheduled task and click 'save' or i have to cancel it and re-create?

[sub]

Ok you are now getting a 403 where sub said he fixed the 401 so I assume both cases will be handled. 

The change I made will stop trying if it gets either a 401 or 403.

[sub]

but based on my experience if you implement a delay between retries it will get more chance to receive HTTP 200 response, i have checked the channel after half an hour of last retry by nextpvr and it works. and it may work in less time

This http retry logic was not originally created for IPTV - I was thinking about HDHomeRun devices, where an instant reconnect will often get things going again immediately.

The retry logic does step down for it's frequency if it's continues to fail. ie, 10 nearly instant reconnects, then followed by 100 five second reconnect, before falling back to 30 second reconnect attempts.

However with that change I've made, it'll now stop retrying for that recording after receiving a 401 or 403. ie, so next reconnect will be at next live tv or recording attempt.

[mvallevand]

Ok. There is an issue of the earlier 403 (maybe on the HEAD) being sent to ffmpeg that should be avoided.

Code:

2020-06-25 22:37:43.388    [DEBUG][271]    ConnectToURL:
...
2020-06-25 22:37:43.427    [DEBUG][271]    WebException: System.Net.WebException: The remote server returned an error: (403) Forbidden.
   at System.Net.HttpWebRequest.GetResponse()
   at NShared.IPTVRecorder.ConnectToURL(String url, Int32 depth)
2020-06-25 22:37:43.427    [DEBUG][271]    CheckTSUrl done
...
2020-06-25 22:37:43.427    [DEBUG][271]    IPTV StartStream@3.3
2020-06-25 22:37:43.427    [DEBUG][271]    IPTV StartStream@3.4
2020-06-25 22:37:43.427    [DEBUG][271]    IPTV StartStream@3.5
2020-06-25 22:37:43.427    [DEBUG][271]    IPTV StartStream@3.5.1
2020-06-25 22:37:43.427    [DEBUG][271]    Executing: ffmpeg -y -user_agent "VLC/2.2.6 LibVLC/2.2.6" -vaapi_device /dev/dri/renderD128 -i http://.... -codec:v:0 h264_vaapi -codec:a:0 aac -strict experimental -ac 2 -ab 128000 -f mpegts  -

Also a weird on where a new xc m3u stream is being send to web client as a url. Could be user error.

Code:

2020-06-24 18:58:23.305    [DEBUG][36]    parameters:
2020-06-24 18:58:23.305    [DEBUG][36]       method: setting.scan.start
2020-06-24 18:58:23.305    [DEBUG][36]       format: json
2020-06-24 18:58:23.305    [DEBUG][36]       source_id: 21
2020-06-24 18:58:23.305    [DEBUG][36]       m3u: ...
2020-06-24 18:58:23.305    [DEBUG][36]       xmltv: ...
2020-06-24 18:58:23.305    [DEBUG][36]       sid: 2a488118-8030-4a98-8558-64e412b2a3b5
2020-06-24 18:58:23.305    [DEBUG][36]       client_ip: ::ffff:89.203.22.109
2020-06-24 18:58:23.305    [DEBUG][36]       user_agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:77.0) Gecko/20100101 Firefox/77.0
2020-06-24 18:58:23.305    [DEBUG][36]       host_callback: acid.seedhost.eu:8866
....
2020-06-24 18:58:23.486    [DEBUG][283]    Downloading m3u xc://ip...
2020-06-24 18:58:23.909    [DEBUG][283]    Failed to download channel list: System.Net.WebException: An exception occurred during a WebClient request.
---> System.NotSupportedException: The URI prefix is not recognized.
   at System.Net.WebRequest.Create(Uri requestUri, Boolean useUriBase)
   at System.Net.WebRequest.Create(Uri requestUri)
   at System.Net.WebClient.GetWebRequest(Uri address)
   at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)
   --- End of inner exception stack trace ---
   at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)
   at System.Net.WebClient.DownloadString(Uri address)
   at NShared.Recorders.IPTVScanner.WorkerThread()

Martin