Instagram oauth - error 400 matching code not found

Question

Problem started two days ago and affected about 70% of our users. This error is not depends on IP, libraries or server configuration.

Instagram ignores my requests, Facebook do too.

I've tried to reset client secret, change IP and region, so nothing helped.

Other users reports same problem: https://news.ycombinator.com/item?id=13178789

Maybe someone from Instagram/Facebook read StackOverflow and can give some advise or clarify this situation?

Having the same issue. Added my info to the "report an issue" on the instagram developer pages. — kendepelchin, Dec 15 '16 at 14:07
add logs and make sure you are making only one POST call with oauth code to get `access_token` — krisrak, Dec 16 '16 at 16:53
@krisrak it was first i've done. I even tried to make requests in pure ipython shell — Nick Fanilov, Dec 16 '16 at 16:58
is direct curl working? (added my experience here: https://news.ycombinator.com/item?id=13194571) — krisrak, Dec 16 '16 at 17:30
@krisrak curl works sometimes, it's not a networking problem — Nick Fanilov, Dec 19 '16 at 11:22

score 2 · Answer 1 · answered Dec 23 '16 at 04:03

2

It appears that Instagram api has move api.instagram.com to www.instagram.com with a 302 redirect.

If you are using omniauth-instagram gem, you can use this fix:

#config/initializers/omniauth_instagram_api_path.rb

module OmniAuth
  module Strategies
    class Instagram
      option :client_options, {
        :site => 'https://www.instagram.com',
        :authorize_url => 'https://www.instagram.com/oauth/authorize',
        :token_url => 'https://www.instagram.com/oauth/access_token'
      }
    end
  end
end

The purpose is the replace api.instagram.com by www.instagram.com.

I managed to make my staging and production application work.

answered Dec 23 '16 at 04:03

Kien Le

191
5

It still does not work for some users in my production environment. I have another work around: – Kien Le Dec 23 '16 at 06:47
- Step 1: Open a new tab and login in Instagram and keep this tab open - Step 2: Open a new tab and go to your web application and login via Instagram. I tested 10 times with my "invalid-credentials" account and it worked like a charm – Kien Le Dec 23 '16 at 06:49

stef · Answer 2 · 2016-12-21T20:24:27.777

1

I'm seeing this consistently. After much investigation (a whole day), it appears that Instagram has changed their main API host for authentication from https://api.instagram.com to https://www.instagram.com and redirect with a 302.

If your code sends a POST to api.instagram.com it is redirected, and (I'm guessing here) Instagram counts that as two requests.

I've changed api.instagram.com in my oauth code to www.instagram.com and was able to get an access token.

edited Dec 21 '16 at 20:24

answered Dec 21 '16 at 19:56

stef

14,172
2
48
70

This did not seem to help me unfortunately :/ And the error is very inconsistent. Signing out of Instagram before performing auth seems to help though. – Joel Dec 22 '16 at 15:42

score 0 · Answer 3 · answered Dec 15 '16 at 16:28

0

Also having this issue. If you login via the web to Instagram and then try the auth flow seems to be a work around.

answered Dec 15 '16 at 16:28

tavosansal

1

1

Unfortunately, this workaround is not consistent. – Fran García Dec 16 '16 at 13:01

Instagram oauth - error 400 matching code not found

3 Answers3

Linked