Have the Issues with YouTube TV been fixed?

I'm using the package version of Channels on my Synology.
I create an account on gmail just for Channels and it will usually validate and log in on the first time.
I will then invite the new email

1 Like

So far

WORKS

  • Windows
  • Linux VM
  • Synology Package
  • Channels DVR TVE Docker image on Synology NAS
  • Channels DVR TVE Docker image (bnhf image) on Synology NAS

FAILS

  • Channels DVR TVE Docker image on Synology NAS
1 Like

Yeah I don’t use windows either and while I have a spare Mac just on the network I like channels on my synology better

What’s the difference between synology package and the docker image?

The Synology package install runs the executables on Synology custom linux and uses an older version of chrome.

The docker image install runs the executables on Alpine linux in the container and uses a newer version of chrome.

Nobody (besides google) seems to know what platform differences the headless chrome sees from its point of view, causing it to work or not work.

Actually the Docker image uses Chromium not Chrome. For good reason of course, as Linux Chromium is cross-platform and Linux Chrome is not (amd64 only). There are many potential reasons for TVE to fail, but given a number of people have reported YTTV failures with Docker, I thought I'd spin-up a test image built with Chrome.

This custom image worked great for me with YTTV -- no different than CDVR running in a Proxmox LXC, or on Windows. Hopefully, one or two of those people reporting failures (@slampman?) will be willing to confirm functionality with a custom-built image as described here:

This should be relatively easy to add to Project One-Click, both the custom image build and the spin-up -- if it proves out...

Ahh, didn't know that.

I would try it, but don't have a YTTV sub or a google account and the below sounds confusing.

Reading this Use YouTube TV to sign in to network sites - YouTube TV Help makes me think that only the Family group manager's credentials will work for TVE, but not any invited Family group members?

Family groups

  • Only the family manager’s sign-in info will work to log in and stream directly on the specific network site.

So how would creating a new google account and inviting it to be part of the Family group allow that family member to access TVE?

I sure will! I'll test it out this weekend :grinning:

1 Like

That is confusing. However, at least as of the moment, creating a family account and adding a second e-mail address with 2FA disabled does work for TVE.

Let's hope that "help" info is outdated rather than foreshadowing.

1 Like

I want to trial YTTV TVE this week to see if it works on;

  • Channels DVR Synology package
  • Channels DVR TVE Docker image
  • bnhf's Channels DVR TVE Docker image

I'm not invested in the google eco-system, so I've started from scratch.
I created a google account and gmail with 2FA that I'll use as my primary google account to get a trial of YTTV.

Not clear if these steps are correct to get a username and password to use for Channels DVR.

  • I've read I can create another google account without a gmail address using accounts.google.com/SignUpWithoutGmail
  • This is the second account I want to create without gmail and without 2FA to use with Channels DVR.
  • Sign into my primary account, create a family group, invite my second account to join it and get my YTTV trial sub using my primary google account.
  • Now I should be able to use my second google account username/password for Channels DVR YTTV TVE.

Does this sound correct?

Just create another Gmail account, it doesn't have to be a non Gmail address

Then follow this
https://support.google.com/youtubetv/answer/7251139?hl=en

1 Like

So far in testing;

  • Channels DVR Synology package WORKS
  • Channels DVR TVE Docker image WORKS
  • Channels DVR TVE Docker image (bnhf image) WORKS

So much for this

I just changed it to Channels DVR TVE docker image WORKS and FAILS.
It works for me.

I think it also works on Windows, but I don't run CDVR on Windows.

I've had no issues with it working on Windows CDVR

1 Like

I'm able to use YTTV TVE on my Synology NAS (DS-1019+)

Most YTTV TVE channels mentioned here are working and also some that are not mentioned.
Here are the channels (minus the FAST ones) I'm getting (the same on all three installations I have)

