YouTubeTV TVE failing: This browser or app may not be secure

[eric]

The specific thing that would be helpful here is for someone who has actually had the DVR installed on a NAS and had this YouTubeTV error then install it in docker on that same system right after and have YouTubeTV authenticate just fine.

What I was meaning is that to diagnose this issue, having first hand accounts of what has worked for people will be important.

[dfrap]

Docker instructions: Channels — Channels DVR Server

I provided an example of compose.yaml for Synology Container Manager : YouTubeTV TVE failing: This browser or app may not be secure - #62 by dfrap

Because network mode is host, setting ports to 8089:8089 is not necessary and causes a warning which can be ignored.

[chDVRuser]

Here's using command line docker commands.
You can use the same port, settings and directory currently used by your Synology Package install.

YouTubeTV TVE failing: This browser or app may not be secure

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 switch…

[Jx_Mullins]

I got around this same issue by making sure I was logged in to the same YTTV account in Chrome as well as on the regular YouTube app on my phone. Once it started scanning for channels about 4x it popped up asking me in the YouTube app to verify my sign-in. Once I clicked yes each time it went on scanning. No issues afterwards.

[rpaulmerrell]

Unless we can get some way of accessing the Chrome browsser in Synology, we can't use TVE on YTTV.
if anyone has a way i can access the embed Chrome on Synology, it would be appreciated.

[chDVRuser]

Have you tried using a docker container on your Synology. It's worked for others.

[rpaulmerrell]

Trying to stay away from running Docker version.
I'm simply going to evaluate what channels i need and most likely leave YTTV.
Philo has most of what is broadcast and Fubo has move. Just wanted to see my options.

[dsd8154]

I was able to get docker working with YTTV. It reports Chrome Version: 120.0.6099.129. Whereas the version under the Synology NAS package was like 114. This must be the difference. Is there a reason that the Synology package cannot update the chrome version?

[eric]

We have an outstanding request for feedback for people who have had problems with the NAS package but success with the Docker setup to try this out and see if there is any improvement:

YouTubeTV TVE failing: This browser or app may not be secure

If you are running a NAS on an x86_64 processor and are running into the "may not be secure" error with YouTube TV, you can test something out by doing the following: Update to the latest pre-release Go to Settings -> Advanced and enable New TV Everywhere Embedded Chrome Launcher Run curl -XPUT 'http://<dvr-ip>:8089/dvr/hacks/tve.chromium_tag/116.0.5845.14' Scan a channel that wasn't working or try to re-add YouTubeTV if it was not added Submit Diagnostics Report back here how it behaved O…

[dsd8154]

Hi @eric, I did as you requested above. First, I installed the Docker container on my Synology NAS and can confirm that this work (chrome browser version at like 120.xx.xx. I was able to add a YTTV source and used it for about a week.

Today, I turned off my docker container and started my Synology native package and updated to the current release. Chrome browser reported version 114. I ran the Curl command successfully and confirmed that chrome browser reported version 116. I attempted to add YTTV source as I did under the docker container. It failed again with the browser error “may not be secure”.

Diagnostics report below:
678b6a6f-f6a4-44fd-820c-16bc1e3046e8

Let me know if you need additional information.

I will move back to the Docker container for now.

Doug

[eric]

Thanks for confirming it didn’t solve the issue. We’ll have to look into other solutions.

[rpaulmerrell]

I'm hoping the devs can find a solution to the YTTV TVE problem.

[LAX]

Is the older Chrome browser version a function of the ChannelsDVR.spk or what is provided by Synology? I'm trying to understand why Docker version and native Synology version have different Chrome revisions.

[rpaulmerrell]

I think it has to do with Docker being a virtual environment..
I've moved on to Philo and Fubo TV for TVE service.

[jsfullam]

I recently subscribed to YouTube TV. I set up a second family member's account without two factor authentication. Using those credentials, adding the TVE source successfully scanned all the channels without problem.

[rpaulmerrell]

I'm hoping it will work for a while.
Eventually, YTTV will require 2fa. I've been down this road several times.
When it works, it works great.

[passband]

Came here looking for solutions to this myself. In my case the solution was easy and may help others. I had installed a new graphics card in the Debian server running the Channels DVR server and while installing the drivers the chromium package was uninstalled. From other posts in the forums here it has been confirmed that TVE requires the Chromium browser (e.g., https://community.getchannels.com/t/channels-and-chrome/37347/2). In any case, once I re-installed the Debian chromium browser the TVE error was fully resolved. I might suggest that anyone seeing this TVE error check that their Chromium browser is updated, as it undergoes frequent security updates. If Channels DVR is running in a docker image or under docker-compose, Chromium browser updates may be automatic and not run into this error.

[slharman1]

I keep getting "No Login form found"
What the heck is that about?