craigmox / cetonproxy

An app that allows a Ceton InfiniTV PCI/network tuner to appear as a SiliconDust HDHomeRun to DVR apps like NextPVR, Plex, and Emby.
GNU General Public License v3.0
23 stars 7 forks source link

Cannot view lineup or channels via browser #15

Closed JoshDi closed 3 years ago

JoshDi commented 3 years ago

I have setup CetonProxy on my Ceton machine, but I am having issues pulling any data (lineup or channels). I have my firewall allowing any connections from cetonproxy.exe

Here are my settings: https://i.ibb.co/YjQJSRh/Ceton-Proxy-Settings.png

And here are my logs:

cetonproxydefault.log

[2020-10-16 13:41:06.529] Starting cetonproxy
[2020-10-16 13:41:07.079] Unable to bind HTTP server listening port
[2020-10-16 13:41:07.930] Checking tuner count
[2020-10-16 13:41:08.010] Determined tuner count: 6
[2020-10-16 13:41:08.010] Identifying tuner model
[2020-10-16 13:41:08.010] Getting diag\Host_Connection for tuner 0
[2020-10-16 13:41:08.030] Received diag\Host_Connection for tuner 0: "pci/ethernet"
[2020-10-16 13:41:08.030] Determined tuner model: PCI
[2020-10-16 13:41:08.030] Detected tuner listen IP: 192.168.200.2
[2020-10-16 13:41:08.030] Getting diag\Host_Firmware for tuner 0
[2020-10-16 13:41:08.050] Received diag\Host_Firmware for tuner 0: "15.1.13.152"
[2020-10-16 13:44:53.220] Checking tuner count
[2020-10-16 13:44:53.250] Determined tuner count: 6
[2020-10-16 13:44:53.250] Identifying tuner model
[2020-10-16 13:44:53.250] Getting diag\Host_Connection for tuner 0
[2020-10-16 13:44:53.270] Received diag\Host_Connection for tuner 0: "pci/ethernet"
[2020-10-16 13:44:53.270] Determined tuner model: PCI
[2020-10-16 13:44:53.270] Detected tuner listen IP: 192.168.201.3
[2020-10-16 13:44:53.270] Getting diag\Host_Firmware for tuner 0
[2020-10-16 13:44:53.300] Received diag\Host_Firmware for tuner 0: "15.1.13.152"

cetonproxydiscovery.log

[2020-10-16 13:41:07.109] Received SSDP discovery response from 192.168.200.1 on 192.168.200.2: HTTP/1.1 200 OK
CACHE-CONTROL: max-age=300
DATE: Thu, 01 Jan 1970 02:54:04 GMT
EXT:
LOCATION: http://192.168.200.1/description.xml
SERVER: Linux/3.0.1+, UPnP/1.0
ST: urn:schemas-cetoncorp-com:device:SecureContainer:1
USN: uuid:89333102-EBE5-11D8-AC9A-0000080958A0::urn:schemas-cetoncorp-com:device:SecureContainer:1

[2020-10-16 13:41:07.109] Received SSDP discovery response from 192.168.201.2 on 192.168.201.3: HTTP/1.1 200 OK
CACHE-CONTROL: max-age=300
DATE: Thu, 01 Jan 1970 02:54:04 GMT
EXT:
LOCATION: http://192.168.201.2/description.xml
SERVER: Linux/3.0.1+, UPnP/1.0
ST: urn:schemas-cetoncorp-com:device:SecureContainer:1
USN: uuid:89333102-EBE5-11D8-AC9A-0000080841D0::urn:schemas-cetoncorp-com:device:SecureContainer:1

[2020-10-16 13:41:07.129] Received SSDP discovery response from 192.168.200.1 on 192.168.200.2: HTTP/1.1 200 OK
CACHE-CONTROL: max-age=300
DATE: Thu, 01 Jan 1970 02:54:04 GMT
EXT:
LOCATION: http://192.168.200.1/description.xml
SERVER: Linux/3.0.1+, UPnP/1.0
ST: urn:schemas-cetoncorp-com:device:SecureContainer:1
USN: uuid:89333102-EBE5-11D8-AC9A-0000080958A7::urn:schemas-cetoncorp-com:device:SecureContainer:1

