Kodi not connecting to NPVR backend

[sitush]

Had a nightmare - Windows 10 update at the weekend left me with black screen problem, rollback didn't resolve it and I've ended up having to do a Windows reset. NPVR reinstalled etc but a Kodi client running on another PC no longer connects.

The NPVR PC IP address is the same and correctly configured in the Kodi NPVR plug-in. The PIN has been re-entered because I seem to recall that has to be done even if defaulting to 0000. The port is set to 8866 in both the client plug-in and the NPVR backend. When I enable the plug-in, it very briefly (one second or so) flashes a message at top right of Kodi window which, I think, is the usual plugin-in scan for channels.

I'm doing something obvious wrong but I'm blowed if I can work out what it is. I'm quite happy for someone else to embarrass me by explaining Thanks.

[Graham]

I'm quite happy for someone else to embarrass me ...

We'll try our best. Please reboot to reset all of the logs, try to get Kodi to reconnect, go to NextPVR Settings --> About and press the button to zip the logs, attach the zip to a post. Thanks.

[sitush]

Ha! Done as per your instructions. I'm suspecting some firewall issue but the settings look ok two me - 2 NPVR services/programs being allowed through.

[sitush]

I've just installed Kodi on the PC that NPVR is installed on - it works fine there.

[TDown]

You can rule out network/firewall with a simple Telnet test from the problematic client:

1. Add 'Telnet Client' to your operating system:

• Run 'optionalfeatures' without quotes from Run dialog (Windows Key+R)
  
• Check 'Telnet Client'
  
• Press 'OK'

2. Launch Command Prompt

3. Type the below (Ensure 'npvrHost' matches exactly as entered in Kodi/NPVR Addon):

Code:

telnet npvrHost 8866

A successful test will be a blank window with a flashing cursor versus an error/timeout of some sort. The command prompt can be closed at this point.

[sitush]

The problematic client is Ubuntu-based. I will see if I can find equivalent commands, thanks.

[sitush]

And the command

telnet 192.168.0.12 8866 in Ubiuntu returns

Trying 192.168.0.12...
Connected to 192.168.0.12.
Escape character is '^]'.
HTTP/1.1 400 Bad Request
Server: NextPVR WebLite
Date: Fri, 11 May 2018 15:47:03 GMT
Content-Length: 1204
Connection: Close

[sub]

It looks like the NextPVR side of things is ok.

Might be worth checking if your firewall is stopping incoming requests.

After that, next step would probably be enabling debug logging in kodi, restarting, then posting the kodi.log.

[TDown]

And the command

telnet 192.168.0.12 8866 in Ubiuntu returns

Trying 192.168.0.12...
Connected to 192.168.0.12.
Escape character is '^]'.
HTTP/1.1 400 Bad Request
Server: NextPVR WebLite
Date: Fri, 11 May 2018 15:47:03 GMT
Content-Length: 1204
Connection: Close

Your Windows box is allowing the connection through.

I get the below responses from a working NPVR server.

Linux Telnet:

Code:

Entering character mode
Escape character is '^]'.
HTTP/1.1 400 Bad Request
Server: NextPVR WebLite
Date: Fri, 11 May 2018 17:35:56 GMT
Content-Length: 1204
Connection: Close

Windows Telnet:

Code:

HTTP/1.1 400 Bad Request
Server: NextPVR WebLite
Date: Fri, 11 May 2018 17:37:56 GMT
Content-Length: 1204
Connection: Close

[sitush]

The Kodi device hasn't changed since before the Windows NPVR device went doo-lally and had worked ok for ages. The problem surely has to lie at the Windows/NPVR end because that is where the changes have happened.

I've just turned off the firewall completely at the NPVR end and still Kodi does not populate on the client. I then did as Sub suggested and attach the Kodi log.