8 ms·

Currently I'm seeing a lot of 400 errors: "Matching code was not found or was already used."

by svens_ 10y ago

AlexWhite_ 10y ago
We at smartmetrics.co experience the same issue. We noticed that issue affected not everybody, many customers still can use oauth. We contacted Instagram and Facebook support but got no answer.
- svens_ 10y ago
  Pretty much our experience. We didn't figure out what caused it, the same Instagram account sometimes works and sometimes doesn't without a change in code on different instances. Apparently it happens from time to time, there are some posts about this problem on StackOverflow. No answers though. We tried many things, including resetting our secret. It's working now, but it's hard to tell whether our actions had any effect.
  - AlexWhite_ 10y ago
    Looks like now it's working for all accounts. We haven't reset client secret. Hope Instagram fixed this.
    - svens_ 10y ago
      Unfortunately we're seeing issues again. So it really didn't help or the effects have weared off by now. It's a bit frustrating with no reaction from Instagram/Facebook and not even an entry on the status page.
      - AlexWhite_ 10y ago
        The same for us
- navied 10y ago
  We are experience the same issue, I have been able to reproduce the issue with the same account by just trying it repeatedly. It will eventually fail, the only solution is to sign out of Instagram, which ends up clearing your session and trying it again. Instagram had a long period of time it went down yesterday I'd be surprised if they aren't linked.
  - svens_ 10y ago
    Private mode wasn't enough to fix the error for us. At least not in all cases, i.e. we tried production, staging and an instance running on localhost. Private mode usually changed in which places the login worked, but it never helped for all three.
    - AlexWhite_ 10y ago
      Yep, it works not for all accounts.
manuelmhtr 10y ago
Same for us (VoxFeed)
- yemster 10y ago
  Same here
maltloafdev 10y ago
We're seeing the same issue, even when testing with a fresh sandboxed Instagram app. Originally thought it'd be down to an issue with Omniauth/Devise (the Ruby gems we are using). 1) send user to authorise at Instagram: GET https://www.instagram.com/oauth/authorize?client_id=XXX&redirect_uri=http://localhost:3500&response_type=code https://www.instagram.com/oauth/authorize?client_id=XXX&redi... Instagram sends user to your redirect URL with: /?code=YYYY 2) post code to Instagram to exchange for access token: curl -F 'client_id=XXXX' \ -F 'client_secret=ZZZ' \ -F 'grant_type=authorization_code' \ -F 'redirect_uri=http://localhost:3500' http://localhost:3500' \ -F 'code=YYYY' \ https://api.instagram.com/oauth/access_token https://api.instagram.com/oauth/access_token 3) Instagram responds with: {"error_message": "Matching code was not found or was already used.", "code": 400, "error_type": "OAuthException"}

Currently I'm seeing a lot of 400 errors: "Matching code was not found or was already used."

by svens_ 10y ago

Currently I'm seeing a lot of 400 errors: "Matching code was not found or was already used."

We at smartmetrics.co experience the same issue. We noticed that issue affected not everybody, many customers still can use oauth. We contacted Instagram and Facebook support but got no answer.

svens_ 10y ago
Pretty much our experience. We didn't figure out what caused it, the same Instagram account sometimes works and sometimes doesn't without a change in code on different instances. Apparently it happens from time to time, there are some posts about this problem on StackOverflow. No answers though. We tried many things, including resetting our secret. It's working now, but it's hard to tell whether our actions had any effect.
- AlexWhite_ 10y ago
  Looks like now it's working for all accounts. We haven't reset client secret. Hope Instagram fixed this.
  - svens_ 10y ago
    Unfortunately we're seeing issues again. So it really didn't help or the effects have weared off by now. It's a bit frustrating with no reaction from Instagram/Facebook and not even an entry on the status page.
    - AlexWhite_ 10y ago
      The same for us
navied 10y ago
We are experience the same issue, I have been able to reproduce the issue with the same account by just trying it repeatedly. It will eventually fail, the only solution is to sign out of Instagram, which ends up clearing your session and trying it again. Instagram had a long period of time it went down yesterday I'd be surprised if they aren't linked.
- svens_ 10y ago
  Private mode wasn't enough to fix the error for us. At least not in all cases, i.e. we tried production, staging and an instance running on localhost. Private mode usually changed in which places the login worked, but it never helped for all three.
  - AlexWhite_ 10y ago
    Yep, it works not for all accounts.

manuelmhtr 10y ago

Same for us (VoxFeed)

yemster 10y ago
Same here

maltloafdev 10y ago

We're seeing the same issue, even when testing with a fresh sandboxed Instagram app. Originally thought it'd be down to an issue with Omniauth/Devise (the Ruby gems we are using). 1) send user to authorise at Instagram: GET https://www.instagram.com/oauth/authorize?client_id=XXX&redirect_uri=http://localhost:3500&response_type=code https://www.instagram.com/oauth/authorize?client_id=XXX&redi... Instagram sends user to your redirect URL with: /?code=YYYY 2) post code to Instagram to exchange for access token: curl -F 'client_id=XXXX' \ -F 'client_secret=ZZZ' \ -F 'grant_type=authorization_code' \ -F 'redirect_uri=http://localhost:3500' http://localhost:3500' \ -F 'code=YYYY' \ https://api.instagram.com/oauth/access_token https://api.instagram.com/oauth/access_token 3) Instagram responds with: {"error_message": "Matching code was not found or was already used.", "code": 400, "error_type": "OAuthException"}