Unable to get to login page after channel refresh

[steveh]

Yesterday, I installed a new HDHomeRunQuatro on my network. I had previously done a Docker install of NextPVR on my NAS (QNAP TS-451+) while waiting for the Quatro to arrive.

After getting everything hooked up, I scanned and located the Quatro tuners and then setup my SD credentials and scanned for channels. Didn't get as many channels as I hoped I'd get, but it was a start! I was able to install the NextPVR add-on for Kodi, and I was watching TV, so I was happy.

Then I decided to relocate my antenna to see if I could do any better on channel reception. That's when everything fell apart. Kodi wasn't able to play anything, so I decided I needed to rescan. That worked with no problems, but didn't solve the Kodi problem. Reinstalling the Kodi addon didn't help either. Next I tried to stream something from within the NextPVR administration page. I could see the channel guide, but every time I tried to watch something (by clicking on it and hitting Watch Now), I got a page that looked like it was going to show, but after a few seconds, I'd get a red message at the bottom that said something like "stream failed". (I don't remember the exact message, and I can't replicate it at the moment, as you'll see shortly!)

I was able to install the HDHomeRun app on a few devices and watch various channels, so I know it's getting that far!

After messing with this for a few hours, I decided to call it a night. This morning I was ready to tackle it again and discovered I could no longer get to the login page to administer the NextPVR backend. So, I went the nuclear route - I blew away the container and started over!

That didn't help... Within the QNAP Container Station, I can see that the container is running, but when I try to go to the login page in my browser, I just get the "can't reach this page" message, so I can't do much else..

Any suggestions?

[mvallevand]

Re-scanning wouldn't have improved reception, it just would have found more or fewer channels.

After that you were seeing the browser cache, definitely one of the annoying things of NextPVR web. At this point if the container is running that is positive, sounds like you screwed up the docker configuration and didn't expose 8866

If you can open a bash shell into your docker you might be able to see the logs.

Martin

[steveh]

Yeah, my wording could have been better there. I wasn't trying to improve reception, I was trying to see if I could increase the channel count.

As for the main point of the post - I've figured it out (and you were on the right track) - I did publish the port, however, for some reason the name of my NAS isn't resolving on my local network - with the port. It is resolving without the port to go to the main NAS login page. Weird. Obviously, I've got something hosed up in the network configuration on the NAS. I'll figure that one out. In the meantime, going there by IP address works fine (this also explains why Kodi suddenly lost the ability to play as well).

[mvallevand]

Your hostname of your LAN IP is the hostname of NextPVR Docker too, the port is not part of the protocol. However there is no guarantee that hostnames are even broadcast around your LAN without some DNS.

Martin

[steveh]

That's what has me confused. Yesterday, I could get to http://NASname/ for the login page for the NAS and http://NASname:8866/ for the login page for NextPVR (before I started having problems). Today, I can get to http://NASname/ for the login page for the NAS, but can't get to http://NASname:8866/ for NextPVR. But I can go to the IP address (with the port) for the NextPVR backend...

Obviously, my NAS is misconfigured as it relates to the routing.

<Edit to fix port number>