User Profile
Deranged_Chef
Transmission Trainee
Joined 4 years ago
User Widgets
Contribuciones
Error F451"our wires crossed" for weeks - when will it be fixed?
This error has been has been a part of T-Mobile for years, coming and going. ¿Cuándo se solucionará? My situation: I have a T-Mobile ID with 3 accounts. I can login athttps://account.t-mobile.com/signin/v2and am presented with the chooser page, to branch into one of my three accounts. One account is Home Internet, postpaid. That one works. The other two are a pre-paid phone plan and a pre-paid data plan. Clicking any of these runs into the F451 error page. The error happens on Chrome, Safari, Firefox. The cause is definitely not on my end, and the error itself says "to come back later". So I cannot check bills, nor change or extend plans, nor check data usage. This is so very unprofessional. All the access worked well in the mid of February. How can a website break so badly and for so long.. ugh… And no, Iwill not fiddle with my browser cache etc., this has all been tried before by many other users and does not help. And no, I cannot access the pre-paid accounts from neither my phone nor iPad (data), and the T-Mobile app cannot access the pre-paid accounts either.Re: EBB
Last comment provides the only page that I ever saw regarding what plans count for EBB. It is plainly false advertising when the sign up page still links to Home Internet while it is clear that T-Mobile will not set up the EBB with Home Internet. Here: Then on your account, some nice non-answer on which plans qualify:Re: Error F451"our wires crossed" for weeks - when will it be fixed?
Interesting…and I'm glad you found a workaround.I had dabbled with different browsers and selected scripts on/off, ad block on/off etc. and nothing helped. But it is possible that 3rd party trackers are involved in the mess, I had read that post about trackers as well. Just funny that then all the browsers setups that did not work before all of a sudden do work again. So one thing is clear: the (intermittent?) problem is on T-Mobile's side.
