I had forgotten how to pull up the screen shot of the TVE error the server makes... found the url to do that.
It shows the login page, and the password field, with nothing filled in. And my user name is above (covered that up in image). This is what it shows for trying to tune Disney channel.
Have you logged on to XFINITY.COM using the acct used on TVE ? to make sure there is nothing wrong with it like asking for 2FA.
Yup works fine on the networks sites. And it is also the same login info / account used on other server.
I read through this whole thread 1 thing is common is WINDOWS 11. my final suggestion turn off Firewall and disable windows defender ? Rescan ...
I know there was a problem running Chrome on Windows 11... at one time Windows 11 was completely blocking Chrome.
3 Ways to Fix Chrome Not Opening on Windows 11 (guidingtech.com)
That’s ridiculous. Nothing has been blocked. Chrome opens and works fine. I can even login into the network website directly on the Windows 11 server machine. And according to the tve error screenshot it’s loading the login page entering the username fine, but it gets hung up with the password screen. it seems to be an issue with Channels scripts or whatever it does logging into Xfinity
Hard to tell from just the error screenshot alone. I'm sure the devs have what they need from your diagnostic log submissions.
It could be entering the wrong username and Xfinity won't complain until after the password is entered. For security reasons it won't tip you off to which one is incorrect.
When I was still using Xfinity TVE recently I had an error screenshot showing [email protected], but I only ever used username. Where can I see my TVE account credentials in Channels? - #11 by chDVRuser
Could have been Channels DVR or the Xfinity auth system doing that. Never found out which one it was and I no longer use Xfinity TVE.
I think the only thing Edwin_Perez is doing different is that he's clearing the chromedata folder before forcing reauths for any expired channel tokens every day. You could do the same by using using the Update Password on your source and then rescanning channels.
Tried that. Did update password, and no Xfinity channels will authorize now. Cable provider authentication failed. Same errors in logs as when i tried to tune a channel.
thre was a pre-release that came out last night. Fixed it for me.
You are referring to 2024.07.27.2008.
I installed this version, it only resolved the parse error in logs.
Did not resolve issue of not being able to authenticate Xfinity TVE channels. for me.
Mine just worked this morning too. Strange that it didn't when I updated to 2024.07.27.2008 last night but this morning it worked. Not sure what I did to make it work.
I get all this trying to authorize any Xfinity channel.
2024/07/28 05:47:01.054740 [TVE] action=auth mvpd=Comcast_SSO requestor=dtci
2024/07/28 05:47:01.281793 [TVE] action=version product=Chrome/127.0.6533.73 jsVersion=12.7.224.16 protocol=1.3 revision=@b59f345ebd6c6bd0b5eb2a715334e912b514773d
2024/07/28 05:47:01.282299 [TVE] action=page_ready chromeVersion=127
2024/07/28 05:47:01.282820 [TVE] action=navigate url=https://sp.auth.adobe.com/adobe-services/authenticate/saml?noflash=true&mso_id=Comcast_SSO&requestor_id=dtci&no_iframe=true&domain_name=adobe.com&redirect_url=https%3A%2F%2Fsp.auth.adobe.com%2Fadobe-services%2FcompletePassiveAuthentication
2024/07/28 05:47:01.284947 [TVE] action=request type=Document method=GET url=https://sp.auth.adobe.com/adobe-services/authenticate/saml
2024/07/28 05:47:01.469573 [TVE] action=request type=Document method=GET url=https://oauth.xfinity.com/oauth/authorize redirected_from=https://sp.auth.adobe.com/adobe-services/authenticate/saml
2024/07/28 05:47:01.872889 [TVE] action=request type=Document method=GET url=https://login.xfinity.com/login redirected_from=https://oauth.xfinity.com/oauth/authorize
2024/07/28 05:47:01.872889 [TVE] action=auth_domain domain=login.xfinity.com
2024/07/28 05:47:02.147221 [TVE] action=wait_for_page
2024/07/28 05:47:02.744413 [TVE] action=error_response type=Stylesheet error=net::ERR_BLOCKED_BY_ORB url=https://content.xfinity.com/securelogin/cima ip=***********
2024/07/28 05:47:32.158184 [TVE] action=wait_for_page err=timeout
2024/07/28 05:47:32.756316 [TVE] action=wait_for_auth timeout=24s
2024/07/28 05:47:32.756316 [TVE] action=fill_form u=***********
2024/07/28 05:47:32.760653 [TVE] action=tvejs msg="xfinityLogin: cookie"
2024/07/28 05:47:33.032093 [TVE] action=error_response type=Script error=net::ERR_TIMED_OUT url=https://polaris.xfinity.com/globalnav/polaris.wc.js ip=*************
2024/07/28 05:47:33.767227 [TVE] action=tvejs msg="xfinityLogin: wait"
2024/07/28 05:47:33.767227 [TVE] action=retry_form
2024/07/28 05:47:33.973505 [TVE] action=request type=Document method=POST url=https://login.xfinity.com/login
2024/07/28 05:47:34.519212 [TVE] action=error_response type=Stylesheet error=net::ERR_BLOCKED_BY_ORB url=https://content.xfinity.com/securelogin/cima ip=***********
2024/07/28 05:47:56.757596 [TVE] action=check_result
2024/07/28 05:47:56.776315 [TVE] action=auth_timed_out
2024/07/28 05:47:56.776315 [TVE] action=screenshot
2024/07/28 05:47:56.801756 [TVE] action=error_response type=XHR error=net::ERR_ABORTED url=https://dl.cws.xfinity.com/event/ ip=*******
2024/07/28 05:47:56.801756 [TVE] action=error_response type=XHR error=net::ERR_ABORTED url=https://dl.cws.xfinity.com/event/ ip=*******
2024/07/28 05:47:56.801756 [TVE] action=error_response type=XHR error=net::ERR_ABORTED url=https://dl.cws.xfinity.com/event/ ip=*******
2024/07/28 05:47:56.802319 [TVE] action=error_response type=XHR error=net::ERR_ABORTED url=https://dl.cws.xfinity.com/event/ ip=*******
2024/07/28 05:47:56.802399 [TVE] action=error_response type=XHR error=net::ERR_ABORTED url=https://dl.cws.xfinity.com/event/ ip=*******
2024/07/28 05:47:56.802399 [TVE] action=error_response type=XHR error=net::ERR_ABORTED url=https://dl.cws.xfinity.com/event/ ip=*******
2024/07/28 05:47:56.802399 [TVE] action=error_response type=XHR error=net::ERR_ABORTED url=https://dl.cws.xfinity.com/event/ ip=*******
2024/07/28 05:47:56.802399 [TVE] action=error_response type=XHR error=net::ERR_ABORTED url=https://dl.cws.xfinity.com/event/ ip=*******
2024/07/28 05:47:56.802399 [TVE] action=error_response type=XHR error=net::ERR_ABORTED url=https://dl.cws.xfinity.com/event/ ip=*******
2024/07/28 05:47:56.803045 [TVE] action=error_response type=XHR error=net::ERR_ABORTED url=https://dl.cws.xfinity.com/event/ ip=*******
2024/07/28 05:47:56.803045 [TVE] action=error_response type=XHR error=net::ERR_ABORTED url=https://dl.cws.xfinity.com/event/ ip=*******
2024/07/28 05:47:56.803045 [TVE] action=error_response type=Script error=net::ERR_ABORTED url=https://polaris.xfinity.com/globalnav/polaris.wc.js ip=*******
2024/07/28 05:47:56.894323 [TVE] action=screenshot size=209773
2024/07/28 05:47:56.894323 [TVE] action=capture_html
2024/07/28 05:47:56.898851 [TVE] action=capture_html size=235284
2024/07/28 05:47:56.955386 [TVE] Channel scan NGWILD failed: Cable provider authentication failed
Might be the Xfinity auth servers are taking too long to respond.
I noticed it took a long time to login this morning when I went to get my monthly statement.
I Installed server v2024.07.27.2008
It fixed my parse error and I can now login into Xfinity
My other Linux based server, is now giving "could not fetch playlist... 403 forbidden"
EDIT: So that 403 error is only happening for channel 6037 TruTV.
All other Xfinity channels i have enabled on that sever (7 others) are loading fine.
Still getting nothing with my main Win 11 server..
I just spun up a Win 10 VM, and installed CDVR and chrome. Same issues. Xfinity will not auth.
No such lag loading for me of any of Xfinity's pages, account, billing, or even Xfinity Stream etc.
Just logged into them via Chrome on 2 other computers fine.
Perhaps, I should start a new thread? Since my issue of Xfinity not Authing does not seem to be related to this threads "cookie pop up" issue.
I started seeing the "could not unmarshal event" error sporadically on Monday but am now seeing it on pretty much every TVE channel I've tried. My Channels DVR Server is on Windows 10 Pro.
I don't know if my problems are related (I'm hosting CDVR on Win 10 Pro), but I haven't been able to get anything to work on Xfinity TVE for at least two days now. One of the errors said it couldn't start Chrome, but when I remoted into the CDVR Server's host PC Chrome opened up just fine, and I'm not seeing that error currently. The most prominent error in my log is "...could not unmarshal event: parse error: expected string near offset...".
Have you updated your server to the latest pre-release as that fixes the parse errors.
Well, it says I'm up-to-date at 2024.07.18.0352, but that seems too long ago to be the latest pre-release.