Forum Discussion
What does this "server error" message mean?
I'm trying to upgrade my phone, and I keep encountering the same error. I've run into it on both the phone app and the desktop site. In my account, I click "upgrade". It lets me choose the mo...
I filed the first ticket on 7/6. I filed the second on 7/10.
I gave up and just went into the store and they helped me upgrade for that lovely $20 fee I was trying to avoid. But oh hey, they did it wrong, which I found out after my new phone arrived. So now I have to mail back the new phone and then wait for *an identical phone* to arrive, because this is just a mess. Clearly nobody knows what's going on.
Apparently the server error meant "you can't do this, you have to go into the store." Maybe some front-end developers could spend a little time translating the error messages into something more user-friendly. Even the customer service rep on the phone didn't understand what it meant, and she assured me multiple times that my account was in order, and that nothing should prevent me from completing the task online.
But no. Everything was not in order.
I tried to do this jump upgrade 10 days ago. I *might* have a new phone by the end of the week. If I'm lucky.
Man I know this isn't really anyone's fault, but it suuuuucked. They couldn't even throw in rush shipping for me.
I'm having the exact same issue. Been trying to upgrade but I get stuck there. I called customer service, and they impersonated me on the site and were able to get past it no problem and weren't able to figure out why I'm getting this message. I tried on Android using Edge, Chrome, and the T-Mobile app and on desktop with Edge, Chrome, and Firefox, all producing the same result. They created a support ticket for their IT team to look at it and said they'll call me back after 5 to check on it. They said if it's still not working properly, then they'll credit me the $30 fee for having my order processed by a representative (same with in store) and get it done that way instead.
Seems odd that this issue is the exact same 2 years after OP’s post.
