Provider - Xfinity

[HarperVision]

I am now getting this error on my Channels DVR Server Logs when I try to watch NBCSports Philly and Philly+, Channels 6170 and 6171. When I tried ESPN it works fine and when I rescanned those two channels they were approved with a check mark as if I could watch them. Here are the last few log entries showing the issue:

2021/06/29 15:04:01.452402 [ERR] Could not start stream for TVE-Comcast_SSO ch6170 NBCSN-PHILLYPLUS: TVE: get http://tvetcnphiladelph.akamaized.net/hls/live/2002666/NBCSportsPhiladelphiaPluscb6ae2e9/clear/master.m3u8?hdnts=exp=1625015162~acl=/hls/live/*~hmac=4c88dcee01155fc76bb85042ca20d30f9bfd590d0794261b8a4d3667fb0d718f: 403 Forbidden
2021/06/29 15:05:51.044122 [TVE] stream timestamps: espn1: start_at=2021-06-29T15:05:12-10:00 current_at=2021-06-29T15:05:26-10:00 end_at=2021-06-29T15:05:30-10:00
2021/06/29 15:05:51.044248 [TNR] Opened connection to TVE-Comcast_SSO for ch6140 ESPN1
2021/06/29 15:05:51.051854 [HLS] Starting transcoder for channel 6140 from 192.168.1.108 (encoder=remux, resolution=, deinterlacer=, bitrate=7721)
2021/06/29 15:05:52.298876 [HLS] Probed live stream in 1.246401666s: h264 1280x720 progressive 6272000bps
2021/06/29 15:05:52.783544 [HLS] Session ch6140-dANY-ip192.168.1.108 started in 5.065803176s
2021/06/29 15:06:13.683402 [HLS] Stopping transcoder session ch6140-dANY-ip192.168.1.108 (out: 24.533333s, finished: false)
2021/06/29 15:06:13.844160 [TNR] Closed connection to TVE-Comcast_SSO for ch6140 ESPN1

The BOLDED first entry is the error, of course.

I did get a message to update Chrome when I went into the Troubleshooting tab and I tried to update it. A recording failed earlier which is what clued me into there being an issue, but the server is on an nVidia Shield Pro 2019, not on the Mac I am looking at the settings on in Safari, if that matters?

[chDVRuser]

When I get 403 Forbidden on Xfinity TVE I have to remove and re-add the source.
Been doing the remove/re-add every two weeks proactively to avoid those errors and interrupted recordings.

[HarperVision]

@chDVRuser

When I get 403 Forbidden on Xfinity TVE I have to remove and re-add the source.
Been doing the remove/re-add every two weeks proactively to avoid those errors and interrupted recordings

I literally just added this back in last night. Would it error out and go away THAT fast?

[chDVRuser]

