Server upgrades Mar 27 + Mar 28 - rsintas@q.com

[rsintas@q.com]

Is anyone else living in a nightmare right now? Everything going wrong since yesterday. The few times I could actually get it to load it would kick me out after a few minutes of watching both recordings and live tv.

Mainly have the error that hdhomerun cannot communicate with slicondust. PLEASE go back to the way it was just two weeks ago!

[signcarver]

I haven't seen any issues since that nearly an hour problem yesterday. You might want to mention location (possibly even isp/dns) and client device.

One thing I did notice a bit ago that https://ipv6-api.hdhomerun.com/discover isn't seeing any of my devices... however all are showing up properly at https://ipv4-api.hdhomerun.com/discover and modern devices normally don't show there (unless they only can reach SD via ipv4).

[nickk]

We are not tracking any communication issues right now.

Can you please provide some more information, including what player platform you are using and the Device ID of your HDHomeRun.

[emveepee]

I am seeing this for the ipv6 discovery

Code: Select all

>curl --connect-timeout 5 -v https://ipv6-api.hdhomerun.com/discover
* Host ipv6-api.hdhomerun.com:443 was resolved.
* IPv6: 2001:470:1:43a:9d51:de58:a363:5269
* IPv4: (none)
*   Trying [2001:470:1:43a:9d51:de58:a363:5269]:443...
* Connection timed out after 5009 milliseconds
* closing connection #0
curl: (28) Connection timed out after 5009 milliseconds

[nickk]

I am seeing this for the ipv6 discovery

Code: Select all

>curl --connect-timeout 5 -v https://ipv6-api.hdhomerun.com/discover
* Host ipv6-api.hdhomerun.com:443 was resolved.
* IPv6: 2001:470:1:43a:9d51:de58:a363:5269
* IPv4: (none)
*   Trying [2001:470:1:43a:9d51:de58:a363:5269]:443...
* Connection timed out after 5009 milliseconds
* closing connection #0
curl: (28) Connection timed out after 5009 milliseconds

Good find! Fixed

[Señor Bob]

A few minutes ago ipv6-api.hdhomerun.com was not responding to ping. It is now.

[emveepee]

Good find! Fixed

It was @signcarver that noticed it. It is working now and the correct JSON is being returned here.

Martin

[signcarver]

Don't forget that it can take up to 8 hours before the device checks in via ipv6... one of mine already did and another i forced via reboot

Edir: I'm not sure if that was op's problem just something that could explain it if device could only connect via ipv6 to SD.