I think maybe existing logons will work but NEW ones will have this new problem.
I'm sure the devs will come up with a fix, and it might work more smoothly and reliably.
So per your additional testing do you still think that 2FA will be required?
I'd rather not go thru the 2FA unless required...
"Google Cloud will require 2FA for all users starting in 2025"
I simply meant that in today's world one should never expect that 2FA is not enabled.
Google is not "requiring" 2FA unless a Google Workspace admin enables that but on personal accounts it is not a requirement yet I am merely saying you should not be using apps today without 2FA it's more secure.
From what I can tell the issue with Channels is "not" 2FA it's the simple fact Google is seeing the channels app connection as an LSA (Less Secure Application) and blocking it in most cases on new connections.
I had an existing connection and it stopped working hence why I tried to make a new connection. I do think existing connections will eventually just stop working, but from what I can tell most certainly any new connections google is blocking it as a LSA (2FA enabled or not) that seems to be irrelevant to the blocking.
It's a bummer as I had over 120 channels on YTTV showing and working including the local streams all of which are gone now since they stopped working and I removed it to try and re-add it and now discovering it's most certainly blocked by google.
At the end of the day you are not going to work around google's security apps just need to work within their requirements and as of now......channels is being considered a less secure app until they move to meet the google security standards for connecting a 3rd party apps to google services. 
If current connections are mostly working I would not remove them for sure or you won't get it reconnected.
1 Like
YouTube TV keeps raising prices ....
Thanks again for a very informative post.
A question:
How did you get all the YTTV "local streams" to work within CDVR... you don't have to answer, LOL!
I will say I am runing the QNAP package but the version is current to what's published ( Version
2024.12.10.0055) and there could be some relationshop to the QNAP OS and Chrome but I Can revert to the docker image and check but I lose the HW transcoding that works so well natively.
generalyl speaking however if a 3rd party app launches a "local" browser to handle the oAuth you never run into the issue of a chrome version built in being stuck at an old version, but I can't tell what/how the chrome version is being determined within the channels app package/version.
I have connected other QNAP apps like Hybrid Mount to google drive without issue as that app uses the proper oauth mechanism with a local browser to connect. See the short videop example below of how it opens a local browser window.
This is how most apps do it (open a local browser) for sure to comply with google security and if your browser is already logged in you just get the permission options presented etc. This is how channels should/needs to connect to the new google.
That I believe was pulled in with the "Local Network" option checked under advanced. I still get a couple pulled in from the DISH connection but not all of them I got when YTTV was connected. You need to be connected to the channels UI with HTTPS though. That has always worked for the locals to get pulled in via TVE
This has nothing to do with less secure apps. Your error says your browser is not secure, which happens when running too old chrome or running on a NAS.
To add to this i literally set up a new tve connection with YTTV last week on my ubunutu server and it worked perfectly. i have not enabled anything re: less secure apps. Now the channels docker fails every time but stand alone ubuntu server works great
1 Like
So even the docker container fails too?. I’d have to go back and check that option but it’s way too random.
Works on native installs not in docker or NAS packages which means it needs better documentation on what works and what doesn’t. Random is no good.
This sounds more likely to the docker problem so host combo may affect it too then
Only place I can run docker is on the QNAP same as the thread above is on synology so even the chrome version in docker on various hosts may differ. It shouldn’t matter though since docker image is self contained and should include its own chrome version. Not sure why it would rely on the hosts version as indicated in the thread above.
1 Like
He was running the :nvidia tagged image which uses an older chrome than the :tve tagged image.
I think the same problem exists even with the :tve tagged image compiled for different platforms.
The developers have had to create new images to get a newer chrome version.
For an OS that you can install chrome on, a native install of CDVR will use it.
Don't know of any NAS that can install a chrome package, so it needs to be included in the CDVR NAS package or CDVR Container image.
I was just going to reply the same thing that :tve image is needed LOL.
I flipped myself from the QNAP image back to the docker :tve and
Also as an update Google with 2FA still does work with the :tve image BUT if you have a PASSKEY configured on the account then that is no dice. I simply got the 2FA "is this you yes/no" on my device with gmail installed.
Tested an app password as well and that was no go.
That is why I switched to SlingTV a while back. I only use ah4c and SlingTV blue for Premier League (USA Network). I kept Paramount/Showtime with YouTubeTV for $10 and Starz as well. Now just out of spite I a going to get those with SlingTV as well.
I'm actually on a friends YTTV since he has access to my plex server so it's a trade off of sorts. I am going to test a basic google account next with no extra login security just waiting for him to add that new account to the group. Then I should be able to keep the passkey on my own account he added years ago. That new account I am hoping won't do the 2FA prompt on my device when trying to start a channel either and I can then re-enable full security on my other account and use this new one just for channels DVR and my freular one with the native YTTV app.
I actually tried the new account added ot my buddy's family no 2FA or passkey (although google REALLY pushes you to add them!). Removed and re-added YTTV with the docker TVE container (vs NAS version) with dev/dri enabled. Everything is pulling in and I am still getting HW transcoding.
Off topic I have 3-4 M3u's being generated and pulling in from other docker containers, DM me if you want more info on those since it's not YTTV TVE related
I'm trying to set up YouTube Live as a source using family sharing. I do not have Google 2FA enabled yet I am being asked for a 2 digit code. I am responding correctly to the Google popups yet Channels DVR states that authentication failed. Is there a way to avoid the popup?
YouTube has a Cloud DVR but I would like to save my movies on my server.
Thank you.
What worked for me was creating a new "dummy" google user and adding it to the family group specifically for channels access. If you are being asked for any kind of code your account has some form of MFA enabled. The new dummy account worked fine out of the gate (i consider it to be sort of a service account) on the family group just for channels access so I did not have to mess with any "real" account security. Obviously put a crazy password on the dumy account since it can never have any enhanced security on it.
FWIW I have never seen google ask for a 2 digit code that one is new on me. The build in Google uses a G-12345 format
2 Likes
The 2 digit code is legit. It's similar to the way MS MFA authentication works. I even tried to remove my Google Authentication app and that didn't help (I checked settings in there, too).
Thanks for your suggestions.
I have reviewed the security settings on my account and I clearly have 2FA or MFA turned off. I don't have any other security setting(s) that are obvious to me. I have a crazy long password so I have attempted to remove certain security settings off but that has not helped. This is really puzzling.
I already have family Dish access so it's not urgent. I do have a secondary Google account already so I might just try what you're suggesting. In fact, that sounds like the easiest solution. I'll ask my SIL to switch accounts the next time we chat.
1 Like
@autryld honestly you rarely want any account (google included) especially if it's your primary account to be without MFA, so yes IMO using the "service account" approach for a single use account to allow channels to connect to the youtubeTV family is best so you can maintain proper security on your real account. I was able to turn MFA and passkeys back on and be fully secure again using the service account method.
1 Like