Connection Lost: JWT without expiration (FS1, FS2 & BIG)

Channels DVR Server TV Everywhere
#21

Yep, now rescan is not working, either.

image
image779×122 10.3 KB 

2024/01/18 08:56:34.359348 [HTTP] | 200 |      23.435ms | 2002:60fd:1d03:1:cd63:c365:9e0c:89f3 | DELETE   "/providers/tve/mvpds/Cox/cache"
2024/01/18 08:56:34.635438 [TVE] Channel scan FS1 failed: JWT without expiration
2024/01/18 08:56:34.635438 [HTTP] | 200 |    265.5738ms | 2002:60fd:1d03:1:cd63:c365:9e0c:89f3 | POST     "/providers/tve/mvpds/Cox/scan/fs1"

Channels did not capture a TVE Error Screenshot.

Should also note that it works fine at https://www.foxsports.com/live/fs1

Submitted diagnostics: f0d8e2a6-bdd6-4dcc-a1b5-5e07a8647dbf

EDIT: Only completely removing the source and re-adding it fixed the issue... at least for now.

EDIT 2: Yeah, that only lasted one day, then had to delete and re-add again.

#22

working perfectly fine. BIG ASSUMPTION on my part: but are you guys those with rediculous 43 channel server setups? because FS1 on Optimum and Verizon work fine. :person_shrugging:

2024/01/18 09:14:51.972061 [TNR] Opened connection to TVE-Cablevision for ch6197 FS1
2024/01/18 09:15:16.437053 [SNR] Rewriter statistics for 192.168.6.4 (iPad) for ch6197 FS1: discontinuity_detected=1 transport_errors=0 saw_pcr=true saw_pmt=true highest_pts=36.528144
2024/01/18 09:15:16.437883 [SNR] Buffer statistics for 192.168.6.4 (iPad) for ch6197 FS1: buf=0% drop=0%
2024/01/18 09:15:16.437918 [SNR] Streaming statistics for 192.168.6.4 (iPad) for ch6197 FS1: timeouts=0 segment_timeouts=0 playlist_timeouts=0
2024/01/18 09:15:16.438326 [TNR] Closed connection to TVE-Cablevision for ch6197 FS1
2024/01/18 09:16:14.609218 [TVE] stream timestamps: fs1: start_at=2024-01-18T09:16:21-05:00 end_at=2024-01-18T09:16:49-05:00 live_delay=15s
2024/01/18 09:16:14.609406 [TNR] Opened connection to TVE-Verizon for ch6197 FS1
2024/01/18 09:16:36.407510 [SNR] Rewriter statistics for 192.168.6.4 (iPad) for ch6197 FS1: discontinuity_detected=1 transport_errors=0 saw_pcr=true saw_pmt=true highest_pts=29.054011
2024/01/18 09:16:36.407736 [SNR] Buffer statistics for 192.168.6.4 (iPad) for ch6197 FS1: buf=0% drop=0%
2024/01/18 09:16:36.407902 [SNR] Streaming statistics for 192.168.6.4 (iPad) for ch6197 FS1: timeouts=0 segment_timeouts=0 playlist_timeouts=0
2024/01/18 09:16:36.409116 [TNR] Closed connection to TVE-Verizon for ch6197 FS1
#23

Bad Assumption I only have 1 DVR server running and no Extra IPTV but Pluto and TVE and they are not working for me. XFINITY

#24

Had the same issue recently. Had to remove my source twice to fix it. Provider is Hulu and it is a single server.

#25

It just happened again. This is the 3rd time this week and I'm tired of deleting the source.

@Maddox @Eric @tmm1

#26

This did not last, however, I re-added the source and it was fixed for a day or 2 and then it happened again. Re-scanning the individual channels does not work. Must re-add the source.

#27

Does anyone know where channels stores the JSON Web Token. I would think it's somewhere in the chromedata folder in order to persist after reboots/restarts.

Maybe try doing an update password before removing and re adding the provider source?
I'm not sure if just removing and re adding the provider source clears the chromedata folder for that provider.

#28

Thanks but I did try that. The problem happened again within two days.
I updated the password.
I re-scanned one channel to see if the error was still there. It was.
I removed and re-added the source. Fixed for two days.
Problem again.

#29

Same here, Spectrum TVE.

#31

That should clear your provider folder in the chromedata folder

That may have redownloaded the non-expiring token again

Not sure if that clears your provider folder in the chromedata folder

I'm just guessing here since I haven't run into the issue using Fubo (yet).

#32

Actually, I am using Fubo and Dish for TVE.
Both services have to fail before I know I have a problem since most are duplicate channels.
Fubo does scan and authorize much quicker :wink:

Edit: I will try what you suggest again without testing in between the nest time it fails.
Thanks!

#34

Wouldn't hurt to do an extra Update Password after re adding the source and re-scanning any failed channels. I really think it's either FOX Sports auth services are misconfigured or the way Channels is handling the token. Nobody seems to know, or for some reason won't discuss it.

#36

This latest pre-release should resolve the issue. It will require tuning into the channel more than once to clear out old cached values but should prevent it from happening again in the future.

3 Likes
"JWT without explanation"
FS1/FS2 not accesible via TVE
#37

Thank you, @eric

1 Like
#38

image
image960×223 11.9 KB

#39

Seems to be much happier, thanks! Like you said, I had a station with the JWT error and had to hit rescan twice to get it to work. On the second one, it took a LONG time (like a couple of minutes), but after that it resolved. The other stations then seemed to scan much quicker and played fine. Will keep an eye out just in case!

3 Likes
#40

Thanks!!

1 Like
#41

I just decided to test it today (haven't used any of these stations in a week) and FS1 failed. I had to go through the rescan process again to get everything back. So the solution works, but is unstable.

Submitted diagnostics: 495ca6c3-16d0-4d3f-bb7d-325f6de5a0c2

#42

It doesn't appear you ran into the JWT issue. This looks like the long-standing issue with the FS1 website where it sometimes just has javascript issues that prevent the pages from working.

#43

image
image976×232 15.1 KB