Settings section - Devices and Channels pages not loading

[kevwag]

OK I tried that, same result.
Next I went full-sledgehammer and did a complete uninstall, rebooted, installed again and still the same issue, even before copying back config.xml and npvr.db3 from the renamed data folder (ie clean install), the same issue continues! At least the two files kept my channels safe so I'm still half-working.

There was a weird error with the uninstaller and it didn't exit gracefully but it did remove the C:\Program Files\NextPVR and C:\Users\public\NextPVR-data folders so unless there are files hiding elsewhere, I'm wondering if there might be something in the registry that should have been removed and wasn't.

Is there anything else I might be missing?

[mvallevand]

What if you go to localhost:8866 instead of 192.168.1.106:8866

Martin

[kevwag]

Yep, tried that... and 127.0.0.1:8866
I have IIS with php running on port 80 for my epg grabber but I haven't touched that and the two were happily co-existing up until a few days ago when I messed with those NPVR script files.
It's starting to defy all logic now!

[mvallevand]

It's defied logic for a while. Maybe go to the history and delete anything related to NextPVR and go to F12 storage and delete from there too. Also make sure javascript is enabled just in case you turned it off.

Martin

[kevwag]

Like I said, I've tried two browsers on the server itself and two browsers remotely from my laptop. I would be thinking browser issue myself if it wasn't for that

[kevwag]

I'm going to call it a night for now. Tomorrow I'll check there's no weirdness going on with windows firewall but again, I haven't touched that so nothing should have changed

[mvallevand]

Since you are using a completely new installation the only explanation is that it is browser related. The F12 log you posted looked to be javascript related.

Martin

[sub]

settings.html#:1 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist

Maybe something to do with this.

Tomorrow, if you know how to do this, and would like me to give it a try, you could forward the port to the internet on your router, and enable remote access (would need to change the username/password from the defaults, and tick 'allow remote access'). I could try connecting from here with my browser, and I'll look at any errors returned in the browser dev tools.

[kevwag]

Well, I'm delighted to say that the problem is now fixed!
True to form, the apparent cause defies logical explanation...
When the problem started, I had been working remotely on my laptop, editing files directly via a network share plus I had a remote desktop session to the server so I could run scripts on the server.
I thought back to you saying you thought postloadEPG.bat had not completed and remembered something that should have been completely irrelevant...

I remember that I did, at one point, mistakenly ran postloadEPG.bat from the network share (ie on the laptop OS) instead of doing it in remote desktop. I realised my error immediately but assumed it was benign; The script ran the pluto epg update followed by a couple of git commands. Since neither python or git are installed on the laptop, I assumed this would have failed without consequence, there were no command windows open to suggest otherwise.

I also considered the same "unable to connect" error you mentioned in your last post and concluded that something could be connecting externally and locking out a connection so I turned my attention to the laptop...
All browser processes were closed, no remote desktop was open but the laptop had turned off its screen and sat quietly running. I decided to reboot the laptop (I try to avoid this as it's an old laptop running W11 and reboots take forever), after rebooting I opened the settings page, clicked "Channels" and boom! Everything working again!

It makes no sense that something the laptop thought it was connected to, somehow managed to persist through complete uninstallation of the server and multiple reboots, or that running a script on the wrong machine might have caused such a situation to arise in the first place but I can find no other explanation that fits the facts!

Massive thanks to you Martin, for your help and guidance, I'm going to leave it alone now It's working again!

[mvallevand]

Glad you sorted it out. You did tell us the complete uninstall failed, so now you have explained why. Still not clear why today's reboot is different from other multiple reboots unless you meant multiple restarts.

What I am most surprised about is how the rename of NPVR-data worked with a locked file.

Martin