Multiple Issues

[mvallevand]

I still think a debug log from Kodi would help. Not sure if waiting for the final v5 will help solve this issue. There is also weakness in the NRecord log since we can't tell what port NextPVR is listening on.

Martin

[sub]

ok I switch from the legacy version of openelec to the newest version.  Disconnected all RPI's access web page via server, can operate everything from local host but nothing can access it from outside of localhost... I will probably give up at this point and live with 4.2.5 until v5 is ready to go...

As Martin says, you're probably need to work through it - it doesn't sound like the sort of thing that will magically fix itself. It hasn't been something others have noted, so I'm not aware of any issue I'll have to fix in NextPVR.

[bisonfan]

I will post my kodi logs when I figure out how to get them off of the sd card. I am not sure where to turn or try next, I did it work on 17.0.0.1 which is the same as localhost so not sure I am moving that far ahead... from there unsure...

[mvallevand]

The two easiest way to send logs are grabbing them via a windows share or installing the Kodi log uploader addon and posting the url here. Make sure debug logging is enabled.

Martin

[bisonfan]

Kodi logs are at https://paste.kodi.tv/uvakeripoy

NPVR logs are from the same time period and attached

A few updates, I update my RPI's to the newest version of Openelec.

4.2.5 port 8866 works perfectly for outside access

I tried to install the same setup on a different machine with the same results.  Starting to wonder if it is an install error. 

My first setup is the files on a second harddrive (small SSD for OS)

The second setup (Different pc) was on the same drive as OS, didn't seem make any difference.

**Note test logs are from first steup***

I installed MS network monitor 3.4, I can see that the router is directing traffic back to the server when attempting to access from outside, it than responds with the error.  I feel confident that my router is working correctly.  

I have reviewed all the firewall inbound policies and eliminated any duplicates there were.  As I type I thought I wonder about outbound policies... That appears to have no affect either.

I turned off windows firewall, nothing...

It works perfectly from my RPI's and localhost, anything else nothing...

Starting to wonder if I somehow got a corrupt copy from the main page download...

[mvallevand]

Sadly you didn't have debug logging when the important login occurred, it is better to turn on debug logging and restart Kodi to have it logging from the beginning. OpenElec is still why behind for RPi support I think most users have move on to LibreElec and I don't support that version of pvr.nextpvr sub might see something I don't In any case your logs are full of the errors from the crappy networking errors in the olders RPi so I would see if there is anything you can clean up to improve this. You should probably confirm that it is not firewall by disabling v4 and have v5 run on port 8866.

It is possible that the new web server timings don't like the old RPi's

If you are using this same RPi for 8867 and 8866 testing make sure you use the option to reset the PVR database in the PVR options when you change the ports. Rereading the thread the only explanation that the RPI works on local host is that you are reading the database cache.

Martin

[bisonfan]

Martin

Thanks for all the help!!  I did not realize I was running such an old system as well as you were looking for the startup logs.    Since it is easy to update the SD cards i switched to librelec with Kodi 18.4.  I have uploaded the kodi logs to https:\\paste.kodi.tv\ocagisigeh (these include the startup logs)


I am sorry I should make myself clear. On the RPI's I set the server information to my server IP address, port and pin and it works great!

My main goal with V5 was for my father to login into my pvr from his computer outside of my network.  when I attempt to use 192.168.50.85:8867 it shows an http 404 error.  

My steps I have been using to allow that to happen are router port forwarding port 8867 to 192.168.50.85.  The server should be listening and allowing the access.  THe same setup works fine on the same ports with 4.2.5. With V5 the only way I can see the web server is localhost:8867.  I am unable to watch tv from the web server on my own network.  It has to be on the server PC.

I don't understand how the RPI's can access it but nothing else seem to be able not to...

[mvallevand]

Wow I was diagnosing the wrong thing I thought you could run on 8866 an 8867 but that last log shows 8867 runs just fine.

Your internet IP for your father will not be your local LAN IP it will be the IP of your router unless you have a VLAN of some sort.

Can you connect to the web server on 8867 on the 192.168 local LAN at all or is it just live tv giving you troubles?

Martin

[bisonfan]

So I was going to load some pictures however they were too large and the kids want to minecraft...

127.0.0.1:8867 and localhost:8867 work on the "server"
192.168.50.85:8867 does not work on the "server" 192.168.50.85 is server DCHP address

I have a DDNS setup to help with ease of access for my dad

port forwarding is port 80, internal address is 192.168.50.85, internal port is 8867. this does not work when i attempt to access from my WAN ip address.

[mvallevand]

It will boil down to some configuration that you have done. Can you trace to it

tracert 192.168.50.85

Martin