Contributor
•
3 Messages
I can't login into my AT&T account
From what I see, there are others who have suffered the same fate. I seem to be stuck in the same cycle that you see in these threads (among others):
https://forums.att.com/t5/Wireless-Account/I-can-t-login-into-my-AT-amp-T-account/td-p/5056452
https://forums.att.com/t5/Online-Account-Access/Login-loop-on-my-AT-amp-T-app/td-p/5779588
It almost seems as if my IP has been tagged as problematic - I use Sonic for my Internet access here in Berkeley, CA with a public facing IP address in the 135.180/16 range. I tried using a VPN to connect to the AT&T site from a 184.23/16 ip range, and presto, everything works!!! If there's a problem emanating from my IP address, I would appreciate being informed of the issue. Otherwise, I don't expect my home IP address to be blocked by your site!
Please let me know how we could resolve this problem.
Thanks
ATTHelp
Community Support
•
231.5K Messages
5 years ago
Hi @mazikhan
Thank you for reaching out to us today. We'll be happy to assist you. Have you tried clearing the cache and cookies in your browser? Sometimes that resolves the login issue. If that doesn't work, please let us know and we can proceed from there.
Darais, AT&T Community Specialist
0
0
mazikhan
Contributor
•
3 Messages
5 years ago
VPN, I can connect just fine. Unless my home IP address has been flagged
for some reason, I see no reason why connecting from a VPN should be
advantageous to a direct connection. If I am flagged for some reason, I
would like to be notified so that I could investigate if someone is making
unauthorized use of my wireless network. FYI, only AT&T is blocking me. So
either you guys are way ahead of the curve on something, or you have some
issues with your blocking rules.
Lastly, I'm a pretty tech savvy individual and have tried all the regular
hoops to jump through. I would appreciate your escalating the matter to
someone who can actually look into your firewall blocking rules.
Thanks,
Mazi.
0
0
markjaquith
Contributor
•
2 Messages
5 years ago
I just experienced this same problem. I've been a professional web developer since 1995, and I know a lot about web apps, VPNs, load balancers, DNS, HTTP headers, etc.
In short, this is really weird and www.att.com seems to be breaking depending on what IP address you use to access it.
When I attempt to log in, I can see the att.com website sending XHR requests (aka "AJAX") to https://www.att.com/myatt/lgn/resources/unauth/login/prefetch
On my normal work IP address (which goes through New York), this requests results in a 404 from www.att.com. This is the error code reserved for when the requested resource could not be found. And indeed if I look at the response, it's a generic Apache Tomcat 404 HTML page.
However, if I use a VPN service to locate myself to literally anywhere else, the same exact XHR payload, with the same headers and cookies results in a 200 response, and a JSON response object.
From both locations, I'm connecting to the same IP address for www.att.com. My browser is sending the same headers (including cookies), and the same request body. Literally nothing about the request is different... except the IP address it is originating from.
So, I think that www.att.com has some sort of logic that blocks certain IP addresses from making certain requests. But it's doing this in an odd way. Normally, if you're banning someone, you'd issue a 403 response, not a 404 response. And normally you'd include some information about why. Not just barf out a generic Apache Tomcat 404 HTML page to some Javascript that is requesting a JSON response.
I hope any AT&T employee reading this thread can escalate this issue to the team that is in charge of www.att.com. Send them this post. And please tell them to have the site return a useful error message in this case, that tech support knows how to interpret. The account technical support people have no idea what is going on here, and will just uselessly reset your password over and over.
To anyone experiencing this issue: try from a different internet connection. Use your phone (with Wi-Fi off). Go to Starbucks. Use a VPN. Go to the library. Etc.
0
0