I decided to switch from DTV Stream to YouTube TV this weekend and ran into this issue. I am on Synology NAS (intel) and sent DIAG to Developers and verified all is GREEN for Google Chrome etc. I have not heard back from Developers yet. Does anybody here know if this issue is simply a LINUX Problem or NAS Problem? Someone said it worked on a macOS but then I read that maybe this is random? Really need to get a resolution by DEC 6th which is when my DTV Expires. I do not watch a lot of LIVE TV any more and my wife really loves this Channels UI. So, of course she could use the YouTube TV App but not a preference.
1 Like
hmm i'm also on a synology install and i cant get yttv or directv to work suddenly
i know there was a synology update not too long ago but i doubt thats it the connections seem to get to where theyre going and fail
Another data point. Unable to add YTTV on a Synology install just as I was unable to add Hulu.
With the latest updates, I'm getting a captcha every time I try. I really wish there was a way to respond to the captcha. I do not see any notifications from Google app that I can respond to.
Is there any reason to try switching Channels to Docker?
If you can spin up a Channels DVR :tve docker container, just add one and try it out.
It can coexist with whatever you're currently running.
The current Channels DVR :tve docker container uses Chrome v117
The current Channels DVR Synology package install uses Chrome v114
It's worth a try to see if the difference in Chrome versions matters.
Might also be some data the servers see from the headless chrome, like OS, or?
According to @tmm1, they're using AI to determine what to block and only they know what that is. They also control chrome and yttv.
so just setup the docker channels instance on the synology instead of the synology package to test?
Could do it two ways.
#1 Leave the Synology Package running and install the docker using a different port and pointing to a different DVR recording folder.
OR
#2 Stop the Synology Package, install the docker using the same port and DVR recording directory as the Synology Package used.
If you use #2, you can Stop the Docker Container and Start the Synology Package, or Stop the Synology Package and Start the Docker Container and either one will record to your existing directory.
Before switching from one to another, backup, then switch, then restore. This keeps the settings and current library items synced between the Synology Package and the Docker Container.
In either case, when installing the Docker Container you'll want to use /volume1/docker/channels-dvr
Here's what I did.
Backup your current Channels DVR Server.
Change this line to use your actual DVR recording directory (mine is /volume1/ChDVRtve)
--volume /volume1/ChDVRtve:/shares/dvr
And change this line to your correct time zone
--env TZ=America/Los_Angeles
create directory
/volume1/docker/channels-dvr
docker pull fancybits/channels-dvr:tve
docker run \
--detach \
--env TZ=America/Los_Angeles \
--name=channels-dvr \
-p 8089:8089 \
--restart=unless-stopped \
--device /dev/dri:/dev/dri \
--volume /volume1/docker/channels-dvr:/channels-dvr \
--volume /volume1/ChDVRtve:/shares/dvr \
fancybits/channels-dvr:tve
Restore from the latest backup you made.
Then in the Channels web UI you set the recording directory to /shares/dvr when running the Docker Container, which maps to the actual directory on the Synology you record to.
You would just have to delete and recreate the guide database (if it doesn't do it for you).
Of course you want to make sure you update to latest prerelease on each one of the two.
so had some issues with docker on synology but pulled out my old rpi4 i used before synology and updated to latest with updated chrome.
Same exact issues with yttv and directv stream.
so i think safe to say for me it isnt the synology
everything was working last week its odd
2 Likes
What version of chrome is the rpi4 install running?
1 Like
117.0.5938.62
synology is
114.0.5735.199
Also appears something else is going on with rpi4 and yttv
2 Likes
Slightly unrelated but directv stream stopped working too wth an auth error.
to me it looks like its trying to authenticate to nbc and cannot gets an error on the adobe login
YT is always an issue with secure browser
There are users reporting it works on their Synology package install and others saying it doesn't and they had to run it in docker on their Synology for it to work. I don't recall seeing anyone saying it works on their rpi4.
also with other sources? yttv i get is the known issue with secure browser, directv is the one that i cant figure out.
just yttv that i've seen
It’s become a crapshoot.
Is that running in a container, or just on the RPi4?
What version of chrome is it running now?
its just on an rpi4
117.0.5938.62
its just strange this pi has exact issues synology with 2 sources
Since google controls both chrome and yttv, there is all sorts of info they can get from a browser that we don't even know about. Lookup browser fingerprinting and device fingerprinting for a start.
i spun up a docker on a debian VM same issues.
yttv i get the login screen problem, so i think yttv is just dead.
directv auth401
Update:
now suddenly yttv is adding on both my new vm and the pi4 but not synology. Strange.
DTV still wont though
2 Likes