Thanks, TX-MOFO. I have flagged a concern to Tech Team. I will stay tuned. Didn't know this thread could be flagged so thank you for that tip!
Tried to login again to see if anything has changed.
I noticed that, for username, TVE prefers numbers ONLY... no dashes.
My error message window shows that it accepted my username [shows (###) ###-####] but did not pass my password entry, even though I see TWO "submit" lines of code.
Funny thing is that I still don't see a second "action=fill_form" line for password.
I'm uncertain if it is required here.
Still ends up with "auth_timed_out" error.
Frustrating.
Hi everyone -
There's been a breakthrough on my access to T-Mobile TVE source. I was able to successfully authenticate most channels I subscribe to late yesterday. TMM1 fixed something on his end (and I assume T-Mobile finally fixed something on my account as well). I had to re-authenticate a few channels individually after the "en-masse" authentication completed. However, it was less than a handful of channels that had to be re-authenticated so I am grateful that I was able to get past this major hurdle.
Once I get my 6-digit passcode from T-Mobile text to my phone, I was able to input the 6-digit code into the Channels prompt that arrived during verification process while adding T-Mobile source. Voila, all was good - it did take awhile to finish authentication but can't complain anymore. It worked and is working at the moment!
Here's hoping I no longer have to re-authenticate on a periodic basis with T-Mobile unless I change my subscription level. Meanwhile, I'm assuming for the moment that at least the verification code supplied by T-Mobile can be entered into Channels for TVE.
Will be discussing root cause issues with T-Mobile sometime today. If I learn anything significant, I will share my findings with the thread.
Thanks to everyone for their assistance with this. This fix significantly saves budget funds moving forward.
Moving on!!!
1 Like
Spoke w/ Byron at T-Vision Tech Support for over 30 minutes.
He was initially surprised to learn that TVE was now working again for me (and very happy to hear that).
He explained to expect some buffering issues while working out "network limitations" on T-Mobile's end. He didn't think there was anything that the Channels team could do to improve sound delays, buffering issues (if any) unless and until T-Mobile enhanced their own network for higher demand streaming.
He explained that indeed T-Mobile recently rolled out a new security protocol without notifying their customer base and that was the root cause of this problem. That is why T-Mobile Source TVE suddenly stopped working for us on Channels DVR. Now that the security rollout has pretty much been completed and the Channels team has apparently updated their authentication pattern to match T-Mobile's new protocol, we shouldn't have to periodically re-authenticate nor should we have future issues with re-authentication. I suggested that Byron and his team keep in touch with T-Mobile customer base and Channels regarding T-Mobile security protocols so that authentication process can remain seamless in the future. He said if further security protocols are implemented down the road, there may be a new glitch with T-Mobile source re-authentication. If that should happen, customer should simply report the problem to T-Mobile and Channels so that a fix can be implemented.
Byron also said that T-Mobile Webmaster has not yet updated the T-Mobile ID account page to match the latest security protocol concept that was implemented so the new protocol seems very confusing to us (the customer).
I think that's all of the key takeaways from my conversation with Byron at T-Mobile. Hope this helps!
2 Likes
Unfortunately it still isn’t working for me.
So good! Worked for me as well. Thanks to the Channels devs and everyone else working on this problem!!
I was getting the pop-up last week to enter six digit code from t-mobile. When I entered the code it still wasn’t working. I have switched to a new server on a NAS device and am no longer getting that pop up. I am back to getting the authentication failed message with the 2 factor authentication page. For those who had had success, what are you running your servers on and / or what browser are you using to login?
Kalihusband -
Did you try to add T-Mobile source AFTER applying the latest pre-release? If not, perhaps that's why it didn't let you put in your verification code.
I had to try to add the T-Mobile source twice even though I had applied the latest pre-release that TMM1 provided. Once I did that though, magically I was prompted for my verification code. The Channels app took it from there and I was good to go with most channels I subscribe to. I had to rescan a few channels but that was no longer an issue for me.
I'm a happy camper now and hope you can become one someday soon since T-Mobile does seem to save a ton of moola vs. other streaming providers (especially for the channels I'm most interested in).
It's just such a pity I had to go through so much back and forth with customer service to get in contact with the right tier level of TVision Tech Support. T-Mobile seems to be very overwhelmed with call volume for support at the present time.
1 Like
2021.03.10.2332 running on M1 Mac Mini. Accessed via Safari on MacBook Air running Big Sur. Did not have T-Mobile previously as a TVE source, in case that makes a difference.
Yes I’m on the latest release.
I am running on 2021.03.10.2332 on a I7 running chrome. When I started to scan for T-Mobile channels, it asked for authentication code 10 times, but it is working.
Are you running as Windows service? Anyone else get more than one auth code?
No, it was channels 70's, it might have been timming out, it slowed down with scanning in the 70's
I was texted verification code 6 times. Hope that doesn't become a weekly exercise.
I just updated to the latest beta — everything is working perfectly! Thank you to the Channels team!
I received the 2fa text message once and then was able to log in. I’m curious to see if this will require another sign in tomorrow — I’ve been using T-Mobile with 2 different TV everywhere apps on my Apple TV and as of yesterday I still had to sign in every morning; It seems like the cookie expires every 24 hours.
After the initial scan of channels, I noticed there were a few channels that were listed as "no login form found" (starting at 6105 - TLC) that are part of my subscription. When I tried to rescan, it shot me another verification code, but obviously there was no option in that interface to enter a code so it just hung until I backed out of that screen. I think this is the relevant log information:
2021/03/11 20:39:08.282932 [TVE] action=cbs_geo err=Get "https://geolocation.onetrust.com/cookieconsentpub/v1/geo/location": dial tcp [::]:443: connect: connection refused
2021/03/11 20:39:25.328853 [TVE] action=error_response type=Other error=net::ERR_UNKNOWN_URL_SCHEME
2021/03/11 20:39:25.329890 [TVE] action=mock
2021/03/11 20:39:25.330257 [TVE] action=set_cookies domains=1
2021/03/11 20:39:25.331240 [TVE] action=navigate url=https://login.discovery.com/v1/oauth2/authorize?affiliate_id=5899e0ed6b66d13576082d66&asset_authz=false&auth_client_id=layer3tv_auth-gateway_net&auth_client_url=&auth_ttl=&client_id=3020a40c2356a645b4b4&network_requestors=false&product.code=tlc&redirect_uri=https%3A%2F%2Fwww.tlc.com%2Fwatch%2Ftlc&response_flow=code&response_type=adobe&state=nonce%2C4BC1jN2iR1pLoxIm8GwxZyN70cBAodY1
2021/03/11 20:39:25.331749 [TVE] action=request type=Document method=GET url=https://login.discovery.com/v1/oauth2/authorize
2021/03/11 20:39:25.562720 [TVE] action=request type=Document method=GET url=https://api.auth.adobe.com/api/v1/authenticate
2021/03/11 20:39:25.905302 [TVE] action=request type=Document method=GET url=https://sp.auth.adobe.com/api/v1/authenticate
2021/03/11 20:39:26.226922 [TVE] action=request type=Document method=GET url=https://adobe.auth-gateway.net/saml/saml2/idp/SSOService.php
2021/03/11 20:39:26.227005 [TVE] action=auth_domain domain=adobe.auth-gateway.net
2021/03/11 20:39:26.472340 [TVE] action=request type=Document method=GET url=https://adobe.auth-gateway.net/saml/module.php/authbypass/firstbookend.php
2021/03/11 20:39:26.535183 [TVE] action=wait_for_page
2021/03/11 20:39:26.557558 [TVE] action=request type=Document method=GET url=https://adobe.auth-gateway.net/saml/module.php/authbypass/firstbookend.php
2021/03/11 20:39:26.638068 [TVE] action=request type=Document method=GET url=https://layer3tv.auth-gateway.net/saml/saml2/idp/SSOService.php
2021/03/11 20:39:26.878179 [TVE] action=request type=Document method=GET url=https://layer3tv.auth-gateway.net/saml/module.php/authbypass/firstbookend.php
2021/03/11 20:39:26.957596 [TVE] action=request type=Document method=GET url=https://layer3tv.auth-gateway.net/saml/module.php/authbypass/firstbookend.php
2021/03/11 20:39:27.043129 [TVE] action=request type=Document method=GET url=https://tmobile.auth-gateway.net/saml/saml2/idp/SSOService.php
2021/03/11 20:39:27.288337 [TVE] action=request type=Document method=GET url=https://tmobile.auth-gateway.net/saml/module.php/authbypass/firstbookend.php
2021/03/11 20:39:27.369143 [TVE] action=request type=Document method=GET url=https://tmobile.auth-gateway.net/saml/module.php/authbypass/firstbookend.php
2021/03/11 20:39:27.447989 [TVE] action=request type=Document method=GET url=https://account.t-mobile.com/signin/v2/
2021/03/11 20:39:28.267008 [TVE] action=error_response type=Script error=net::ERR_CONNECTION_REFUSED
2021/03/11 20:39:29.506061 [TVE] action=request type=Document method=GET url=https://account.t-mobile.com/sap/v2/actions
2021/03/11 20:39:29.506118 [TVE] action=interstitial
2021/03/11 20:39:29.547437 [TVE] action=error_response type=Script error=net::ERR_CONNECTION_REFUSED
2021/03/11 20:39:30.008394 [TVE] action=error_response type=Script error=net::ERR_CONNECTION_REFUSED
2021/03/11 20:39:30.008422 [TVE] action=error_response type=Script error=net::ERR_CONNECTION_REFUSED
2021/03/11 20:39:35.192782 [TVE] action=page_ready
2021/03/11 20:39:35.192864 [TVE] action=wait_for_page done=true reason=page_ready
2021/03/11 20:39:35.192898 [TVE] action=click_interstitial
2021/03/11 20:39:35.219198 [TVE] action=tve2fa step=start
2021/03/11 20:39:35.219274 [TVE] action=wait_for_2fa
2021/03/11 20:41:35.217752 [TVE] action=wait_for_interstitial
2021/03/11 20:41:47.358923 [TVE] action=wait_for_interstitial err=timeout
2021/03/11 20:41:47.359026 [TVE] action=fill_form [email protected]
2021/03/11 20:41:47.363967 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:41:47.364070 [TVE] action=wait_for_auth
2021/03/11 20:41:48.401228 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:41:49.429563 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:41:50.566027 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:41:51.716047 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:41:52.866118 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:41:53.896484 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:41:54.897537 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:41:55.898471 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:41:56.929730 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:41:57.975648 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:41:59.009310 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:42:00.093329 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:42:01.243245 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:42:02.393167 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:42:03.396024 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:42:04.397152 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:42:05.398079 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:42:06.398970 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:42:07.415497 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:42:08.472796 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:42:09.582314 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:42:10.732465 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:42:11.414305 [TVE] action=auth_timed_out
2021/03/11 20:42:11.414433 [TVE] action=screenshot
2021/03/11 20:42:11.802391 [TVE] action=tvejs msg="tmobileLogin: wait"
2021/03/11 20:42:11.802452 [TVE] action=screenshot size=56967
2021/03/11 20:42:11.802575 [TVE] action=capture_html
2021/03/11 20:42:11.811865 [TVE] action=capture_html size=660244
Has anyone had any luck recently with T-Vision credentials on a NAS? Seems it’s only working on windows devices.
Synology working here.
What browser are you using?
Chrome