Guess I just don't understand. You have to login to your chrome browser to use it???
Yes... I am trying to give the Developers some feedback on what I have to do to make YouTube TV work. Others are posting the same problem with YouTube TV and that it does not work for them either. This is the workaround I have found. However, I am now having a problem getting Local Channels. Those that have YouTube TV working do you get Local Channels. To be clear I am talking about CBS, NBC (i lost this on DTV), ABC, KTTV - ie. all channels < 6011.
1 Like
When looking at the Channel Lineup and the errors like YouTube TV does not provide this channel (something like that) the Local Channels are not even listed. As if you are not even trying to access them. Does this have something to do with it?
Local Networks via TV Everywhere
Try again over HTTPS here or here. Your browser failed to retrieve your geolocation: Only secure origins are allowed (see: Prefer Secure Origins For Powerful New Features).
I clicked it to check but it is just spinning so not sure.
Yes, you have to use a secure HTTPS connection to your DVR server and also allow the browser to use its location service
I searched and learned something (I don't use Google or Chrome).
You're really signing into your Google account, not signing into your chrome browser. I thought you meant your browser was user/password protected.
https://myaccount.google.com/intro/signing-in-to-google
Switching to Docker on Synology is successful for me. I added YTTV as a source on the first try.
First I made backup of the library database. Then stopped channels and created a Docker container. It was relatively easy, with some effort to make sure I was pointing to the right directory during setup. Everything I had added in the native Synology program was still there.
My Synology is running DSM 7.2, so it uses Container Manager. The configuration file doesn’t seem to exist as a separate entity in the native application so I created a new directory config to mount on channels-dvr.
services:
channels-dvr:
container_name: 'Channels-DVR'
network_mode: host
environment:
- TZ=America/Detroit
ports:
- 8089:8089
devices:
- /dev/dri:/dev/dri
volumes:
- /volume1/ChannelsDVR:/shares/dvr
- /volume1/docker/channels/config:/channels-dvr
restart: unless-stopped
image: fancybits/channels-dvr:tve
3 Likes
i was struggling to get docker to work on synology and i found for some reason it wouldnt accept my custom ports.
switched off the current package running and then boom on 8089 its running and logging in with yttv credentials.
So now i need to fix it from my test folders to use the storage volume i had on the original install
did you just restore from the backup file? or point to all the same directories ?
I used the same /volume1/ChannelsDVR directory that the native app created and used. As I stepped through setup it had me select a specific directory in the mount at /shares/dvr. Setup had me select a backup of the library database to restore and it was easy to find the backup made minutes earlier.
i use a external drive, its weird the docker instance cant get to usb.
but i dont have any special restrictions....time to spend more hours toying with synology's docker
Up to Synology DSM 6, the usb drivers were included in the kernel but then on 7+ Synology removed usb support.
ah , the native channels app accessed by drive just fine.
never messed with docker on synology since i have a different system where my docker stuff goes
With Docker, you have to map the Synology host direcories into the docker container in order for Channels DVR running in the docker container to see them.
When I played with using a USB drive in this post, it was accessed on the Synology at /volumeUSB1/usbshare
So you would need to map the Synology USB drive directory to the docker container /shares/dvr directory
--volume /volumeUSB1/usbshare:/shares/dvr
And then select the /shares/dvr directory from Channels setup (running in a container)
yup i did that still wouldnt show, but i tried mapping the volume of the usb to a different container mapping and bam got usb drive.
going through the synology gui took way longer than if i had just installed portainer or used cli
What, exactly does that mean?
so lets say i had it mapped /volume1/usb1:/share/dvr
that wasnt seeing the usb, but passing it as /volume1/usb1:/usb1 i was then able to reach all my recordings and backups.
OK, most likely you typo'd something on your first attempt, or had capitalization wrong (linux is case sensitive)
There is no difference in those two mappings, other than the Synology directory /volume1/usb1 appearing inside the docker container at /share/dvr in the first one (I use /shares/dvr) and /usb1 in the second
1 Like
Any one find a fix for this?
Does anyone have a guess why using Docker Google would see the Browser as Secure and think it is not Secure when not using Docker?
Another workaround. I have a second Synology NAS running a LINUX VM (pop-os). I installed Channels DVR on that LINUX VM with Google Chrome (google account) logged in. And YouTube TV worked. I then Logged out of Google Account and Channels Continued to work. I then rebooted Synology with the Linux VM set to autostart and Channels continue to work on restart with Google Account still not logged in.
What version of Chrome is reported when you use docker?