Thank you. I didn't realize that was a way to do it. What happened to the simple Click Here to Update Chrome from the troubleshoot if it was outdated. I was only able to get it to 129. Going to restart NAS and try again if I can get it to 132.
After restart no change. Latest version it would upgrade to is 129.0.6668.59. I can't get 132. So maybe thats part of the issue.
Is it installed using the Synology Package Install or the Channels DVR TVE docker?
Synology Package.
v129 is the latest version you'll get with the Synology Package install.
TY for checking.
At least it's newer than the v114 you had
Very true.
No, newer versions are not able to run on Synology
You would have to use Container Station if chrome version is important for your provider
Ty good to know. So that means if Youtube TV starts blocking older versions like 129 or older and you have the Synology Package version installed for Channels DVR you will need to move your server from that to a Container or Virtual Machine that can upgrade to a newer version of Chrome/Chromium.That might be what @Matt_Edmunds might be running into now.
1 Like
I don't know if you'll get a different reply from Aman, but for me it seems that CDVR TVE has always been a whack-a-mole game.
Never knew if it's the chromium version or what. I went back and forth between Synology Package and Docker trying to get the latest Chrome version. I never knew if it was the Chrome version, the chromedata folder and what it was holding, etc. And the devs never said.
We don't know either 
Yeah I can’t remember if it’s the Synology package version or I installed it. It was sooooo long ago. But I updated it via the troubleshoot and it went to 129. I then tried going to pre-release seeing if maybe there was a fix there but no dice. Bummer because this was the main way I consumed channels tv content after moving away from a strong antenna signal. I guess I’ll have to get creative.
I started with Synology being my main server and use it as a backup now, but have since switched to a mini pc with a usb drive. I run linux and able to update the os as well as receive chromium updates regularly. Maybe if you have a small pc sitting around just for testing to see if it works. Then you will know if the issue is Youtube or if its old chrome version being rejected.
Was just able to do a test with another account, using Xfinity creds as a test and it appears to work and validate, so definitely seems to be an account / chrome / YTTV issue more than a specific Channels issue which is what I've suspected. Stinks because I doubt YTTV cares.
Yes that is why I mentioned the mini pc with a modern linux install that allows latest chrome for a test to verify if yttv will work then we will know the answer. Since yttv is google, they are going to be more picky than other providers as far as versions to use since they own yttv and chrome ;-(
You could also try installing Channels DVR TVE server in a docker container and see if that works for you.
@bnhf also has instructions for creating your own Channels DVR TVE container that uses the latest debian linux instead of alpine linux and the latest chrome instead of chromium if you want to go that far.
Works for me with YTTV
I've been using it since this June for my YTTV TVE access
2 Likes
I'm running a fresh install in Docker, I've verified that YTTV TVE attempts to use ABC.COM for the initial authorization. this DOES NOT WORK since Disney+ is no longer available in YTTV. I've contacted support and they verifies it, with no fix.
I suggested using NBC.COM or better yet, use ABC.COM as a default, but either failover to NBC.COM, or, use a variable for the value.
Please see if this pre-release is better.