Just tried that; spinning circle
I just updated to prerelease version 2022.01.16.0341 and now I can add the Xfinity provider successfully once again.
Nothing worked for me until I uninstalled the service (Windows), deleted Channels, made sure the \ProgramData\ChannelsDVR folder was empty, reinstalled the server, imported the database and then added Xfinity TVE as a source. Bottom line, there must be something there keeping old user/password data, and that prevents Channels from logging into Xfinity. When I got a screenshot after the ERR_CONNECTION_REFUSED and "context deadline exceeded", the username in the screenshot showed a username I no longer use.
Start using incognito when you manage the Xfinity source
Update: Reinstalled ChannelsDVR and emptied Chrome cache and cookies and it seems like everything is working; can view live and make recordings. So..... 'SOLVED'.
My CBS affiliate is now available in the 6000 range. Hopefully, this will bode well for the rest of the Viacom channels. BTW, the stats show that CBS provides a 1080p/60fps stream!
@tmm1
Based on gt2982a comment above, I checked CBS.com and I have access to live TV now too. I rescanned my Xfinity credentials and I have two stations, WUSA and WSVF but only WUSA gets added. WSVF says "stream-info failure" with I rescan it. When I go to CBS.com it asks me to pick which one I want to view and I have tested I can see either. However, my real local CBS is the WSVF station I can't get. I guess my location is on the fringe of both. Can the WSVF channel be added?
Thanks,
Chuck
Please email support with screenshot of what you see on cbs. I didn't realize they offered an option if you're in between markets
1 Like
Just sent the email to support. Thanks!
I am having this exact same issue since yesterday.
Logs have been submitted as ab2ca6d0-e5ff-4812-a3f6-29954036414e
Anyone else having trouble adding Xfinity as a TVE source? The verification step fails and the log shows an issue with attempting to authenticate. I verified my password works using nbc.com/live and I am using a Xfinity subaccount. I also verified that xfinity.com/stream works as well. I am using the latest chrome on the DVR server (Windows 10).
Here is the log entry showing the authentication error:
2022/01/24 10:01:35.450911 [TVE] Auth starting for Comcast_SSO as abrahamjerry
2022/01/24 10:01:35.450911 [TVE] action=auth mvpd=Comcast_SSO requestor=nbcentertainment
2022/01/24 10:01:35.703975 [TVE] action=version product=HeadlessChrome/97.0.4692.99 jsVersion=9.7.106.19 protocol=1.3 revision=@d740da257583289dbebd2eb37e8668928fac5ead
2022/01/24 10:01:35.706237 [TVE] action=mock
2022/01/24 10:01:35.712385 [TVE] action=navigate url=https://sp.auth.adobe.com/adobe-services/authenticate/saml?noflash=true&mso_id=Comcast_SSO&requestor_id=nbcentertainment&no_iframe=true&domain_name=adobe.com&redirect_url=https%3A%2F%2Fsp.auth.adobe.com%2Fadobe-services%2FcompletePassiveAuthentication
2022/01/24 10:01:35.713646 [TVE] action=request type=Document method=GET url=https://sp.auth.adobe.com/adobe-services/authenticate/saml
2022/01/24 10:01:38.525251 [TVE] action=request type=Document method=GET url=https://oauth.xfinity.com/oauth/authorize
2022/01/24 10:01:39.057945 [TVE] action=request type=Document method=GET url=https://login.xfinity.com/login
2022/01/24 10:01:39.058061 [TVE] action=auth_domain domain=login.xfinity.com
2022/01/24 10:01:39.332701 [TVE] action=wait_for_page
2022/01/24 10:01:39.678819 [TVE] action=exception err=&runtime.ExceptionDetails{ExceptionID:1, Text:"Uncaught", LineNumber:371, ColumnNumber:38, ScriptID:"249", URL:"https://login.xfinity.com/static/js/vm-login-form-ad.js", StackTrace:(*runtime.StackTrace)(0xc000c2e540), Exception:(*runtime.RemoteObject)(0xc000d223f0), ExecutionContextID:2, ExceptionMetaData:easyjson.RawMessage(nil)} value=TypeError: Cannot read properties of null (reading 'appendChild')
at buildIFrame (https://login.xfinity.com/static/js/vm-login-form-ad.js:372:39)
at decideMobileOrWeb (https://login.xfinity.com/static/js/vm-login-form-ad.js:257:4)
at Object.init (https://login.xfinity.com/static/js/vm-login-form-ad.js:11:3)
at Sign in to Xfinity
After this, the DVR server reattempts to authenticate until it eventually times out. I would expect if there was a wrong password that the first attempt would return an error instead of timing out.
1 Like
Yes I have been having this issue since yesterday.
1 Like
v2022.01.25.0055 build appears to be working for me!
Edit: got this working on like the 15th try somehow. Who knows. 
Original text:
It had been working great since 12/21. I was forced to change my password today. Authorized a few [devices with the new password, but Channels is stuck at "Cable provider authentication failed":
I've tried:
- updating from 2022.01.13.2139 to 2022.01.25.0145
Update Password- removing/re-adding the TV Everywhere source
- copying and pasting the password
- rebooting
all with no luck. Logs don't show much, but they've been submitted as 973e98d5-a8b7-4337-b02d-1298075e99b0. Any ideas?
2022/01/25 20:16:22.903796 [TVE] action=page_ready
2022/01/25 20:16:22.903796 [TVE] action=retry_form step=auth_form count=3
2022/01/25 20:16:23.842415 [TVE] action=fill_form u=MYUSERNAMELOL
2022/01/25 20:16:23.845349 [TVE] action=tvejs msg="xfinityLogin: wait"
2022/01/25 20:16:23.845349 [TVE] action=retry_form
2022/01/25 20:16:24.153166 [TVE] action=wait_for_auth
2022/01/25 20:16:24.166197 [TVE] action=request type=Document method=POST url=https://login.xfinity.com/login
2022/01/25 20:16:30.430134 [TVE] action=page_ready
2022/01/25 20:16:30.430134 [TVE] action=retry_form_failed
2022/01/25 20:16:30.430134 [TVE] action=screenshot
2022/01/25 20:16:30.591803 [TVE] action=screenshot size=35643
2022/01/25 20:16:30.601829 [TVE] action=capture_html
2022/01/25 20:16:30.607882 [TVE] action=capture_html size=42950
2022/01/25 20:16:30.715168 [TVE] action=screenshot
2022/01/25 20:16:30.881037 [TVE] action=screenshot size=35643
2022/01/25 20:16:30.891027 [TVE] action=capture_html
2022/01/25 20:16:30.897048 [TVE] action=capture_html size=42950
2022/01/25 20:16:30.998314 [TVE] action=screenshot
2022/01/25 20:16:31.163021 [TVE] action=screenshot size=35643
2022/01/25 20:16:31.173085 [TVE] action=capture_html
2022/01/25 20:16:31.179100 [TVE] action=capture_html size=42950
2022/01/25 20:16:31.285191 [TVE] action=screenshot
2022/01/25 20:16:31.451639 [TVE] action=screenshot size=35643
2022/01/25 20:16:31.461698 [TVE] action=capture_html
2022/01/25 20:16:31.466714 [TVE] action=capture_html size=42950
2022/01/25 20:16:31.637128 [TVE] Auth failed for Comcast_SSO: Cable provider authentication failed
So I lost access to discovery channels today. Getting a 403 error. I tried to update to the latest pre release. I can still stream other non discovery channels (oxygen and tnt for example). Trying to remember what else I need to try to get it working again. I added password and and tried to rescan. I checked the id with xfinity stream and go.discovery.com works as well.
I either just lucked out or going to incognito was the trick to get the rescan to work. I was able to get the channels back. Discovery has been solid for several months and our most watched channels.
Always use incognito when managing Xfinity as a source, especially if login sharing. What I've been doing short of removing / readding is using the change password, putting in the original password to clear the chromedata folder, then initiating a full channel scan.
1 Like
Rather than wade through posts to find fixes, I added a pinned topic with a list of TVE troubleshooting tips here TVE Troubleshooting tips
Let me know if I missed anything and I'll add it.
2 Likes
@chDVRuser curious if you’ve dealt with the following. I’m getting not in subscription for TNT TBS. I’m on the current stable release from earlier this week. I tried the password step from an ingconito crome browser. I’ve gone to tntdrama to try it directly. It looks like there is an auth issue between xfinity and tnt. When I try to link my account it doesn’t ask me for my id just says this network is not included and gives a upgrade now. If I follow that link and use the secondary id, I can go back and get tntdrama.com to work as the id has the sub. My hope was that I could then go back to the server and rescan and hope it would self heal which it didn’t. So is this a case where even though I have the subscription that I’m at the mercy of xfinity and tnt on how they are handling the handshake. The discovery channels that I care about the most are working (thus have not taken the step to remove and add the source) so my assumption is the id I have set is correct on the server even though I can’t tell from the logs what it is using.
Sounds like you're trying to use two different Xfinity account id's (names).
Just use a secondary viewer only account for Channels DVR.
Not sure what you mean?
Sounds like you need to turn off auto-authentication on the main Xfinity account