I navigated to c:\programdata\channelsdvr\data\chromedata and there were no files or folders in that folder at all. Not sure what that means.
Thanks for the help!
That is only created once the source is added so I guess not relevant here.
Usually not in subscription happens when there's a local Comcast account used as ISP which is auto authenticating. But it seems like other issues are going on with their auth recently so I'm not sure anymore.
It is strange since it worked before the other day. Is this something that can be debugged or am I just out of luck?
And for me and many others, and as i posted before, with this auth issue, before i removed it as a tve source, it said "Cable provider authentication failed" when each channel was re-scanned...er go....not the same issue, exactly, as you are having. as tmm1 already pointed out...but, could be related or side affect in some way...who knows.
Trying to decode what you posted.
So a new Chrome version 89 is available, but to get it, one has to do both of these?
- update to the Channels DVR pre-release 2021.04.07.2050
- curl -XPOST http://x.x.x.x:8089/providers/tve/chrome
Then what are you looking for as far as testing when on a Synology (which I thought you had)?
I'm running it (TVE) on my older Synology NAS, my new Synology runs Channels DVR with an HDHR Prime.
1 Like
This worked for me. After doing the funky way of updating the Chrome on the Pi image, i immediately re-scanned the one channel that i had tried before, that then went Cable Auth failed, and, after this update process, it authorized.
All my Xfinity channels working again.
(Until next time, when Xfinity decides it needs a newer Chrome version, i guess)
so yea... this issue seems to be version of Chrome related i guess.
maybe we all can run that update every so often then?
can it be made a button in the server gui to update Chrome? just to make it easy and fast?
I tried those steps on my Synology NAS and now I get that SSO. I've never deleted Xfinity as the source, just always changed the password back to the original one when it complained:
2021/04/08 07:11:45.647077 [TVE] action=auth mvpd=Dish requestor=nbcentertainment
2021/04/08 07:11:45.648075 registry.ping url=https://registry-1.docker.io/v2/
2021/04/08 07:11:46.194731 registry.manifest.get url=https://registry-1.docker.io/v2/chromedp/headless-shell/manifests/89.0.4389.114 repository=chromedp/headless-shell reference=89.0.4389.114
2021/04/08 07:11:46.916173 registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:1633fec4c8941cfbdde74459550ed95d255878d91ee08fb5894627cdf046fca0 repository=chromedp/headless-shell digest=sha256:1633fec4c8941cfbdde74459550ed95d255878d91ee08fb5894627cdf046fca0
2021/04/08 07:11:49.335649 registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:f04fd593031a9b736187fbfac2f8e72fbe68bc9d65ca2eaeedf9f618e255d658 repository=chromedp/headless-shell digest=sha256:f04fd593031a9b736187fbfac2f8e72fbe68bc9d65ca2eaeedf9f618e255d658
2021/04/08 07:11:50.180423 registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:71120124a9d579b544ff09506c59a81f5548dd2f19b278622307af04ef29e189 repository=chromedp/headless-shell digest=sha256:71120124a9d579b544ff09506c59a81f5548dd2f19b278622307af04ef29e189
2021/04/08 07:11:54.209594 registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:5af79d440e20791028323fc0d80605674d6442a23dc49909a362e9f94b22cae4 repository=chromedp/headless-shell digest=sha256:5af79d440e20791028323fc0d80605674d6442a23dc49909a362e9f94b22cae4
2021/04/08 07:11:54.917578 [TVE] Auth failed for Dish: context canceled
2021/04/08 07:14:36.063618 [TVE] Auth starting for Dish as test
2021/04/08 07:14:36.063694 [TVE] action=auth mvpd=Dish requestor=nbcentertainment
2021/04/08 07:14:36.064727 registry.ping url=https://registry-1.docker.io/v2/
2021/04/08 07:14:36.544721 registry.manifest.get url=https://registry-1.docker.io/v2/chromedp/headless-shell/manifests/89.0.4389.114 repository=chromedp/headless-shell reference=89.0.4389.114
2021/04/08 07:14:37.196822 registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:1633fec4c8941cfbdde74459550ed95d255878d91ee08fb5894627cdf046fca0 repository=chromedp/headless-shell digest=sha256:1633fec4c8941cfbdde74459550ed95d255878d91ee08fb5894627cdf046fca0
2021/04/08 07:14:39.444624 registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:f04fd593031a9b736187fbfac2f8e72fbe68bc9d65ca2eaeedf9f618e255d658 repository=chromedp/headless-shell digest=sha256:f04fd593031a9b736187fbfac2f8e72fbe68bc9d65ca2eaeedf9f618e255d658
2021/04/08 07:14:40.017414 registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:71120124a9d579b544ff09506c59a81f5548dd2f19b278622307af04ef29e189 repository=chromedp/headless-shell digest=sha256:71120124a9d579b544ff09506c59a81f5548dd2f19b278622307af04ef29e189
2021/04/08 07:14:43.879862 registry.blob.download url=https://registry-1.docker.io/v2/chromedp/headless-shell/blobs/sha256:5af79d440e20791028323fc0d80605674d6442a23dc49909a362e9f94b22cae4 repository=chromedp/headless-shell digest=sha256:5af79d440e20791028323fc0d80605674d6442a23dc49909a362e9f94b22cae4
2021/04/08 07:14:44.276139 [TVE] Auth failed for Dish: context canceled
2021/04/08 07:19:54.546233 [TVE] action=auth mvpd=Comcast_SSO requestor=golf
2021/04/08 07:19:54.623346 [ERR] Could not start stream for TVE-Comcast_SSO ch6159 GOLF: TVE: context canceledI use a Synology DS718+ and am willing to troubleshoot/test with you.
I followed the instructions to update Chrome, and got a "Context Cancelled" error. I checked the logs and it was an error trying to reach Docker..only I wasn't trying to use Docker anymore. I then went in and uninstalled docker completely from the NAS, and uninstalled the native Channels spk.
- Reinstalled Channels spk native app
- Opened and updated to latest build (via hold)
- Followed the instructions exactly, including hold the sign in button.
I still got "Context Cancelled" again, and my logs still are trying to ping Docker. How do I now get out of this hell hole from trying to follow the docker recommendation?
@JBgotM: I never had Docker on my Synology and I'm getting the same thing (Context Cancelled with Docker errors in the log), so it's nothing within your modified installation. It seems like something's changed in the latest build that's assuming Docker.
Please make your own thread for your docker and chrome update context canceled issues. @JBgotM and others
This is the same issue.
TVE fails to authenticate Xfinity, which has been confirmed to be an issue with the the Chrome version used by the channels app. The logs of this failure state that channels is looking for docker, which appears to be a bug. @jimf confirmed it is not related to a docker install.
No....your issue of nothing being able to update, getting context canceled error with your NAS device, is NOT part of the Xfinty TVE issue.
It is specific to your server device as that is not happening to me and others here that are not using that as a sever.
please make your own tread in regards to that context error issue.
I would make things easier to help address your specific issue, and keep this thread less cluttered.
The context cancelled issue is fixed in 2021.04.08.1642
Follow the same steps as before
4 Likes
Success! Thank you for working through all the intricacies to get this running again. I see TVE integration as a big benefit and one of the reasons I stick with this platform.
1 Like
Thanks! As the chrome install ages, will we be able to repeat this process to update on our own?
Updated to 2021.04.08.1719 and followed the instructions.
I've now lost DIY channel 6108 and can't get it back.
Other than my local PBS and some free channels, that's the only cable channel I record with TVE.
I tried rescanning that channel multiple times and then rescanned all channels.
Still getting a 403 forbidden error on DIY channel 6108.
I can login and watch https://watch.diynetwork.com/watch/diy with my Xfinity credentials no problem.
Send me some diagnostics and I will look.
Logs have been submitted as e8232d1b-bd22-45a2-b0ec-a5f7daf01664
Try the new prerelease and resubmit if not working.
2021.04.08.2119 didn't fix it. Still same 403 error.
Logs have been submitted as 18ac20bd-7b0c-42ab-81d5-2d1d5e7f666b