NFL Network "Cable provider authentication failed" December 2022

[Eric_P75]

v2022.12.26.1705 fixed my issues with YouTube TV as well!

[David_Smit]

One thing I've noticed, is when trying to auth using YTTV, I'm still getting the "no login form found" message.

However, before I scan the channels, TVE says chrome version is good.

After I scan, It says its out of date, this is repeatable.

ae2a8870-c1ac-4b3b-a69c-807b3bb93d5f

[chDVRuser]

You might want to add to this thread (no acknowledgment from the devs yet)

Headless chrome constantly out of date?

I’m just curious about how often headless chrome gets updated. I’ve been checking the troubleshooting tab on an almost daily basis, and every time I check it shows up as out of date. I tell it to update and it does but then a day later it shows as out of date again. Is headless chrome really being updated for raspberry pi that often? I’ve got channels on a raspberry pi running raspberry pi os. I update my raspberry pi weekly so it’s not like I’m letting the OS get out of date. It just seems like…

[WillParman]

Fixed for me on Hulu.

[ericsmcdonald]

2022.12.26.1705 Fixed for both spectrum and YouTube tv. Thanks!

[B0bHalter]

NFL Channel working with 2022.12.28.0400 for Spectrum on Mac OSX Monterey

[rcgfl]

@B0bHalter

NFL Channel working with 2022.12.28.0400 for Spectrum on Mac OSX Monterey

Can confirm the same for Hotwire (same build and OS as well).

[teladog01]

Still not working here with Hulu.

Whenever I do a rescan of NFL Network, I get a one-time verification code emailed to me from Hulu. Am I supposed to be able to enter this somewhere?

Version 2022.12.28.2233

Diagnostics d03f209e-7e12-475c-a4f1-fdcc2f6c40b8

[chDVRuser]

Did you try this?

@kprice

I was able to Hulu to add back as source by deleting the device from Hulu - then it added back fine -

@Jrb2153

I got the damn thing to work. I went into Hulu website and deleted all the web devices on my account. I changed the password on Hulu and now it works.

[teladog01]

Yes, I've done that procedure several times over the past several days (delete "TV Everywhere" device in Hulu account, then delete and re-add source in Channels). NFL Network always failed. But...

Just tried it again and now NFL Network scans successfully when re-adding the source in Channels. This was the first time I tried using the 2022.12.28.2233 pre-release.

[B0bHalter]

Looks like this problem with NFL Network is back again. Running Channels (version 2023.04.04.2041 ) on 2012 mac mini (MacOS Monterey 12.6.4) with Spectrum TVE. Rescanned NFL Network and it passed the rescan, but still not viewable. Works fine when accessed through NFL.com.
Log:

2023/04/05 12:32:06.135278 [TNR] Opened connection to TVE-Spectrum for ch6192 NFL
2023/04/05 12:32:06.142611 [HLS] Starting live stream for channel 6192 from x.x.x.x (bitrate=3200)
2023/04/05 12:32:07.131200 [HLS] ffmpeg: ch6192-dANY-ipx.x.x.x-remux:  Output file #0 does not contain any stream
2023/04/05 12:32:07.213712 [HLS] Couldn't generate stream playlist for ch6192-dANY-ipx.x.x.x: Stream stopped
2023/04/05 12:32:07.213799 [HLS] Stopping transcoder session ch6192-dANY-ipx.x.x.x
2023/04/05 12:32:07.215113 [TNR] Closed connection to TVE-Spectrum for ch6192 NFL
2023/04/05 12:32:07.215180 [ERR] Probe failed for live stream after 1.070186189s and 0 bytes
2023/04/05 12:32:07.975786 [TNR] Opened connection to TVE-Spectrum for ch6192 NFL
2023/04/05 12:32:07.982251 [HLS] Starting live stream for channel 6192 from 10.0.0.103 (bitrate=3200)
2023/04/05 12:32:08.962809 [HLS] ffmpeg: ch6192-dANY-ipx.x.x.x-remux:  Output file #0 does not contain any stream
2023/04/05 12:32:09.003657 [HLS] Couldn't generate stream playlist for ch6192-dANY-ipx.x.x.x: Stream stopped
2023/04/05 12:32:09.003725 [HLS] Stopping transcoder session ch6192-dANY-ipx.x.x.x
2023/04/05 12:32:09.004917 [TNR] Closed connection to TVE-Spectrum for ch6192 NFL
2023/04/05 12:32:09.004993 [ERR] Probe failed for live stream after 1.019805593s and 0 bytes
2023/04/05 12:32:10.123853 [TNR] Opened connection to TVE-Spectrum for ch6192 NFL
2023/04/05 12:32:10.131439 [HLS] Starting live stream for channel 6192 from x.x.x.x (bitrate=3200)
2023/04/05 12:32:11.053710 [HLS] ffmpeg: ch6192-dANY-ipx.x.x.x-remux:  Output file #0 does not contain any stream
2023/04/05 12:32:11.083473 [HLS] Couldn't generate stream playlist for ch6192-dANY-ipx.x.x.x: Stream stopped
2023/04/05 12:32:11.083570 [HLS] Stopping transcoder session ch6192-dANY-ipx.x.x.x
2023/04/05 12:32:11.084676 [TNR] Closed connection to TVE-Spectrum for ch6192 NFL
2023/04/05 12:32:11.084777 [ERR] Probe failed for live stream after 951.08836ms and 0 bytes
2023/04/05 12:32:12.132936 [TNR] Opened connection to TVE-Spectrum for ch6192 NFL
2023/04/05 12:32:12.139939 [HLS] Starting live stream for channel 6192 from x.x.x.x (bitrate=3200)
2023/04/05 12:32:12.743054 [HLS] ffmpeg: ch6192-dANY-ipx.x.x.x-remux:  Output file #0 does not contain any stream
2023/04/05 12:32:12.803770 [HLS] Couldn't generate stream playlist for ch6192-dANY-ipx.x.x.x: Stream stopped
2023/04/05 12:32:12.803867 [HLS] Stopping transcoder session ch6192-dANY-ipx.x.x.x
2023/04/05 12:32:12.805065 [TNR] Closed connection to TVE-Spectrum for ch6192 NFL
2023/04/05 12:32:12.805154 [ERR] Probe failed for live stream after 662.116585ms and 0 bytes