Yep, I would try again and make sure you're running the latest DVR pre-release version..
The devs haven't given a clue as to how it works or why this happens.
I run mine on a Synology NAS and this is what I do every two weeks.
Remove Xfinity TVE source.
Stop the Channels DVR service
Start the Channels DVR service
Add the Xfinity TVE source (click and hold the last button in the sequence, forget what it's named)

[HarperVision]

OK I will try that, with much hesitation of course because Xfinity TVE is a total bear to get back in usually!

[chDVRuser]

I haven't got password reset from them in quite awhile and no longer hesitate to remove/add the source.

[HarperVision]

Any idea about fixing this failed troubleshooting step before I go traipsing all over the forum for a solution by chance?

TV Everywhere
Chrome version is out of date: HeadlessChrome/81.0.4044.113
FIX: Upgrade Chrome

[chDVRuser]

What are you running Channels DVR on?

[HarperVision]

nVidia Shield Pro 2019

[chDVRuser]

Got me there. Would assume you need to update the headless Chrome on it, but have no idea how to do it.
Think you need minimum version 89

[HarperVision]

Ha ha now you are talking Greek!

[chDVRuser]

Sorry, don't use an nVidia Shield.
I would assume if you got it from here, the devs need to update your headless chrome.

[tmm1]

Clicking the FIX button on the troubleshooting page will upgrade chrome.

Removing/readd of TVE is not necessary. The issue with discovery stopping working can be resolved by removing the chromedata folder which holds all the cookies.

I'm not sure about NBCSN 403. The only time I have seen that is when VPN is being used and the connection is not coming from residential US IP.

[keno-h]

Remove the whole folder or just the files? I didn’t realize this. And sorry, I have two accounts on here for two locations, so I get myself confused on which account I’m responding on (one is remote management)

[HarperVision]

@chDVRuser

I run mine on a Synology NAS and this is what I do every two weeks.
Remove Xfinity TVE source.
Stop the Channels DVR service
Start the Channels DVR service
Add the Xfinity TVE source (click and hold the last button in the sequence, forget what it's named)

OK I tried these steps and they didn’t work. Still can get a channel like ESPN but can’t get NBCSports Philly/Philly+ and get the previously posted error 403.

[HarperVision]

@tmm1

Clicking the FIX button on the troubleshooting page will upgrade chrome.

Removing/readd of TVE is not necessary. The issue with discovery stopping working can be resolved by removing the chromedata folder which holds all the cookies.

I'm not sure about NBCSN 403. The only time I have seen that is when VPN is being used and the connection is not coming from residential US IP.

I clicked fix several times and it would just spin and then stop. Then I would try the Troubleshooter again and it would still report Chrome out of date.

I’ll have to see if Discovery also doesn’t come in and/or gives me that same 403 error.

I’m not using a VPN, but I am far away from the area where the authenticated TVE source is. I am using my parents Xfinity account near Philly in which I am the main account contact because I take care of it for them because they’re too old to understand all this stuff.

I’m in Hawaii so could it be detecting that I’m outside the area, aka “Out of Home” and giving me that error? It never did before.

My IP should still show as a US address I’d think.

[HarperVision]

OK, I am not sure what happened or if you ( @tmm1 ) did anything on your end, but it is working now. Maybe when I logged into Xfinity on my Mac to see if it worked there, as requested, that kicked something on, idk?

I guess we will see how long this lasts.

[chDVRuser]

@tmm1

Removing/readd of TVE is not necessary. The issue with discovery stopping working can be resolved by removing the chromedata folder which holds all the cookies.

Does anything need to be done after deleting the chromedata directory?
Like tuning to a channel or rescanning all or individual channels?
I'm trying to avoid errors that happen every couple of weeks with scheduled recordings, mainly DIY channel.

Thanks for the tip!

The last error I fixed by removing/adding the TVE source was TLC getting a 403 error.

TLC Channel 6105 error 403 Forbidden

Anyone else seeing this on TLC? I re-added my Xfinity-TVE yesterday and this is the only stubborn channel that a rescan wont fix. I've probably rescanned it 10 times since yesterday. Had the same error with Travel-6106 yesterday, but after 5-6 rescans it came back. Running DVR v2021.06.13.0323 (latest prerelease) Logs have been submitted as ab55b75e-a807-43f0-b9a4-989d5dcbe218

I just now deleted the chromedata folder after stopping the Channels DVR docker container.
I then tuned to DIY, which worked and there's nothing in the log about authenticating.

Will the chromedata folder get recreated at some point and I'll have to do this again?

[chDVRuser]

@chDVRuser

Will the chromedata folder get recreated at some point and I'll have to do this again?

The folder was recreated after re-authing all the Discovery Network channels a few minutes ago.

Discovery networks stop tuning

I just tried DIY and am getting errors. action=discovery_refresh data={"code":410,"message":"Gone","description":"User authentication has expired (invalidating session)"} action=version product=Chrome/89.0.4389.72 jsVersion=8.9.255.20 protocol=1.3 revision=@3f345f156bfd157bd1bea06310e55f3fb2490359 Failed to start stream for ch6108: TVE: chrome failed to start: [789:807:0711/180340.692578:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket…

Should I delete it again or wait for a recording to fail first?

[chDVRuser]

Trying to understand this thing about the chromedata folder.

It appears Channels DVR creates it when it needs to authorize some channels.
I tested this by authorizing the channels I watch or record, then deleted the chromedata folder.
I then tuned to a channel I never watch and in the process of authorizing the channel it created the chromedata folder again.

If the folder contents (cookies?) hang around until that channel needs re-authed again, it causes problems.

Is this correct?