Can't access NPVR Web server at any port

[no1453]

I just downloaded, installed, and configured NextPVR on my WIndows 10x64 machine. I can watch live TV, the recording seems to work, but in my attempts to connect NPVR to Kodi, I found out I cannot even access the web interface through my browser on the same machine, I get "refused to connect".
In Settings->Clients, the box next to "Enable Web Server" is checked, the port is the standard 8866, but going to the web address "127.0.0.1:8866" results in "Refused to Connect" in Chrome.
I thought perhaps the port was already in use, but changing the port to various other values, 8282, 8867, 7799, and then trying to connect to that port through the browser results in the same problem, refused to connect.
I've made sure nrecord.exe, nextpvr.exe, and ndigitalhost.exe are all "allow"ed through my firewall (Norton Premier 360). Even tested with the firewall disabled, still no go. Hopefully my included logs might give some clue what's wrong. Thanks. :confused:

[Graham]

The nrecord.log has this ...

2018-02-17 23:13:50.897 [ERROR][4] Unexpected error starting web server:
System.AppDomainUnloadedException: The application domain in which the thread was running has been unloaded.

I have no clue what the message means. Did you reboot after installing NextPVR? Might be worth trying. I expect someone will be along soon with a more professional suggestion.

[mvallevand]

Other users have that problem found it based on their virus scanner. You need to stop the recording service disable the virus scanner and then restart the service to do a good test for virus scanner and internet security blocking.

Martin

[no1453]

Thanks for the suggestions. After having no luck disabling my antivirus (same error when it was disabled), I uninstalled it completely and rebooted. The Nrecord.log still shows the same problem starting the web server.
I'm going to try to uninstall npvr completely, delete all files, and reinstall fresh. EDIT: Didn't help, same error.

[Reddwarf]

I seem to remember something about .net and problems with the server a long time ago but can't remember what. Maybe try searching the forum?

[no1453]

Thanks, I'll see what I can dig up. One addiotional detail, I notice in the NRecord.log that it keeps popping up with "IP Address: 192.168.56.1". The machine's actual local address is 192.168.1.167, so I'm not sure how to interpret that. EDIT: Ran ipconfig in a command shell, that ip belongs to "VirtualBox Host-Only Network #3" on my machine. It's probably using the wrong network adapter, I'll have to search for that in the forum, and try some things.

[no1453]

I disabled the VirtualBox adapter, and now the Nrecord log shows the correct IP, but still that unexpected error, so that doesn't seem to have been the problem.

[no1453]

Well, I looked through the forums for quite a while, didn't find anything enlightening. I did one more test after uninstalling my antivirus, and rebooting, and got the attached logs. It does not seem to be an antivirus problem, at least, because the Nrecord log is basically the same.

[Reddwarf]

Puzzeling. Hvae you tried uninstalling VBox and remove its' adapter? And perhaps check for .net updates although I think you'r having a different issue. Not sure what to suggest, I have never seen that error message before.

[eastavin]

you may be on the right track Reddwarf. I tried to access the server from EDGE and was surprised to see it does not work. I used to use it but that was several months ago. Here is the error I get from Microsoft Edge with Windows 10 16299.248 Its complaining about some file ambiguity in NEWA. No idea what it all means.