NextPVR PVR Client: Tuner Not Available

[jdraket]

I've been trying to get NextPVR to integrate with Kodi for over a week now with no luck. Anytime I try and view a channel I get the error, "NextPVR PVR Client: Tuner Not Available". I have tried multiple suggestions from members in the Kodi forum (http://forum.kodi.tv/showthread.php?tid=235443).

I've attached my NPVR log.zip and uploaded my latest Kodi log to http://xbmclogs.com/pr2gtilxw

Any help?!?

Thanks,

A newbie.

[JavaWiz]

Looks like this is your problem - in the kodi log file:

Code:

725.15:26:31 T:9572   DEBUG: PVRManager - PVR::CPVRManager::OpenLiveStream - opening live stream on channel 'KTTV-DT'
726.15:26:31 T:9572   DEBUG: opening live stream for channel 'KTTV-DT'
727.15:26:31 T:9572   DEBUG: AddOnLog: NextPVR PVR Client: OpenLiveStream(11:KTTV-DT) (oid=7152)
728.15:26:31 T:9572   DEBUG: AddOnLog: NextPVR PVR Client: OpenLiveStream()@1
729.15:26:31 T:9572   DEBUG: AddOnLog: NextPVR PVR Client: OpenLiveStream()@2
[B]730.15:26:31 T:9572   DEBUG: AddOnLog: NextPVR PVR Client: HTTP/1.1 404 Not Found
[/B]731.                                            Server: Microsoft-Cassini/1.0.0.0
732.                                            Date: Fri, 21 Aug 2015 22:26:31 GMT
733.                                            Content-Length: 1196
734.                                            Connection: Close
735.15:26:31 T:9572   DEBUG: AddOnLog: NextPVR PVR Client: Unable to start channel. 404
736.

Sub may be able to provide some insight at to why that http 404 (not found) is occurring...

[sub]

Sorry, I might need to get you to do it again, and post the same logs, and also the kodi.log, so I can compare the timestamps between the two files.

I can't see the request arriving in the web.log, which returns the 404, but there is a lot of log there, so it's hard to know exactly where to look.

[jdraket]

Sorry, I might need to get you to do it again, and post the same logs, and also the kodi.log, so I can compare the timestamps between the two files.

I can't see the request arriving in the web.log, which returns the 404, but there is a lot of log there, so it's hard to know exactly where to look.

Thanks for looking into this. Here are my latest logs.

Latest Kodi log to http://xbmclogs.com/pdpcyblgd

[sub]

It's odd. I can't find any sign of the request in web.log, which is returning this 404 error.

I'd normally give you a patch with additional logging to help us track down what's happening. Unfortunately it's not great timing, with us in the final throws of testing for the next release, and my build isn't compatible with yours, so I can't give you a patch. If you can wait a few days until the next release is out, then I'm happy to take a closer look.

[jdraket]

It's odd. I can't find any sign of the request in web.log, which is returning this 404 error.

I'd normally give you a patch with additional logging to help us track down what's happening. Unfortunately it's not great timing, with us in the final throws of testing for the next release, and my build isn't compatible with yours, so I can't give you a patch. If you can wait a few days until the next release is out, then I'm happy to take a closer look.

OK, will do. Thanks!

[jdraket]

OK, will do. Thanks!

I figured out what the problem was. I had K9 Web Protection installed on my computer (internet family filter). The web interface that it uses for its program is 127.0.0.1 - the same address as NPVR. I uninstalled the program and it worked! Does anyone know if I can change the address for NPVR? I am going to reinstall K9 and give it a try.

[sub]

Great. Glad you got it sorted.

"127.0.0.1" is just a way of saying "the local machine". You can have multiple networking programs all running on the same machine. You could have problems if another application was trying to use port 8866, which is the default port used by the NextPVR web server. It's more likely just a case of your "K9 Web Protection" blocking what it thinks is internet communication, when it's really just communication between Kodi and NextPVR. You might have been able to add some exclusion settings in your K9 Web Protection software.