CHAN x NAME                    AUTHENTICATION ERROR MESSAGE
---- - ----------------------- ----------------------------
6001   ABC (KXTV)
6002   FOX (KTXL)              Authenticates, but fails streaming
6003   CBS (KOVR)
6007   CSPAN                   YouTube TV does not provide TVE access to CSPAN
6008   CSPAN2                  YouTube TV does not provide TVE access to CSPAN2
6009   CSPAN3                  YouTube TV does not provide TVE access to CSPAN3
6015   VH1P
6019   BETP
6030   CNN
6031   HLN
6032   CNNI
6033   TBS
6034   TBSP
6035   TNT
6036   TNTP
6037   TRU
6038   TRUP
6039   TCM
6040   TCMP
6043   AETV                    YouTube TV does not provide TVE access to AETV
6044   HISTORY                 YouTube TV does not provide TVE access to HISTORY
6045   FYI                     YouTube TV does not provide TVE access to FYI
6046   LIFETIME                YouTube TV does not provide TVE access to LIFETIME
6070   NGC
6071   NGCP
6072   NGWILD
6073   FNC
6074   FBN
6080   FX
6081   FXP
6082   FXX
6083   FXXP
6084   FXM
6085   SUNDANCE
6086   AMC
6087   BBCA
6088   IFC
6089   WETV
6090   HALLMARK
6091   HALLMARKMM
6092   HALLMARKDRAMA
6095   REELZ                   YouTube TV does not provide TVE access to REELZ
6097   NEWSNATION
6100   OWN
6101   DISCOVERY
6102   FOOD
6103   ANIMAL-PLANET
6104   HGTV
6105   TLC
6106   TRAVEL
6107   INVESTIGATION-DISCOVERY
6108 - DIY                     playback info: access.denied.missingpackage: MagnoliaNetPreview
6109   COOKING-CHANNEL         playback info: access.denied.missingpackage: Cooking
6110   SCIENCE                 playback info: access.denied.missingpackage: Science
6111   AHC                     playback info: access.denied.missingpackage: AmericanHeroes
6112   DESTINATION-AMERICA     playback info: access.denied.missingpackage: DestinationAmerica
6113   DISCOVERY-LIFE          playback info: access.denied.missingpackage: DiscoveryLife
6114 + MOTORTREND
6120   DISNEY
6121   DISNEYP
6122   DISNEYJR
6123   DISNEYJRP
6124   DISNEYXD
6125   DISNEYXDP
6126   FREEFORM
6127   FREEFORMP
6140   ESPN1
6141   ESPN2
6142   ESPNU
6143   ESPNEWS
6144   SEC
6145 - LONGHORN                notAuthorized: You are not authorized to view this content.
6146 - ESPNDEPORTES            notAuthorized: You are not authorized to view this content.
6147   ACC
6172   NESNPLUS                YouTube TV does not provide TVE access to NESNPLUS
6196   CBSSPORTS
6197 + FS1
6198 + FS2
6199 + BTN
6200   DEPORTES                not entitled: mvpd: Resource is not supported by MVPD
6201   FS-SOCCERPLUS           not entitled: mvpd: Resource is not supported by MVPD
     -  Supposed to get, but don't  (per https://getchannels.com/docs/channels-dvr-server/tv-everywhere/availability/#YouTubeTV)
     +  Not supposed to get, but do (per https://getchannels.com/docs/channels-dvr-server/tv-everywhere/availability/#YouTubeTV)

@Mikchek @slampman
It's working for me in the Channels DVR TVE docker image on my Synology DS-1019+
Channels DVR pre-release v2025.06.26.1658, says it's using Chrome v132
The other two installs that are working are at the same pre-release version, just different chrome versions (syno package Chrome v129, bnhf docker image Chrome v138).

1 Like

That’s good to know
I’m so confused what is the difference between the synology image and the docker image?

The Synology package is just basically linux scripts that install the linux version of Channels DVR on a Synology NAS (which uses its own custom linux distro).

The docker image creates a docker container which runs the linux version of Channels DVR on Alpine Linux inside the container on top of the Synology NAS. It's isolated in that container from the underlying operating system (Synology NAS).

So basically, the docker image is used to create the same container and contents no matter what underlying operating system it runs on. There are usually different architectures of docker images offered, depending on what hardware (cpu) you run it on.

As far as how google knows what you're running Channels DVR on when you use YTTV TVE, I think only they know the answer to that. They own YTTV and Chrome, so have insider knowledge.

If you're using the latest Channels DVR docker image with the :tve tag, it should work with YTTV
https://hub.docker.com/r/fancybits/channels-dvr/tags

Possible solution to YouTubeTV
HARDWARE: Synology NAS, with Channels Apps (not Channels docker)

Like everyone else, I was being blocked by Google/YoutubeTV. Here is what I found.

Step 1: Create a new Google account. (NO Passkey or 2FA.) Just the username and password. PW has no special characters, just numbers, and letters (upper and lower case)
Step 2: Do NOT subscribe to YouTubeTV, yet.
Step 3: Sources--> Add Source-->TV Everywhere. Add the new Google account.
Step 4: Channels will try to connect. It added the basic free channels. (ABC News, CBS News, etc)
Step 5: Once completed, THEN I purchased a NEW YouTubeTV subscription. (Trial discount).

NOTE: I tried to use my existing YouTubeTV account, but it did not work.

Step 6 Once the NEW YoutubeTV has been set up with the NEW Gmail account, then return to CHANNEL--> SOURCE --> MANAGE (youtubeTV)-->RESCAN CHANNELS. It adds the eligible Channels (Note: TVLand, CMT, etc are missing)

When I set up the NEW YouTubeTV subscription, for LOCATION, I used a zip code in Montana and ran ExpressVPN/Seattle on my Apple TV. I can get the local channels on the YouTubeTV App in Montana. Just make sure your VPN is on your device. On the Channels App, the local channels are my home local channels. Hope this helps. This worked for me.

1 Like

@ouman28 thanks, this worked i tried a slightly different path to attempt to see what mattered and didn't
I am on synology using the synology package not the docker container, it was installed many years ago...

  1. i created a new (non-gmail) google account, i never touched any other settings, i used my own email
  2. i logged into YTTV and like you said i didn't subscribe
  3. i then added it as source, and watched the logs, it took many loops in the log, but did start scanning channels and showing i was not authorized
  4. while that was happening i went and subscribed with that new account and after a few minutes (it was still scanning from previous steps) the later channels started to be authorized

i will rescan when that is complete to mop up the failed channells, thanks so much, i was tearing my hair out :slight_smile:

I suspect the step with this being a new account that hasn't been used with any other google services and hasnt ever had the security settings touched is they key.

thanks again, super useful post!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.