recording trouble

[sub]

Do you remember if you were using NScriptHelper to call setting.m3u.update, or if you used the 'automap' feature in the Settings->Channels page? It looked like either of these lead to that logging message that included the m3u url. Regardless, this log message is fixed for the next build, so that the url is properly obfuscated.

[sub]

Using NextPVR Version: 5.2.7.220410 on Lubuntu 20.04.

I keep having scheduled IPTV recordings to fail after 3 or 4 minutes after starting with the same error:

2022-07-14 05:34:01.693 [DEBUG][64] HTTP input source starting
2022-07-14 05:34:02.189 [DEBUG][64] Unexpected error in HTTP input source: System.Net.WebException: The remote server returned an error: (503) Service Unavailable.
  at System.Net.HttpWebRequest.GetResponse()
  at NShared.Shim.InputSourceHTTP.WorkerThread()

Unfortunately this is problem happening at your IPTV provider. For whatever reason, that service went offline and their server is returning 'Service Unavailable'. It's not uncommon for these types of IPTV services to be very flaky.

Does NextPVR actually stop/re-start the stream between retries?

Yes it does. The error message you see above is from it trying to restart a connection to your stream.

[sub]

NextPVR shouldn't be retrying on error since that could lock your account. 

It gives up on a 401 or 403 or 404. It will retry like 20 times with any other error (including this 503), with a 5 second delay.

[gdenton61]

Thanks for the reply sub.
You are right - I did use the 'automap' feature in the Settings->Channels page.
I counted 40 retries over ~9.5 minutes in the log after the initial error.

My provider is usually pretty stable but does hang here and there, I use Tivimate on an Android TV box when I watch on my TV and sometimes a channel stops like it's buffering but never resumes until I switch to another channel and right back to the original channel and then it's fine, I thought maybe that was a Tivimate issue but now I'm beginning to wonder if it's a provider issue.

[sub]

Thanks for the reply sub.
You are right - I did use the 'automap' feature in the Settings->Channels page.
I counted 40 retries over ~9.5 minutes in the log after the initial error.

You're right - it was 40. I recently reduced it, but you guys don't have that build yet.

My provider is usually pretty stable but does hang here and there, I use Tivimate on an Android TV box when I watch on my TV and sometimes a channel stops like it's buffering but never resumes until I switch to another channel and right back to the original channel and then it's fine, I thought maybe that was a Tivimate issue but now I'm beginning to wonder if it's a provider issue.

It's possibly your provider is changing the url, so we're just continuing to open a url that is no longer valid.

[sub]

My provider is usually pretty stable but does hang here and there, I use Tivimate on an Android TV box when I watch on my TV and sometimes a channel stops like it's buffering but never resumes until I switch to another channel and right back to the original channel and then it's fine, I thought maybe that was a Tivimate issue but now I'm beginning to wonder if it's a provider issue.

It's possibly your provider is changing the url, so we're just continuing to open a url that is no longer valid.

I've made a change for the next release to handle this possible scenario. (so that it'll go through the full redirection chain etc, in case the IPTV provider as switched the url - which they might be doing to try protecting the stream)

[gdenton61]

That sounds good sub, looking forward to the next release.