[KE3JU]

I'm glad I'm not the only one, I was hesitant to post because no one else has yet either. Spectrum TVE also. I see Connection Lost (-17) on the screen. Log segment below.

2023/04/05 14:06:22.024125 [TNR] Error during live stream for ch6192 NFL: Failed to download segment 14: https://o300801-mp-lura-live.fsy.nfl.com/live/ephemeral/54AVmb0klx0KCyCYkFbJwmEle6YKX2NE/nfln-la3/3296k/eB29azo3UTr/171499/segment_171499022.ts?token=1680721566_f2b135f78a756eb3240cadf6de5a9f458c1f415c: Unknown encryption method: SAMPLE-AES
2023/04/05 14:06:22.024246 [SNR] Buffer statistics for 10.110.17.131 (Ed's Galaxy Note 9) for ch6192 NFL: buf=0% drop=0%
2023/04/05 14:06:22.041567 [HTTP] | 200 |   10.173577ms |   10.110.17.100 | GET      "/log"
2023/04/05 14:06:22.042514 [HTTP] | 404 |     340.431µs |   10.110.17.131 | GET      "/devices/TVE-Spectrum/status/0-3/debug"
2023/04/05 14:06:22.050701 [TNR] Closed connection to TVE-Spectrum for ch6192 NFL
2023/04/05 14:06:22.050708 [HTTP] | 200 |  4.657760043s |   10.110.17.131 | GET      "/devices/TVE-Spectrum/channels/6192/stream.mpg"

[tmm1]

Unfortunately it looks like they've added DRM so we will no longer be able to support it.

[babsonnexus]

@tmm1

Unfortunately it looks like they've added DRM so we will no longer be able to support it.

Is this happening with a lot of TVE right now? I saw these other threads, too:

NBC Sports RSNs: Stream Not Available

The new nbc.com/live streams are not compatible unfortunately. It is not likely that these could be readded, unless they old stream website starts working again.

@tmm1

No, it looks like they're in the middle of changing their streaming platform. We may lose access to all the stations on that website if they decide to switch over completely.

Are you seeing a cascade of these things going down?

[themediaguy]

@babsonnexus

Are you seeing a cascade of these things going down?

I would be asking the same question?

[tmm1]

We are posting what we see here in real-time, so you're seeing exactly what we see.

NFL has been experimenting with changes for months.

Sports channels have always been the ones most likely to use DRM

[babsonnexus]

@miibeez, can your VLC Bridge Solution also work for NFL Network and the NBC stations?

[rpaulmerrell]

will definitly be watcing.

[babsonnexus]

I now have NFL Network back with this workaround:

BETA: PC Stream for Channels (DRM Workaround) | No new hardware required!

Inspired by the HDMI for Channels project, this solution attempts to do the same thing. Namely, this project allows the user to stream any station, including ones protected by DRM, in Channels--so long as there is a web source to get the content from that the user has legal access to. However, this solution focuses on doing so without using a separate (expensive) HDMI capture device and setup, eliminating multiple potential physical hardware fail points, and using an existing always-on Channels …