That's the point. It's automatically authenticating with the account which is providing internet.
2 Likes
It’s not the same residence. She moved out of here to her fiancé’s house.
But I think you’re onto something. We are sharing Xfinity Wifi with the tenants upstairs, who are my cousin and his family. It’s their new wifi account here at this residence now, so I bet what’s happening is it’s auto logging into THEIR account! Good grief, thanks man!
1 Like
Just to follow up, as always @tmm1 was right. I fixed this issue by creating a hotspot with my phone while using my VPN, connecting the Shield which hosts the DVR Server on it and then trying the sign in for my Xfinity TVE on my phone. It worked flawlessly!
Thanks again for the amazing support Aman and the Channels team! Sorry for being so dense. It didn’t dawn on me that this was the same issue as someone having internet only service, since the account sign on that it was based on wasn’t active at all, for TV nor internet. I should’ve realized when I tried signing onto a network’s website to authenticate a TV app not long before and got a similar message, but like I said, I’m dense! 
1 Like
That worked for me too, but honestly it's far too much effort for just a few shows. There is plenty else to watch with the TV viewing time I have.
Just noticed that I lost access to TLC- a rescan of the channel shows the "no auth token" error. I can log in and watch tv on tlc.com using the same username/password that channels is using. all the other channels seem ok.
i updated channels to 2135 and chromium (via apt) to 90.0.4430.212 -- no difference.
anyone else?
When I lost a channel, I had to delete and reinstall the TVE-Xfinity source.
I removed the source and re-added. all working fine now, including the previously broken TLC!
thanks
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?
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.
1 Like
I literally just added this back in last night. Would it error out and go away THAT fast?
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)
1 Like
OK I will try that, with much hesitation of course because Xfinity TVE is a total bear to get back in usually!
I haven't got password reset from them in quite awhile and no longer hesitate to remove/add the source.
1 Like
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
What are you running Channels DVR on?
nVidia Shield Pro 2019
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
Ha ha now you are talking Greek!
Sorry, don't use an nVidia Shield.
I would assume if you got it from here, the devs need to update your headless chrome.
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.
1 Like