-
-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sample error: “InternalOAuthError: failed to obtain request token” #3
Comments
|
I ran into the same issue and found that it only happened when I ran the app through http://localhost:3000. When the request went out through http://127.0.0.1:3000/ the token came through. Hope that helps. |
|
same problem here, using http://127.0.0.1:3000/ did not help |
|
I accessed the app at http://127.0.0.1:3000 and set the callbackURL to http://127.0.0.1:3000/auth/twitter/callback. I get the same error, still. |
|
Which Node.js and Express versions are you using? I’m using Express 2.2.0 and the latest Node.js, 0.6.11. |
|
This continues to happen to me occasionally. It seems to fix itself over a period of time, regardless of whether I use localhost, 127.0.0.1, or any other hostfile alias. There's no way I'm getting rate limited by Twitter, and my internet continues to work just fine, so it's got to be something in the library. At the moment I have Node v0.6.11 and Express v2.5.8. Anyone have any ideas? |
|
I believe with my pull request #5 this problem will be solved |
|
Hi. After I specified a callback URL on dev.twitter.com it seems to be working fine. |
|
I've just pushed new versions of passport-oauth (v0.1.7) and passport-twitter (v0.1.3). I suggest upgrading to these, as the error messages are more detailed. Any failure responses from the Twitter API will be reported, and it'll be clear wether the failure is on that side or on the local system (and what can potentially be done about it). If this helps isolate any errors to something specific to Passport, file an issue. Thanks! |
|
Still seeing this with latest packages.... |
|
yeah, same here |
|
@ktkaushik Are you sure you have the |
|
Same problem here and I also solved that using npm update |
|
Same problem here |
|
For me, the issue was a After reverting this, the issue no longer persists. |
|
"InternalOAuthError: failed to obtain request token" |
I get this when trying the sample.
This is my callback URL:
callbackURL: "http://127.0.0.1:3000/auth/twitter/callback"InternalOAuthError: failed to obtain request token
at /Users/frode/Dropbox/Nettsider/signin/node_modules/passport-twitter/node_modules/passport-oauth/lib/passport-oauth/strategies/oauth.js:155:36
at /Users/frode/Dropbox/Nettsider/signin/node_modules/passport-twitter/node_modules/passport-oauth/node_modules/oauth/lib/oauth.js:510:17
at passBackControl (/Users/frode/Dropbox/Nettsider/signin/node_modules/passport-twitter/node_modules/passport-oauth/node_modules/oauth/lib/oauth.js:366:13)
at IncomingMessage. (/Users/frode/Dropbox/Nettsider/signin/node_modules/passport-twitter/node_modules/passport-oauth/node_modules/oauth/lib/oauth.js:378:9)
at IncomingMessage.emit (events.js:88:20)
at HTTPParser.onMessageComplete (http.js:137:23)
at CleartextStream.ondata (http.js:1137:24)
at CleartextStream._push (tls.js:367:27)
at SecurePair.cycle (tls.js:688:20)
at EncryptedStream.write (tls.js:122:13)
The text was updated successfully, but these errors were encountered: