Thanks, I'm aware of that. But only used TVE to get the channels in HD that my HDHR cablecard gets in SD. Not a priority, so not worth getting more HDHR tuners, as I don't need more tuners. I killed TVE and haven't missed it. Especially with the interrupted and missed recordings and having to jump through hoops to re-record them with Channels DVR.
Sorry to tack on to the CableCARD derailing - what's the trick to get cards for cheap from Xfinity? I used to get them for $0-1.50-2.50 per card per month, and am still willing to pay that much, but now they want $7.50-10.00/card/month, so now I have 4 HDHR PRIMEs just wasting away unfortunately. TV Everywhere worked pretty well for me until NBC (NBC Sports Bay Area) stopped support, Chrome Capture for Channels is mediocre and NBC's web feed is 30fps and low-bitrate anyways. I miss having good, reliable access.
My XFINITY Cable cards are free .... TVE Recordings have been flawless no Interrupted recordings.
1 Like
Rescan this morning working again.
Hallmark Channels not working ....
2024/08/10 07:18:00.515308 [TVE] action=error_response type=Stylesheet error=net::ERR_BLOCKED_BY_ORB url=https://content.xfinity.com/securelogin/cima ip=23.56.125.247
2024/08/10 07:18:01.289814 [TVE] action=error_response type=XHR error=net::ERR_FAILED url=https://dl.cws.xfinity.com/event/ ip=23.59.198.240
2024/08/10 07:18:01.290384 [TVE] action=error_response type=XHR error=net::ERR_FAILED url=https://dl.cws.xfinity.com/event/ ip=23.59.198.240
2024/08/10 07:18:01.290949 [TVE] action=error_response type=XHR error=net::ERR_FAILED url=https://dl.cws.xfinity.com/event/ ip=23.59.198.240
2024/08/10 07:18:01.539194 [TVE] action=error_response type=XHR error=net::ERR_FAILED url=https://dl.cws.xfinity.com/event/ ip=23.59.198.240
2024/08/10 07:18:01.539666 [TVE] action=error_response type=XHR error=net::ERR_FAILED url=https://dl.cws.xfinity.com/event/ ip=23.59.198.240
2024/08/10 07:18:01.540263 [TVE] action=error_response type=XHR error=net::ERR_FAILED url=https://dl.cws.xfinity.com/event/ ip=23.59.198.240
2024/08/10 07:18:01.540263 [TVE] action=error_response type=XHR error=net::ERR_FAILED url=https://dl.cws.xfinity.com/event/ ip=23.59.198.240
2024/08/10 07:18:01.540795 [TVE] action=error_response type=XHR error=net::ERR_FAILED url=https://dl.cws.xfinity.com/event/ ip=23.59.198.240
2024/08/10 07:18:01.573935 [TVE] action=error_response type=XHR error=net::ERR_FAILED url=https://dl.cws.xfinity.com/event/ ip=23.59.198.240
2024/08/10 07:18:01.574504 [TVE] action=error_response type=XHR error=net::ERR_FAILED url=https://dl.cws.xfinity.com/event/ ip=23.59.198.240
2024/08/10 07:18:01.575036 [TVE] action=error_response type=XHR error=net::ERR_FAILED url=https://dl.cws.xfinity.com/event/ ip=23.59.198.240
2024/08/10 07:18:01.575036 [TVE] action=error_response type=XHR error=net::ERR_FAILED url=https://dl.cws.xfinity.com/event/ ip=23.59.198.240
This is so weird ... my Windows TVE succesfully authorizes 150 Channels ... they all work.
2024/08/29 06:10:23.405537 [TVE] Channel scan finished after 5m16s: 150/159 channels available
My linux TVE only authorizes 129 Channels
2024/08/29 08:04:16.131838 [TVE] Channel scan finished after 20m0s: 129/159 channels available
So I am dumping my Linux Channels DVR server. RIP ... This has been consistent ... I have been monitoring for a while.
1 Like
I see you figured those out.
These are mentioned in the first post of this topic Provider - Xfinity
and in the TVE Troubleshooting Tips TVE Troubleshooting tips - #6 by chDVRuser
1 Like
I think the chromium dependency being pulled in is borked - was having nothing but issues attempting to log into Comcast TVE, went through all of the steps, did a clean install on a new VM but kept running into the same issues.
Attempted on a Windows host out of desperation and it worked after installing Chrome. Did the same thing on the Ubuntu VM and boom - now able to pull in channels.
Please review this in your integration testing... not something I want to deal with as an end-user
Can confirm updating chromium fixes this issue. restart server after update.
Another Xfinity failure....
I'm running Channels on a Raspberry Pi 4. It had been working fine with Xfinity for several months but recently started to fail, unable to record any channels at all. I did all the troubleshooting, removed the old Source, added subsidiary account, changed paswords, and tried several times to add the Xfinity back in as a Source. Now it can't do even that.
I'm wondering if the problem is that I need a new version of Chromium. I'm running the standard "Pi image" downloaded from getchannels.com. I tried running the latest pre-release but it gets same behavior.
Does anyone know if that Pi image includes the appropriate version of Chromium? If not, can I update it somehow? My Pi is setup as a headless server.
FYI, log from server attempt to add Xfinity as a new Source is below. It looks like it tries twice but is getting some fatal error trying to fill in some form, causing an uncaught exception. There's also a report of a stylesheet error.
I submitted logs and emailed with Support but they haven't "gotten to the bottom of it" yet either. Apparently it's happening on both Pi and NAS installations, which is what made me suspect the possibility of Chromium in the downloaded images for those machines.
Any ideas?
Jack
===============
Log from my server of attempt to add Xfinity as source:
2024/10/12 16:51:44.787716 [TVE] Auth starting for Comcast_SSO as gh95959
2024/10/12 16:51:54.685460 [TVE] action=auth mvpd=Comcast_SSO requestor=HGTV
2024/10/12 16:51:56.748355 [TVE] action=version product=Chrome/117.0.5938.62 jsVersion=11.7.439.16 protocol=1.3 revision=@25a7172909a4cba7355365cf424d7d7eb35231f4
2024/10/12 16:51:56.750795 [TVE] action=page_ready chromeVersion=117
2024/10/12 16:51:56.806274 [TVE] action=navigate url=https://sp.auth.adobe.com/adobe-services/authenticate/saml?noflash=true&mso_id=Comcast_SSO&requestor_id=HGTV&no_iframe=true&domain_name=adobe.com&redirect_url=https%3A%2F%2Fsp.auth.adobe.com%2Fadobe-services%2FcompletePassiveAuthentication
2024/10/12 16:51:56.817355 [TVE] action=request type=Document method=GET url=https://sp.auth.adobe.com/adobe-services/authenticate/saml
2024/10/12 16:51:57.183725 [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/10/12 16:51:57.611942 [TVE] action=request type=Document method=GET url=https://login.xfinity.com/login redirected_from=https://oauth.xfinity.com/oauth/authorize
2024/10/12 16:51:57.612085 [TVE] action=auth_domain domain=login.xfinity.com
2024/10/12 16:51:58.101025 [TVE] action=wait_for_page
2024/10/12 16:51:58.247289 [TVE] action=error_response type=Stylesheet error=net::ERR_ABORTED url=https://login.xfinity.com/static/resi/dist/prism-ui/prism-ui-ce5b093.css ip=23.62.46.137
2024/10/12 16:52:01.904386 [TVE] action=error_response type=Document error=net::ERR_ABORTED url=
2024/10/12 16:52:08.029348 [TVE] action=page_ready
2024/10/12 16:52:08.029505 [TVE] action=wait_for_page done=true reason=page_ready
2024/10/12 16:52:08.706837 [TVE] action=wait_for_auth timeout=24s
2024/10/12 16:52:08.706877 [TVE] action=fill_form u=gh95959
2024/10/12 16:52:08.727085 [TVE] action=tvejs msg="xfinityLogin: wait"
2024/10/12 16:52:08.727223 [TVE] action=retry_form
2024/10/12 16:52:09.388739 [TVE] action=request type=Document method=POST url=https://login.xfinity.com/login
2024/10/12 16:52:15.046939 [TVE] action=page_ready
2024/10/12 16:52:15.047203 [TVE] action=check_result
2024/10/12 16:52:15.056949 [TVE] action=retry_form step=auth_form count=1
2024/10/12 16:52:16.266258 [TVE] action=fill_form u=gh95959
2024/10/12 16:52:16.266764 [TVE] action=wait_for_auth timeout=24s
2024/10/12 16:52:16.280715 [TVE] action=tvejs msg="xfinityLogin: permission denied"
2024/10/12 16:52:16.280970 [TVE] action=fill_form state=done err=&runtime.ExceptionDetails{ExceptionID:1, Text:"Uncaught (in promise)", LineNumber:0, ColumnNumber:0, ScriptID:"", URL:"", StackTrace:(*runtime.StackTrace)(nil), Exception:(*runtime.RemoteObject)(0x4001914360), ExecutionContextID:0, ExceptionMetaData:easyjson.RawMessage(nil)}
2024/10/12 16:52:16.281256 [TVE] action=screenshot
2024/10/12 16:52:16.376697 [TVE] action=screenshot size=18272
2024/10/12 16:52:16.377229 [TVE] action=capture_html
2024/10/12 16:52:16.379696 [TVE] action=capture_html size=300
2024/10/12 16:52:16.394270 [TVE] action=script_error err=Blocked by Xfinity: There was an error processing your request. Please try again.
2024/10/12 16:52:16.574687 [TVE] Auth failed for Comcast_SSO: Blocked by Xfinity: There was an error processing your request. Please try again.
2024/10/12 16:52:54.204466 [TVE] Auth starting for Comcast_SSO as gh95959
2024/10/12 16:52:54.370478 [TVE] action=auth mvpd=Comcast_SSO requestor=HGTV
2024/10/12 16:52:55.509670 [TVE] action=version product=Chrome/117.0.5938.62 jsVersion=11.7.439.16 protocol=1.3 revision=@25a7172909a4cba7355365cf424d7d7eb35231f4
2024/10/12 16:52:55.512505 [TVE] action=page_ready chromeVersion=117
2024/10/12 16:52:55.513826 [TVE] action=navigate url=https://sp.auth.adobe.com/adobe-services/authenticate/saml?noflash=true&mso_id=Comcast_SSO&requestor_id=HGTV&no_iframe=true&domain_name=adobe.com&redirect_url=https%3A%2F%2Fsp.auth.adobe.com%2Fadobe-services%2FcompletePassiveAuthentication
2024/10/12 16:52:55.520406 [TVE] action=request type=Document method=GET url=https://sp.auth.adobe.com/adobe-services/authenticate/saml
2024/10/12 16:52:55.803076 [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/10/12 16:52:56.207919 [TVE] action=request type=Document method=GET url=https://login.xfinity.com/login redirected_from=https://oauth.xfinity.com/oauth/authorize
2024/10/12 16:52:56.208132 [TVE] action=auth_domain domain=login.xfinity.com
2024/10/12 16:52:57.943127 [TVE] action=wait_for_page
2024/10/12 16:52:58.035431 [TVE] action=error_response type=Stylesheet error=net::ERR_ABORTED url=https://login.xfinity.com/static/resi/dist/prism-ui/prism-ui-ce5b093.css ip=23.62.46.146
2024/10/12 16:53:01.385288 [TVE] action=error_response type=Document error=net::ERR_ABORTED url=
2024/10/12 16:53:07.516856 [TVE] action=page_ready
2024/10/12 16:53:07.517132 [TVE] action=wait_for_page done=true reason=page_ready
2024/10/12 16:53:08.498278 [TVE] action=wait_for_auth timeout=24s
2024/10/12 16:53:08.498290 [TVE] action=fill_form u=gh95959
2024/10/12 16:53:08.522049 [TVE] action=tvejs msg="xfinityLogin: wait"
2024/10/12 16:53:08.522150 [TVE] action=retry_form
2024/10/12 16:53:09.202958 [TVE] action=request type=Document method=POST url=https://login.xfinity.com/login
2024/10/12 16:53:14.522869 [TVE] action=page_ready
2024/10/12 16:53:14.523097 [TVE] action=check_result
2024/10/12 16:53:14.532823 [TVE] action=retry_form step=auth_form count=1
2024/10/12 16:53:15.240567 [TVE] action=fill_form u=gh95959
2024/10/12 16:53:15.240613 [TVE] action=wait_for_auth timeout=24s
2024/10/12 16:53:15.253843 [TVE] action=tvejs msg="xfinityLogin: permission denied"
2024/10/12 16:53:15.254857 [TVE] action=fill_form state=done err=&runtime.ExceptionDetails{ExceptionID:1, Text:"Uncaught (in promise)", LineNumber:0, ColumnNumber:0, ScriptID:"", URL:"", StackTrace:(*runtime.StackTrace)(nil), Exception:(*runtime.RemoteObject)(0x4000771320), ExecutionContextID:0, ExceptionMetaData:easyjson.RawMessage(nil)}
2024/10/12 16:53:15.255100 [TVE] action=screenshot
2024/10/12 16:53:15.354882 [TVE] action=screenshot size=18028
2024/10/12 16:53:15.355401 [TVE] action=capture_html
2024/10/12 16:53:15.358503 [TVE] action=capture_html size=300
2024/10/12 16:53:15.359109 [TVE] action=script_error err=Blocked by Xfinity: There was an error processing your request. Please try again.
2024/10/12 16:53:15.527841 [TVE] Auth failed for Comcast_SSO: Blocked by Xfinity: There was an error processing your request. Please try again.
I don't use a pi, but I understand you can run Channels DVR in a Docker Container on it?
I've gone back and forth with my Synology NAS's using the bare metal vs. Docker installs to get the latest version of chrome when I have issues w/Xfinity TVE.
Currently running my Channels DVR TVE server in a docker container on my Synology NAS using the :tve version and it reports chrome version 120.0.6099.129 vs. your 117.0.5938.62
Thanks, I suspect that the 120 version supports something used by the login form, and the 117 version in my Pi does not.
I brought up the server on a Pi using the image downloaded from getchannels.com. That page also says "Both the server software and the underlying operating system upgrade automatically with no fuss." So perhaps either no one has updated the Chromium contained in the image, or it's not considered part of the "underlying operating system". Anyone know if Pi users have to update Chromium themselves?
I noticed that there's a new pre-release of the Server from a few days ago. It came out after my last attempt to add Xfinity as a Source. I'll try again and see what happens.....perhaps Chromium will change to 120.
Update:
Successfully added Xfinity as a Source, using latest pre-release. However, it only added 82 channels, instead of the usual 100+. Tried another rescan, got 85 channels. Many channels are getting an error, one instance included below. Looks like there's still some problems.
Chrome locked by `/mnt/data/channels-dvr/data/chromedata/Comcast_SSO/SingletonLock': chrome failed to start: [18975:18975:1017/115558.256495:FATAL:spawn_subprocess.cc(221)] posix_spawn: No such file or directory (2) [18955:19002:1017/115558.719375:ERROR:bus.cc(406)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [18955:19002:1017/115558.719519:ERROR:bus.cc(406)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [18955:19002:1017/115558.719559:ERROR:bus.cc(406)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [18955:19002:1017/115558.719593:ERROR:bus.cc(406)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [18955:18955:1017/115558.743416:ERROR:system_network_context_manager.cc(797)] Cannot use V8 Proxy resolver in single process mode. [18955:18955:1017/115558.744592:ERROR:process_singleton_posix.cc(335)] Failed to create /mnt/data/channels-dvr/data/chromedata/Comcast_SSO/SingletonLock: File exists (17)
I’ve tested all of the versions up to 130 on the Synology and the Pi and haven’t seen any change/improvement in this error.
1 Like
Thanks Eric. I noticed another prelease posted today (2024.10.17.1732) so I upgraded and tried again. Whatever you guys did seems to have worked! I successfully added Xfinity as a Source by just rescanning all channels. Got 122 this time, which is about what I was getting a few weeks ago before the problem started.
2024.10.17.1732 has only been running for 30 minutes but so far it seems to have fixed the problem!
Thanks!
Jack
We didn’t make any changes related to that so I think it was just a coincidence that it started working.
1 Like
I've always hated when things just start working without doing anything.
FYI, some channels did get the "stylesheet error", but most of the failures were expected, like "not in subscription". I didn't see any of the Lock File errors which were common in the 10.14 prerelease. Chromium version is reported as 124. Ended up with 122 channels out of 155.
If it would be helpful I can send in the diagnostics or logs.
Interesting. Mine is still v120 using Channels DVR v2024.10.17.1732
Thanks for all the support so far. I'll keep waiting. Still having the "Blocked by Xfinity: There was an error processing your request. Please try again." error. Upgraded 2024.10.14 to 2024.10.17.1732, Synology with Chrome 114.0.5735.199.
Two suggestions, just shots in the dark:
- I couldn't add a source while using Chrome 117. So it might help to get Chrome on your NAS up to a more recent version. But I have no idea how to do that...
- there's another player in this game, namely the server(s) on the Xfinity side. They may have changed something which made my add-source suddenly work. Try adding the source every day or so. Even if you get errors, the other side is probably getting errors also in their logs. That may motivate them to change something.
Good luck!
On a Synology, I only know of two three ways, since chrome is integrated in the install and not a separate chrome/chromium like Mac, Windows, etc.
- Click and hold the Sign In button when adding the TVE source
- Use either the Synology package or the
:tvedocker container, whichever uses the latest chrome version. - Run
Support > Troubleshootingand if Chrome can be fixed/updated you will see a button for it
