Repeated log entries: "Error checking for update" and "Failed to refresh auth"

Channels DVR Server
#1

I just started using Channels a few weeks ago. I am running it on a Windows 11 PC and using a HDHR Prime (with CableCard) and TV Everywhere. Nearly every time the PC wakes from sleep or is rebooted, the following log entries are made soon after:

2026/02/02 15:34:26.538644 [SYS] Error checking for update: Get "https://channels-dvr.s3.amazonaws.com/latest.json": dial tcp: lookup channels-dvr.s3.amazonaws.com: no such host
2026/02/02 15:34:26.541646 [ERR] Failed to refresh auth: Post "https://community.getchannels.com/dvr/api": dial tcp: lookup community.getchannels.com: no such host

I haven't had any actual issues with my Channels DVR server functionality thus far. Recordings from both my tuner and TVE have been fine. I have been able to establish a remote connection to my server. My guide data is downloading every day without issue. If I manually click the Check for Update button on my Status page, it responds with "Up to date!"

And when I run the Troubleshooting routine under the Support tab, I get all green checks (except for Power Management since I do allow my system to sleep when idle).

Should I be worried about these log entries? If so, what should I do to fix the issue(s) causing them?

I'll be happy to answer any questions about my system and/or submit diagnostic data if necessary.

Thank you!

#2

Is it possible it’s a race situation where the network isn’t settled before those log events come up?

1 Like
#3

Thanks so much for taking the time to reply, KineticMan. :blush:

I was thinking that is a strong possibility since I think all or most entries occur right after starting/waking. I guess my question would then be, are log entries related to update checks and authorizations only made when there's a problem, but not when these activities are successful?

#4

This :point_up_2:

The developers will tell you to run the DVR Server on a device that stays on and awake 24x7.

1 Like
#5

Yep. Or just ignore the errors

1 Like
#6

So is it simply what KineticMan suggested? The initial attempt fails because things aren't yet fully up and running, but subsequent attempts succeed and just aren't logged?

Thanks so much for responding, chDVRuser and tmm1.

#7