Guide Data no longer coming in

Channels DVR Server
#1

Hello, my guide data is no longer coming in. I've been running the latest server in a Docker container successfully for several months and this issue just cropped up to. The Troubleshooting page provides the following red flags:

Cloud Reachable
Could not connect to community.getchannels.com: Get "https://community.getchannels.com/": local error: tls: bad record MAC
Guide Provider
Could not connect to guide provider: data.tmsapi.com: Get "https://tmsdata.fancybits.co/healthcheck": local error: tls: bad record MAC
Remote Access
Could not send request to community.getchannels.com: Get "https://community.getchannels.com/dvr/api/remotehealth": local error: tls: bad record MAC

My logs indicate:
2025/01/18 16:37:39.769052 [TVE] action=cbs_station err=CBS stream is not available via your TV provider
2025/01/18 16:37:40.548667 [ERR] Failed to refresh auth: Post "https://community.getchannels.com/dvr/api": local error: tls: bad record MAC
2025/01/18 16:37:40.549171 [TLS] Requesting certificate for 04e091c7f5e9.u.channelsdvr.net
2025/01/18 16:37:40.580699 [DVR] Recording engine started in /channels-dvr
2025/01/18 16:37:40.582856 [zeroconf] no suitable IPv4 interface: listen udp4 224.0.0.0:5353: bind: address already in use
2025/01/18 16:37:40.582963 [zeroconf] no suitable IPv6 interface: listen udp6 [ff02::]:5353: bind: address already in use
2025/01/18 16:37:40.582998 [SYS] Bonjour failed to register service: No supported interface
2025/01/18 16:37:40.867121 [ERR] Generating SSL cert failed: get directory at 'https://acme-v02.api.letsencrypt.org/directory': Get "https://acme-v02.api.letsencrypt.org/directory": local error: tls: bad record MAC
2025/01/18 16:37:42.226292 [SYS] Created database snapshot: backup-20250118.223742
2025/01/18 16:37:42.226461 [SYS] Removing old backup backup-20241222.153416
2025/01/18 16:37:50.585865 [IDX] Pruned 0 expired airings from X-TVE in 456.321µs.
2025/01/18 16:37:50.586566 [IDX] Pruned 0 expired airings from USA-OTA61820 in 594.549µs.
2025/01/18 16:37:50.587046 [IDX] Pruned 0 expired airings from X-M3U in 393.32µs.
2025/01/18 16:37:50.590290 [IDX] Pruned 1 expired airings from X-VIRTUAL in 3ms.
2025/01/18 16:51:39.699273 [TRS] DNS: OK: Resolved host via system DNS
2025/01/18 16:51:39.699396 [TRS] DBG: Provider: "PAVLOV MEDIA INC" (PM-45) from 66.253.230.43
2025/01/18 16:51:39.957255 [TRS] Cloud Reachable: ERROR: Could not connect to community.getchannels.com: Get "https://community.getchannels.com/": local error: tls: bad record MAC
2025/01/18 16:51:40.069273 [TRS] Local Time: OK: Local clock is accurate
2025/01/18 16:51:40.069568 [TRS] TV Everywhere: OK: Chrome version up to date: 120.0.6099.129
2025/01/18 16:51:40.074842 [TRS] TV Everywhere DNS: OK: Resolved TVE authenticator via system DNS
2025/01/18 16:51:40.078819 [TRS] ad-dns: Resolved adservice.google.com: 142.250.190.34, 2607:f8b0:4009:81a::2002
2025/01/18 16:51:40.083743 [TRS] ad-dns: Resolved googleads.g.doubleclick.net: 142.250.190.2, 2607:f8b0:4009:80a::2002
2025/01/18 16:51:40.088445 [TRS] ad-dns: Resolved assets.adobedtm.com: 23.44.17.57, 2600:1407:7400:1c8d::1e80, 2600:1407:7400:1c89::1e80
2025/01/18 16:51:40.098509 [TRS] ad-dns: Resolved d.adroll.com: 174.129.212.252, 44.194.188.117, 2600:1f18:61c0:2205:9255:1843:74a5:42ea, 2600:1f18:61c0:2204:f883:9276:b37d:e3dc
2025/01/18 16:51:40.103069 [TRS] ad-dns: Resolved bat.bing.com: 150.171.28.10, 150.171.27.10, 2620:1ec:33:1::10, 2620:1ec:33::10
2025/01/18 16:51:40.108590 [TRS] ad-dns: Resolved pubads.g.doubleclick.net: 142.250.191.194, 2607:f8b0:4009:81a::2002
2025/01/18 16:51:40.118345 [TRS] ad-dns: Resolved edge.api.brightcove.com: 146.75.78.27
2025/01/18 16:51:40.127027 [TRS] ad-dns: Resolved medium.ngtv.io: 23.61.108.204, 2600:1407:7400:787::3134, 2600:1407:7400:78f::3134
2025/01/18 16:51:40.127105 [TRS] DNS Ad Blocking: OK
2025/01/18 16:51:40.397998 [TRS] Guide Provider: ERROR: Could not connect to guide provider: data.tmsapi.com: Get "https://tmsdata.fancybits.co/healthcheck": local error: tls: bad record MAC
2025/01/18 16:51:40.648668 [TRS] Guide Provider: Failed to lookup HDFX-4US (10B082D0): USA-OTA61820: Get "https://tmsdata.fancybits.co/v1.1/lineups/USA-OTA61820": local error: tls: bad record MAC
2025/01/18 16:51:40.648717 [TRS] Device Lineups: OK: All devices have guide data mapped
2025/01/18 16:51:40.648760 [TRS] Operating System: OK
2025/01/18 16:51:40.651298 [TRS] Network Interfaces: OK
2025/01/18 16:51:40.905068 [TRS] Remote Access: ERROR: Could not send request to community.getchannels.com: Get "https://community.getchannels.com/dvr/api/remotehealth": local error: tls: bad record MAC
2025/01/18 16:51:40.905192 [TRS] Recording Directory: OK
2025/01/18 16:51:40.906192 [TRS] Disk Permissions: OK
2025/01/18 16:51:40.906252 [TRS] Disk Space: OK: DVR directory '/channels-dvr' has 785.4G free
2025/01/18 16:51:41.097313 [TRS] DVR Version: OK: DVR is up to date
2025/01/18 16:51:41.097385 [TRS] DBG: Version info: &{2024.12.10.0055 https://cdn.channelsdvr.net/dvr false}
2025/01/18 16:51:41.097431 [TRS] DVR Status: OK: DVR is enabled

I've not made any network changes yet this issue has cropped up. What specific actions can I take to resolve? I'm not super technical so if you could "get me on the bus" in terms of where I go to make updates that would be greatly appreciated.

Thanks!

#2

Have you tried restarting your server?

#5

Yes I have.

#6

A quick search online shows that the most likely cause of the tls: bad record MAC error is generally to do with a faulty network driver or stability of your network connection. Another common issue could be some other software (such as an invasive firewall) putting itself in between the secure connection.

Looks like you need a new SSL certificate for remote access. A bad SSL certificate—or an untrusted self-signed one—already present on your system could also be the cause of the first error.

Something else on your system is already trying to use the ports that Channels wants. Because it can't bind to those network ports, it can't communicate with the internet, or get responses back when trying to do anything.

In short, you have network issues, likely stemming from bad or misconfigured network interfaces. Any further help would need additional details, such as how you installed Channels and which OS you are using.

#7

Thanks for the suggestions. In regards to installation, I'm on TrueNas Electric Eel and running Channels via Dockge. The installation has been working fine since September 2024 and this issue just flared up the other day.

I'm not sure how to track down a faulty network driver but will look into how to do that as well as the SSL certificate. I haven't introduced anything into the network that should be causing such an issue.
I'll look into how to identify what may be using these ports as well. Interesting that Channels had access to the ports for several months and now they seem to be taken away by another service. I would've figured the other service would've been denied the ports since Channels was already using them.

#8

Well now this issue seems to have resolved itself without my intervention. I have to laugh. I didn't do anything and the issue manifested and then after being gone for 2 weeks I come home and it has fixed itself. What a time to be alive!

1 Like
#9