@RickNappier said:
My Plex Server did not detect it either, but if I click on the manual link and enter the IP address, then it recognized it - and it worked fine.
I tried doing that too but it doesn’t seem to want to work.
@johnm_ColaSC said:
What version of Plex Media Server? What OS is the Plex Media Server? What is the IP Address of the Server and IP Address of the HDHR? Are they on the same subnet? Since you mentioned container I have seen other posts on the forum discussing vimage needing to be enabled. Have you looked at that setting?
Latest version, 1.9.0.4252 and its on a debian container.
Container - 192.168.20.53
HDHR - 192.168.20.16
It can definitely get the information it needs since the responses are 200 but then decides its not valid
They are however are not on the same LAN because subnet mask is 255.255.255.0, i would be surprised if that was the issue considering it can ping and talk to it
And what is vimage? Im running on LXC containers
Also whats weird is I restored a backup of when it was definitely working and it acted all fine, i could view all the channels and in the logs it was communicating just fine. I went ahead to add a new device just to see if it would find it, then all of a sudden its like “nope cant talk to it anymore” and says it cant contact the device even though i can still watch live TV through plex with it.
Sep 19, 2017 12:20:56.227 [0x7fc381ffc700] DEBUG - DVR:Grabber: Checking device URI http://192.168.10.16
Sep 19, 2017 12:20:56.227 [0x7fc381ffc700] DEBUG - HTTP requesting GET http://192.168.10.16/discover.json
Sep 19, 2017 12:20:56.228 [0x7fc381ffc700] DEBUG - HTTP 200 response from GET http://192.168.10.16/discover.json
Sep 19, 2017 12:20:56.229 [0x7fc381ffc700] DEBUG - HTTP requesting GET http://192.168.10.16/lineup_status.json
Sep 19, 2017 12:20:56.229 [0x7fc381ffc700] DEBUG - HTTP 200 response from GET http://192.168.10.16/lineup_status.json
Sep 19, 2017 12:20:56.230 [0x7fc381ffc700] DEBUG - DVR:Grabber: tv.plex.grabbers.hdhomerun called the probe of http://192.168.10.16 a success.
Sep 19, 2017 12:20:56.230 [0x7fc381ffc700] DEBUG - HTTP requesting GET http://192.168.10.16/discover.json
Sep 19, 2017 12:20:56.230 [0x7fc381ffc700] DEBUG - HTTP 200 response from GET http://192.168.10.16/discover.json
Sep 19, 2017 12:20:56.231 [0x7fc381ffc700] DEBUG - HTTP requesting GET http://192.168.10.16/lineup_status.json
Sep 19, 2017 12:20:56.231 [0x7fc381ffc700] DEBUG - HTTP 200 response from GET http://192.168.10.16/lineup_status.json
Sep 19, 2017 12:20:56.232 [0x7fc381ffc700] INFO - DVR:Grabber: The device was already discovered at http://192.168.10.16, updating URI
Sep 19, 2017 12:20:56.235 [0x7fc3bfbfe700] DEBUG - Completed: [192.168.20.10:54990] 200 POST /media/grabbers/tv.plex.grabbers.hdhomerun/devices?uri=192.168.10.16 (9 live) TLS GZIP 8ms 903 bytes (pipelined: 1)
Sep 19, 2017 12:20:56.314 [0x7fc3c03ff700] DEBUG - Auth: We found auth token (xxxxxxxxxxxxxxxxxxxx), enabling token-based authentication.
Sep 19, 2017 12:20:56.314 [0x7fc3c03ff700] DEBUG - Auth: authenticated user 1 as 12jdlovins
Sep 19, 2017 12:20:56.314 [0x7fc3c03ff700] DEBUG - Auth: Came in with a super-token, authorization succeeded.
Sep 19, 2017 12:20:56.315 [0x7fc3a0fff700] DEBUG - Request: [192.168.20.10:54990 (Subnet)] POST /media/grabbers/devices/discover (9 live) TLS GZIP Signed-in Token (12jdlovins)
Sep 19, 2017 12:20:56.315 [0x7fc3a0fff700] DEBUG - DVR:Device: Discovering and refreshing devices.
Sep 19, 2017 12:20:56.316 [0x7fc3a0fff700] DEBUG - DVR:Grabber: HDHomerun discovered 0 compatible devices.
Sep 19, 2017 12:20:56.316 [0x7fc3a0fff700] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/132670C0 at http://192.168.10.16
Sep 19, 2017 12:20:56.320 [0x7fc3a0fff700] DEBUG - DVR:Device: Device device://tv.plex.grabbers.hdhomerun/132670C0 died
Sep 19, 2017 12:20:56.320 [0x7fc3a0fff700] DEBUG - DVR:Grabber: Mystery discovered 0 compatible devices.