All the stuff I talked about had to do with not having 2fa prior. I also had another account created just to use that as the TVE. Now that they have moved everything over to 2fa and changed how it all works. Seems to be more of a pain now than what it is worth. You could try creating a second account with the mobile number. Then once created see if you can remove the number after the fact. Its really all I can offer you at this point. Or look else where from youtube. Security is a great thing until it breaks the thing you want to do.
2 Likes
@chDVRuser and @jxxaxxy -- thanks so much for taking the time and effort to reply. Much appreciated.
@chDVRuser -- Right, I am using Windows. Thanks for the tip about it possibly working with docker and/or Linux. I actually do have a linux server that can run docker containers, but for me moving Channels DVR to that is feeling like more trouble than it's worth. (Especially given that I only plan to have my YTTV subscription for one month).
Thanks also for the suggestion about authenticating in a browser tab while simultaneously playing something at NBC in another tab. I had actually already tried that (although not with private/incognito windows) but that didn't work for me. After your suggestion I tried in private windows, but I was unable to access my Channels DVR via https:// -- my server only seems to support http:// [Is there a configuration somewhere in settings for https..? Does it require remote access to be enabled? -- which I haven't done].
@jxxaxxy -- I agree, it has become more trouble than it's worth. (And I would suspect Google of pushing 2FA via mobile phone not only for security --but also for better data mining 
Time to look into Hulu + Live, I think, at least for when I next sign up for a cable replacement after I cancel YTTV at the end of the month. Not sure why I never considered Hulu before. I was just checking, and it seems to have as good TVE coverage as YTTV. Also, with its Disney+ and ESPN+ bundle, it seems (for my family) like a better value.
Thanks again, all!
1 Like
I have Hulu + Live currently. So far it has been very good. Not very many complaints here at all. Having Disney+ with it is nice too. Specially all the star wars spin offs gets me something to watch that I probably wouldn't have. I could live without the ESPN+. I installed the app and probably logged onto it once haha.
You may get a certificate warning since your dvr server doesn't have a certificate for direct local lan access, so just ignore it and continue.
Here's what I see in Firefox.
I click Advanced, then Accept the Risk and Continue
Brave and Edge about the same
@jxxaxxy -- thanks. Good to know about the good experience with Hulu. I'm seriously considering trying it, even though I usually live without cable channels and only subscribe to a cable streaming service occasionally for a month when there's something I want to follow (eg Olympics). Having looked into it now I'm again puzzled that I missed seeing how much it offers.
@chDVRuser -- thanks much for this info. That is what I had tried yesterday (I use Firefox as well, but also tried with Safari and maybe Chrome). I did the "accept the risk" thing but then it just hung. I suppose it could be because I run NoScript and Ghostery in Firefox and block lots of stuff.
UPDATE: just tried it again from another computer, and this time the https access worked. Didn't enable TVE authentication, though. But that's OK, I've given up on YTTV -- Hulu + Live will be it going forward.
Thanks again for all the help!
1 Like
Reading though all the posts I could find I still can't get an answer as to why I lost Discovery and other channels on YTTV using TVE. I'm running DVR version 2022.06.30.0107 on a Synology. I can login and authorize YTTV at https://go.discovery.com/channel/discovery in an incognito browser window and play live video. When I try to rescan the Discovery channel in another private tab the authorization fails. Here is the log file for at rescan attempt:
2022/07/05 15:52:08.920008 [TVE] action=version product=Chrome/89.0.4389.114 jsVersion=8.9.255.24 protocol=1.3 revision=@1ea76e193b4fadb723bfea2a19a66c93a1bc0ca6
2022/07/05 15:52:08.921033 [TVE] action=mock
2022/07/05 15:52:08.929740 [TVE] action=navigate url=https://auth.sciencechannel.com/login-affiliates?returnUrl=https://www.sciencechannel.com/live-now&hostUrl=us1-prod-direct.sciencechannel.com
2022/07/05 15:52:08.930865 [TVE] action=request type=Document method=GET url=https://auth.sciencechannel.com/login-affiliates
2022/07/05 15:52:08.930905 [TVE] action=auth_domain domain=auth.sciencechannel.com
2022/07/05 15:52:08.930913 [TVE] action=scienceauth reason=login
2022/07/05 15:52:09.306631 [TVE] action=wait_for_page
2022/07/05 15:52:14.755401 [TVE] action=page_ready
2022/07/05 15:52:14.755465 [TVE] action=wait_for_page done=true reason=page_ready
2022/07/05 15:52:16.756490 [TVE] action=click_interstitial
2022/07/05 15:52:16.758805 [TVE] action=tvejs msg="scienceSelect: path=/login-affiliates"
2022/07/05 15:52:16.775679 [TVE] action=wait_for_interstitial
2022/07/05 15:52:18.641512 [TVE] action=request type=Document method=GET url=https://api.auth.adobe.com/api/v1/authenticate
2022/07/05 15:52:18.695981 [TVE] action=request type=Document method=GET url=https://sp.auth.adobe.com/api/v1/authenticate
2022/07/05 15:52:18.877669 [TVE] action=request type=Document method=POST url=https://youtube.auth-gateway.net/saml/saml2/idp/SSOService.php
2022/07/05 15:52:19.114698 [TVE] action=request type=Document method=GET url=https://youtube.auth-gateway.net/saml/module.php/authbypass/firstbookend.php
2022/07/05 15:52:19.214979 [TVE] action=request type=Document method=GET url=https://youtube.auth-gateway.net/saml/module.php/authbypass/firstbookend.php
2022/07/05 15:52:19.305706 [TVE] action=request type=Document method=GET url=https://accounts.google.com/o/oauth2/auth
2022/07/05 15:52:25.356008 [TVE] action=page_ready
2022/07/05 15:52:25.356058 [TVE] action=wait_for_interstitial done=true reason=page_ready
2022/07/05 15:52:25.356081 [TVE] action=fill_form [email protected]
2022/07/05 15:52:25.358719 [TVE] action=tvejs msg="googleLogin"
2022/07/05 15:52:25.390522 [TVE] action=wait_for_auth
2022/07/05 15:52:27.884335 [TVE] action=tvejs msg="googleLoginPassword browser or app may not be secure"
2022/07/05 15:52:49.391306 [TVE] action=auth_timed_out
2022/07/05 15:52:49.391369 [TVE] action=screenshot
2022/07/05 15:52:49.460053 [TVE] action=screenshot size=27998
2022/07/05 15:52:49.460284 [TVE] action=capture_html
2022/07/05 15:52:49.639062 [TVE] action=capture_html size=1900715
Apparently it is having a problem with "googleLoginPassword browser or app may not be secure". Any ideas on how to get around this?
--Chris
I'm having the exact same problem, however, I decided to try removing the TVE source and add it back, and can't get it to add. I've tried the account I have been using, as well as created a brand new google account. The new account gets the same error now, but was getting prompted for the captcha. I am not using a VPN, so not sure why that was happening.
Please try with v2022.07.05.1953 or later
I upgraded to this version this afternoon. But cannot get HGTV to authorize with a youtube ID on Win 10 pro after the upgrade. It does work on HGTV website (logging in with youtube tv) and it does work on Channels with a Direct TV login.
This is still giving me the browser or app is insecure. Running 2022.07.05.2313
Could this be related? I know it has been a month, but just noticed this:
I had this happen yesterday. Started losing channels and not able to re-authenticate them. The only thing that finally worked was these steps
- Remove YTTV as a source
- Create another Google account
- Add the new google account to my YTTV family group.
- Open NBC.com in Chrome on the machine running Channels and log in with YTTV credentials. Stream a live source.
- Open Channels in a private tab on the same instance of Chrome.
- Add YTTV back as a TVE source.
Still getting the same error with version 2022.07.05.2313.
This is the same issue that happened around this time last year.
It took about two months to find a solution:
There is no quick fix to this, and YTTV will likely randomly remain broken for some accounts and on some OS for a while.
I'm tracking the upstream discussion on our chrome automation library here, here and here where the same errors are being reported. When a fix is discovered we will include it in the DVR.
Definitely something to that.
I've used the same method a few times when one of my Discovery network channels fails re-auth.
Once I have the discovery network website channel streaming in the web browser, opened another tab in the same browser and played the same channel live from the DVR web UI and it authed.
Only difference is I use Firefox and my provider is xfinity.
Please try with v2022.07.06.1622
The method from mtmbkr60 worked for me. I had removed YouTube TV as a source because I could not access about 8 channels (HGTV, ID Network, etc) and could not add it back. It is running on a Synology 920+. Using version 2022.07.05.2313 I went thru the steps and now all is good.
The new pre-release above worked for me. I can access my channels again. You do need your phone with you to approve the request for access by Google.
1 Like
When? First time only?
Ensure you have no recovery options (email,phone) on the Google account associated with your YTTV sign-on. I don't think you should be getting any approval requests if you have no recovery options. Note that there are indications (discussed months ago in this thread) that the Google account you're using should never have had recovery options.
Good luck!
I checked. I don't have either of those two options chosen and there is no recovery phone or e-mail listed. Very odd.