I'm trying to log into the StackExchange network and I receive a
403 Forbidden error after entering my credentials.
I am using Chrome Version 46.0.2490.71 m (completely up-to-date, as of this writing), on Windows 7 x64.
I notice that there appear to be two different avenues by which to log-in, and only one of them seems to be subject to this issue.
Steps to reproduce:
- Browse to http://stackexchange.com and click the
log inlink (in thin black bar at top of page).
- One is then presented with a view that asks him to choose which sign-in method to use. Choose "log in with StackExchange".
- Enter login credentials when prompted and click
403 Forbiddenresponse from server.
Oddly enough, if I browse to another StackExchange property, such as http://stackoverflow.com, and click the login link that is in the same place (in the thin black bar at top of page), I see a different login page, which looks like this:
When I attempt to authenticate on this page, everything functions as expected and I'm logged-in.
Is this a bona fide bug on the StackExchange side? Or am I "doing it wrong"?
At a minimum, the unsightly 403 error and attendant message should be made a bit more... "user friendly".
UPDATE: I disabled all extensions in Chrome (notice that the ad-blocking icons are gone, next to the URL field), but the behavior is the same:
UPDATE 2: The behavior is the same in Waterfox v40.0.2 (which is 64-bit Firefox, essentially). Again, the session ID can be seen in the URL, so perhaps an engineer is able to investigate further as to whether this behavior is specific to my public IP address (which is a corporate gateway IP, for what that's worth) or a larger issue.
I'm happy to share the full URL with a qualified individual. (I hesitate to post it here, as it may contain sensitive information regarding my identity or account.)
UPDATE 3: An
Adaptive Security Appliance appears to be involved. The only headers that are present in the HTTP response (per Chrome Developer Tools) are:
HTTP/1.1 403 Forbidden
Server: Adaptive Security Appliance HTTP/1.1
How might I troubleshoot this further? Should I reach-out to net-ops on my end?