I'm experiencing issues again too, though interestingly only with the Discovery Family Network of channels. Other things like Own, Hallmark, etc that aren't Discovery channels are fine. Interestingly, I can access them in Chrome on my computer (in version 88). I hope we don't lose the TV everywhere completely again.
Thanks for confirming that, was sounding like I was stupid or something. I managed to fix them with the whole pw change, removing and readding xfinity a few posts back, not sure if you want to take those drastic measures until necessary (it will be eventually).
Also, I found the status of the other channels with the checkmark, looking all a-ok weren't ok, I would rescan some of the ones that say they work and it would come up with the error on those too. Not all, but some.
I hate to do that if until I have to, it always makes me nervous that I won't get my channels back. I'm mooching off a family member for the log in and I'm on a VPN so that just adds to the complications with me. I do have my own sign in so hopefully they won't be getting a password reset email. I've just skipped the last couple of things on any of those channels for the next few days, so hopefully it'll work out before then. If not, I'll deal with it on the weekend as long as everything else keeps working.
I too, am sharing logins. My password was still working so I just signed in and changed it, it hadn't gotten to the denied access, need to use the primary account to fix it.
I'm looking into this now. Chrome v89 is available in the v2021.04.07.2050 prerelease for Intel-based NAS. To update chrome, you must click-and-hold the Sign In button:
- click add source
- select dish (or any other provider you don't have)
- enter test/test for user/pass
- click-AND-hold the Sign In button for one second
You can also do it via the API:
curl -XPOST http://x.x.x.x:8089/providers/tve/chrome
I tested on my QNAP and it works. It may require some tweaks on Synology so I would appreciate testers.
I have issues with TVE-Xfinity. I have removed the source, reset password, rebooted my Windows 10 computer that has the Channels DVR server installed on it. I did all of that last night. I just tried to add the TVE-Xfinity source again with the new password I still get the "not in subscription" error. I can log into my Xfinity account with the same credentials so I have no idea what is the issue.
Can you help?
Thanks,
Chuck
Not the same issue being talked about here. This is for those who can not even logging authentication failed and get password reset email.
Not in subscription is a different problem since it is after one gets the tve added and it accepts the login fine
Try deleting c:\programdata\channelsdvr\data\chromedata\Comcast_SSO
Not exactly like you explain. It doesn't add TVE-Xfinity at all as a source and it gives me that error message. So, the TVE-Xfinity is not available for me to do anything with.
When this first started I did have TVE-Xfinity already added and when I rescanned them individually it did say "not in subscription" for each channel. This issue now doesn't even allow me to add the source at all.
1 Like
I will try this now. Thanks for the suggestion.
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.