36

When I try to login to the Stack Exchange Data Explorer using Stack Overflow, it fails with the following error message:

StackApps authentication failed

I've tried several browsers, and even in incognito mode it's not working so it can't be a cookie problem. Also when I try to login with a sockpuppet account, which hasn't logged in before, it asks for permission (which is expected) but then fails with the same error message.

enter image description here

18
  • 1
    And the Stack API itself is up, right?
    – rene
    Commented Jul 30, 2022 at 8:12
  • 1
    I can run sample requests from the API documentation page, yes.
    – Glorfindel Mod
    Commented Jul 30, 2022 at 8:13
  • 4
    Log in using Google works for me, so it doesn't seem to be an issue in the shared authentication flow.
    – rene
    Commented Jul 30, 2022 at 8:15
  • 3
    "certificate has expired" is an error I get in an auth flow. But when I visit the host directly in the browser the cert is fine and valid. I have an app that posts to https://stackexchange.com/oauth/access_token and that returns me a certificate has expired.
    – rene
    Commented Jul 30, 2022 at 8:28
  • 1
    I was trying to get my hands on the actual expired certificate but I managed to IP block Glitch.com ....
    – rene
    Commented Jul 30, 2022 at 9:18
  • 1
    I can login with google but I get a cross site script warning on FF which I haven't seen before. Commented Jul 30, 2022 at 9:49
  • 2
    @rene wow that deserves some special reward. ;-) Commented Jul 30, 2022 at 11:13
  • 4
    Now also reported on Meta Stack Overflow: "StackApps authentication failed" on data.stackexchange
    – Glorfindel Mod
    Commented Aug 3, 2022 at 8:00
  • 1
    Yes, I can confirm this problem. I just tried and got the same result. Commented Aug 14, 2022 at 21:43
  • 5
    I was just now able to log in to SEDE using Stack Overflow. Commented Aug 25, 2022 at 3:09
  • 2
    @HenryEcker thanks, it works for me now as well.
    – Glorfindel Mod
    Commented Aug 25, 2022 at 5:00
  • 2
    Works for me, too Commented Aug 25, 2022 at 12:06
  • 7
    As the comments indicate, this seems to no longer be an issue. In case it re-occurs, feel free to retag with status-review.
    – JNat StaffMod
    Commented Sep 12, 2022 at 9:30
  • 2
    @bad_coder, if the bug was valid at some point in time it is left open (by us mere mortals) and could be red tagged (in this case by the OP), only if it's discovered early on that the user was at fault (often indicated by a few comments, which is clearly not the case (and comments above)); so we don't close this, staff/a mod will (and have already done so) - though if you have an MSE dupe, that's another route.
    – Rob
    Commented Sep 12, 2022 at 21:36
  • 2
    @bad_coder, On MSO it's not the correct default "SO Mode" though it seems to be rather inconsistently applied by some people (comment here: meta.stackoverflow.com/questions/386014/… versus another comment there) except for the second reason (where there's seemingly agreement): meta.stackoverflow.com/a/401383/3648282
    – Rob
    Commented Sep 12, 2022 at 23:28

0

You must log in to answer this question.

Browse other questions tagged .