Channels has gone bonkers!

#1

Can someone tell me what the error message means in the attachment. My system seemed to be working fine (was having some problems with recordings) but had not problem with everything else.

Today, while watching live TV, the picture would go off and I would get a "Playback failure (0)" error message. If I went back to the guide, the program would restart, but after a few minutes, the error screen reappeared.

While watching a recorded program, it kept stopping and starting every few seconds like it was buffering.

No clue what brought on these group of errors and problems. I have already rebooted my modem and router.

Any help or suggestions to get my system to start working properly again?

Screenshot 2023-01-13 222244
Screenshot 2023-01-13 2222441057Ă—452 71.3 KB

2 Likes
#2

Can you go to https://speedtest.net/ and post the results here?

Are you using the DNS servers provided by your ISP or have you customized them? (to 8.8.8.8 or otherwise)

1 Like
#3

I had similar errors, only last night, and on 2 different internet sources (TVE and the ESPN+ bits)

2023/01/13 19:47:51.792355 [TNR] Opened connection to TVE-YouTubeTV for ch6196 CBSSPORTS
2023/01/13 19:50:18.966143 [TNR] Error during live stream for ch6196 CBSSPORTS: hls: temporary failure while downloading: GET: https://cbssn.cbssvideo.com/live/853636/3659760/23/01/14/00/1673657381152.ts: 403 Forbidden
2023/01/13 19:50:18.968473 [SNR] Buffer statistics for 192.168.50.76 (tv room) for ch6196 CBSSPORTS: buf=0% drop=0%
2023/01/13 19:50:18.983028 [TNR] Closed connection to TVE-YouTubeTV for ch6196 CBSSPORTS
2023/01/13 20:07:30.150941 [ERR] Could not parse client registration: read tcp 192.168.50.128:8089->107.122.192.97:64113: read: connection reset by peer

I'll keep an eye on this today, but given the timing, I'm thinking something bigger is up.
I'm on ISP DNS and speedtest over 300Mb down, with gigabit on this whole chain.

#4

Something odd is going on this morning as “On Now” icons have been really slow to populate and I’m seeing timeouts on TVE streams like this on multiple channels:

2023/01/14 10:17:23.425409 [ERR] Could not start stream for TVE-Philo ch6768 BLOOMBERG: TVE: Could not fetch playlist: www.bloomberg.com (Timeout): Get "https://www.bloomberg.com/media-manifest/streams/phoenix-us.m3u8": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2023/01/14 10:17:38.790539 [ERR] Could not start stream for TVE-slingtv ch6768 BLOOMBERG: TVE: Could not fetch playlist: www.bloomberg.com (Timeout): Get "https://www.bloomberg.com/media-manifest/streams/phoenix-us.m3u8": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

Additional Info: DVR 2023.01.14.0039
My Sling and Philo apps are working without issue.

1 Like
#5

Dont know if its related or not, but I noticed some unusual errors on a pluto stream yesterday as well. BBC FOOD had temporary error in the log. In practice we were watching the program, and then got “stream unavailable” in middle of the show. Happened a couple of times.
Other channels appeared to be fine.

Didnt really pursue it until i saw this thread.

image
image1668Ă—901 185 KB

Im on isp with 500mb down 80 up, on hardwired gigabit ethernet.

#6

Hi Eric,

I ran the speed test by three different apps. The first, my download was 261, upload was 40. The second, download was 587 and the upload was 23. The third test was 578, upload was 23. One of the tests was using the app you mentioned.

I have not changed my DNS, so whatever Spectrum set it when installed, the setting remains. I don't have a good understanding of DNS settings and wouldn't attempt to change without some guidance.

All of my problems were happening on my main TV in the living room. It is directly connected to my modem and router. I watched my other TV for about three hours and only got one timeout error while watching a live TV program. None of the issues mentioned when I watched programs from the DVR or while watching live TV.

My second TV is a Fire TV and only connects by Wifi, so it would seem that it would be more unstable than the one connected directly to my internet equipment. I do use Channels through both an Amazon Fire Stick and a Apple TV box on the living room TV.

Any help appreciated!

#7

Any TVE sources I try from Channels are failing to run with a "timeout" or "context deadline exceeded" message, but I can copy the stream URL from the log and open it immediately in a new tab on the browser without issue. Clients I've tested on are the latest iOS, iPadOS and TVOS plus the browser

#8

Any chance we were all on the semi-current pre-release at the time, fixed by the link, with the vague-yet-bad-sounding release notes? I was...

1 Like
#9

I'm using V2023.01.13.004.

#10

Update to Version
2023.01.14.0039

1 Like
#11

Already there…updated last night before I noticed the TVE issues.

#12

Update: in the process of troubleshooting I eventually got around to re-booting my FiOS router. After that, TVE is working again so maybe this was an issue in either my local network or with Verizon.

#13

Updated. I'll check to see if problems have gone away.

Thanks for all replies!

#14

@loucille48 Looks like we had a regression that didn't retry properly when there was a timeout.

Please try the latest pre-release and let us know if it solves your issue.

1 Like
#15

Eric,

I did update my Channels DVR. Most problems are no longer an issue. I am still getting some Playback Failure (0) errors on some channels and getting Playback Failure (-17) on several Plex channels. Is there some setting I need to change to keep these failures from occurring?

#16

Please submit diagnostics from the app so we can see what these are.

#17

Hi Eric,

I just submitted the log. The log number is: fdadcf8e-b1bb-43a2-8355-9a38f42f19a2

#18

The diagnostics look like you aren't running v2023.01.14.2318. Can you try to update one more time?

#19

I updated and I am now running 2023.01.16.0217. I'll check my TV service today and report back. Thanks for the help!

#20

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.