[2020-10-16 13:41:07.129] Received SSDP discovery response from 192.168.200.1 on 192.168.200.2: HTTP/1.1 200 OK
CACHE-CONTROL: max-age=300
DATE: Thu, 01 Jan 1970 02:54:04 GMT
EXT:
LOCATION: http://192.168.200.1/description.xml
SERVER: Linux/3.0.1+, UPnP/1.0
ST: urn:schemas-cetoncorp-com:device:SecureContainer:1
USN: uuid:89333102-EBE5-11D8-AC9A-0000080958A8::urn:schemas-cetoncorp-com:device:SecureContainer:1

[2020-10-16 13:41:07.139] Received SSDP discovery response from 192.168.200.1 on 192.168.200.2: HTTP/1.1 200 OK
CACHE-CONTROL: max-age=300
DATE: Thu, 01 Jan 1970 02:54:04 GMT
EXT:
LOCATION: http://192.168.200.1/description.xml
SERVER: Linux/3.0.1+, UPnP/1.0
ST: urn:schemas-cetoncorp-com:device:SecureContainer:1
USN: uuid:89333102-EBE5-11D8-AC9A-0000080958A9::urn:schemas-cetoncorp-com:device:SecureContainer:1

[2020-10-16 13:41:07.159] Received SSDP discovery response from 192.168.201.2 on 192.168.201.3: HTTP/1.1 200 OK
CACHE-CONTROL: max-age=300
DATE: Thu, 01 Jan 1970 02:54:04 GMT
EXT:
LOCATION: http://192.168.201.2/description.xml
SERVER: Linux/3.0.1+, UPnP/1.0
ST: urn:schemas-cetoncorp-com:device:SecureContainer:1
USN: uuid:89333102-EBE5-11D8-AC9A-0000080841D7::urn:schemas-cetoncorp-com:device:SecureContainer:1

[2020-10-16 13:41:07.169] Received SSDP discovery response from 192.168.201.2 on 192.168.201.3: HTTP/1.1 200 OK
CACHE-CONTROL: max-age=300
DATE: Thu, 01 Jan 1970 02:54:05 GMT
EXT:
LOCATION: http://192.168.201.2/description.xml
SERVER: Linux/3.0.1+, UPnP/1.0
ST: urn:schemas-cetoncorp-com:device:SecureContainer:1
USN: uuid:89333102-EBE5-11D8-AC9A-0000080841D8::urn:schemas-cetoncorp-com:device:SecureContainer:1

[2020-10-16 13:41:07.169] Received SSDP discovery response from 192.168.201.2 on 192.168.201.3: HTTP/1.1 200 OK
CACHE-CONTROL: max-age=300
DATE: Thu, 01 Jan 1970 02:54:05 GMT
EXT:
LOCATION: http://192.168.201.2/description.xml
SERVER: Linux/3.0.1+, UPnP/1.0
ST: urn:schemas-cetoncorp-com:device:SecureContainer:1
USN: uuid:89333102-EBE5-11D8-AC9A-0000080841D9::urn:schemas-cetoncorp-com:device:SecureContainer:1
mpatriche commented 3 years ago

Hey JoshDi,

Leave the 'External address as HDHomeRun' blank....and try again. Does that help?

Thanks!

JoshDi commented 3 years ago

Hey JoshDi,

Leave the 'External address as HDHomeRun' blank....and try again. Does that help?

Thanks!

I made 'External address as HDHomeRun' blank and restarted the application.

I still get an error 404 when trying to access http://192.168.1.50:5004/lineup.xml

mpatriche commented 3 years ago

Hey...happy to continue troubleshooting.. Would you be open to do a Zoom conference? My email is avail via my profile. Once we figure it out...will post the solution back in this thread..

JoshDi commented 3 years ago

@mpatriche thank you for helping me debug this. The problem was another app was running on port 80 (IIS) so I disabled the service and cetonproxy worked fine. Looking through the code, it looks like the app always tries to bind to port 80 for NextPVR. @craigmox can we create a flag to turn this feature on or off?

mpatriche commented 3 years ago

My pleasure...glad we got it working.

@craigmox It's also undocumented...that port 80 is locked open. Might be worth adding it to the README file.

craigmox commented 3 years ago

Thanks for the heads up guys. I removed listening on port 80. Hopefully no other DVR software needs it. (My testing abilities are limited right now)

mpatriche commented 3 years ago

Awesome! Thanks again! 👍