Newbe here... Kodi 17.6 with Nextpvr backend - PVR manager is starting up: 0%
#1
Hi all... recently started using Kodi 17.6 with NextPvr as my back end. Had everything up and running just fine. Was having trouble upgrading to Kodi 18.0 so I installed a fresh copy of Kodi 18.0 instead. Now I'm having an issue where the NextPVR PVR Client will not start up. When I first open Kodi I get an error message the Add-on couldn't be loaded. An unknown error has occurred. The only thing I can find so far that looks weird is when I click on "configure" (within the NextPVR Client add-on tab) the NextPVR Hostname is blank. Clicking on the hostname field opens another window where the hostname can be entered. the local host IP address is populated w/ 127.0.0.1. Clicking OK takes me back to the Settings screen where the Hostname now shows correctly.

Thought I might have an install issue with Kodi 18.0 being 64bit while NextPVR is 32 bit. So I've tried both 32bit and 64bit Kodi 18.0 as well as deleting everything and going back to Kodi 17.6 (the 32bit version I had up and running fine). All three versions of Kodi are giving me the same error message now...

Not sure where to start my troubleshooting...

Log file is:

https://paste.kodi.tv/epiruwuquy
Reply
#2
To eliminate some things the hidden hostname is normal.  There are no issues connecting 64bit clients to the 32 bit server.

The log errors look like it might be firewall or virus internet protection related.  Otherwise perhaps the server is not running, you would need to show us the NextPVR logs for that.

Martin
Reply
#3
Wink 
Thank you for the information, emveepee...

So, have started off by temporarily turning off my AVG antivirus as well as Windows Firewall... So far no change.

NVPR log

https://pastebin.com/QLhEZt7d

NRecording log

https://pastebin.com/C0pen5Bp

I'm not familiar with the pastebin website... If there's anything in my logs that shouldn't be on a public site, please let me know...
Reply
#4
You're better off zipping and posting all the NextPVR.logs.

In this case, web.log would have contained the most useful information, since that is where communication from Kodi arrives into NextPVR.
Reply
#5
You can also try opening http://127.0.0.1:8866 in a web browser, to check you can see the web app.
Reply
#6
(2019-02-03, 05:25)sub3 Wrote: You're better off zipping and posting all the NextPVR.logs.

In this case, web.log would have contained the most useful information, since that is where communication from Kodi arrives into NextPVR.
Thanks for the tip about zipping, will do this in the future. I'm not finding a flle named web.log. This would be in the same log folder as the other two, correct?
Reply
#7
(2019-02-03, 05:26)sub3 Wrote: You can also try opening http://127.0.0.1:8866 in a web browser, to check you can see the web app.
 Interesting... trying to open the local host address returns a "Problem loading page: Unable to connect...
Reply
#8
(2019-02-03, 05:58)ihscout64 Wrote:
(2019-02-03, 05:25)sub3 Wrote: You're better off zipping and posting all the NextPVR.logs.

In this case, web.log would have contained the most useful information, since that is where communication from Kodi arrives into NextPVR.
Thanks for the tip about zipping, will do this in the future. I'm not finding a flle named web.log. This would be in the same log folder as the other two, correct? 
Well, found my web log file. It wasn't there originally because the check box for "web server" on the Clients page of NextPVR was not checked. Restarted recording service and the following two lines showed up in a weblog file...

[...startup]
2019-02-02 22:12:13.930    [DEBUG][4]    Starting webserver for IPv6/IPv4
Reply
#9
.... and just like that, the local host webpage is now working as well as my TV service. Looks like that one checkbox to "enable web server" not being checked was the issue...
Reply
#10
Great.

You must have unchecked it at some stage because it's checked by default on a new install.
Reply

Logout Mark Read Team Forum Stats Members Help
Newbe here... Kodi 17.6 with Nextpvr backend - PVR manager is starting up: 0%0