Intermittent OAuth issue

Digitalsmind · 2012-12-10T21:42:23.000Z

I have the same issue now. We had a server crash and now, no matter what we try we are getting 401 errors. We even had the folks who make the app look at it (we were with them ALL day trying things out) and they finally said… it’s a twitter issue.

We can connect to the API (via SSH) and the facebook and linkin API calls ALL work from the app.

I’ve tried all the stuff mentioned here… no luck…

Anyone figure this out yet?

brouits · 2013-02-06T14:19:01.000Z

i also have 401 Unauthorized reponses on several requests, almost all the time.
e.g: /1.1/users/show.json?screen_name=brouits leads to 401 Unauthorized response with headers following:

content-type: application/json; charset=utf-8
date: Wed, 06 Feb 2013 14:14:42 UTC
server: tfe
content-encoding: gzip

with /1.0/ i have no problem.

brouits · 2013-02-06T15:08:29.000Z

okay, my mistake. for /1.1/users/show.json i made a mistake in baseString generation (i used it with full url and query params, not just base url). see 9.1.2. Construct Request URL in oauth.net documentation.

NaorBiton · 2013-05-14T08:29:00.000Z

Huh, I just noticed this thread now,
I opened a thread about an issue that sounds very similar, but happens on POST ‘statuses/filter’ of the Streaming API.
https://dev.twitter.com/discussions/17580

We have spent a significant amount of time to trace the root cause of this, and we thought that perhaps there is something missing from our API calls which can make them pass all the time.
So far we haven’t managed to change anything that has any impact on how this works, and the service seems to come back up every now and then, but soon after we’re back to receiving 401’s.
I did find out that during “down time”, usually after 5- 7 connection retries (manual) we’re getting the stream to work.
We’re using the ‘ntwitter’ module for Node.js

Any help will be extremely appreciated. We can not go to production with this.

bryan_m · 2013-06-26T09:54:56.000Z

I know this is a old thread but I’m adding it here incase someone actually reads it. Since the change to API 1.1 and required OAuth with callbacks. I have seen entirely random 401’s when sending a post… I can do a few 200’s in a row then all of a sudden get hit with some 401’s for no reason, then all of a sudden the servers will then accept the updates for a while. Entirely random with no reason or valid code of why the error happens.

edit: and no, it’s not a rate limit issue.

Sulabh_Jain · 2013-06-28T17:53:09.000Z

I am running into similar issue where airbrake is showing 401 with Twitter not responding error message. Is that an expected behavior ? I am using oauth. This has been happening intermittently for last 2-3 weeks.

itsvipins · 2013-10-20T10:08:06.000Z

I am getting the same error {“errors”:[{“message”:“Could not authenticate you”,“code”:32}]}

chadmaughan · 2013-11-13T17:19:00.000Z

We’ve seen similar behavior.

It’s happened to us once before and is currently happening. When we deploy new code (unrelated to OAuth) to multiple AWS instances, it suddenly stops working. This is for both new authenticate requests and API connections with previously acquired access tokens.

Several weeks ago this happened on a deploy. A few days later it magically started working again with no code changes.

It has only affects a single deployment lane (i.e. works in dev, stage, but not in prod).

Our first thought was system times. That doesn’t appear to be the case.

Any one have any ideas?

Thanks in advance for your help!

episod · 2013-11-13T17:54:12.000Z

Do you know if you’re changing geographic regions at all, perhaps talking to a different Twitter data center than you typically do, one where maybe your application-related data isn’t as “hot” and ready? Do you know if your instances are aggressively caching DNS or other routing information potentially leading you to talk to servers that aren’t in active use? If you examine the raw requests, HTTP headers and all when requests fail do they more or less functionally identical to those sent that were functional?

Sokine199 · 2014-01-02T15:27:35.000Z

of conditions would be a 50X response, but the root cause here is ? 401s that you’re seeing. Ultimately, this is similar to 502s ?401 error a total failure in authentication. , , , , …

Sokine199 · 2014-01-02T15:28:32.000Z

last 2 days or so. What’s been very strange for me is that I have 2 apps I , using exactly the same code and oauth keys. What’s even more odd is that if I ?curl code from the terminal on my laptop, it works as expected. , , & tags

Sokine199 · 2014-01-02T15:29:39.000Z

having this issue. keys. What’s even more odd is that if I I have 2 apps I , using exactly the - , & tags,

Sokine199 · 2014-01-02T15:30:30.000Z

– however, applications are all written differently and it’s possible the iPad …now. Thanks for fixing this! , , , ##HootSuite_Help 11:44pm via HootSuite

Sokine199 · 2014-01-02T15:31:35.000Z

401 errors with one client. A repeatable fix is for the client to go into his twitter … and check Tweet location and Save. 401 errors with one …, , .

Sokine199 · 2014-01-02T15:32:19.000Z

two different computers on two different networks. Twhirl and Tweetdeck which work fine on both networks, suddenly stopped working yesterday. When looking at the log files, I get Oauth errors. Both systems are Windows 7, 64 bit. , , , , , …

Sokine199 · 2014-01-02T15:33:36.000Z

DNS results for reverse lookups are cached, and checked to prevent ARP poisoning , the same issue now. We had a server crash and now, no matter what we try we are.?…

Sokine199 · 2014-01-02T15:34:25.000Z

& tags. Many languages are supported like ?server crash and now, no matter what we try we are getting 401 …,I’ve tried all the stuff mentioned here… no luck…

AmancioJunior79 · 2014-01-18T05:08:56.000Z

Apple

daosold · 2014-01-27T10:47:04.000Z

Hello everyone!
It seems like Twitter is about to tighten it’s restrictions on usability of their API without any announce. Why not just to disable API at all?
I have a bunch of apps, that crawl Twitter using Net::Twitter from CPAN. I respect every policy of Twitter, but today I found, that my apps, created about week ago, is constantly receiving 401.
I create new apps, put it to the same crawler, et voila! Everything is working fine…
So, it seems like Twitter is delimiting absolute maximum number of allowed requests per application ( i.e. even if we make, say, one request per minute during 15 minutes window, and will do this everyday, expect this gets broken forever after. say. 1M completed request ).

Could Twitter kindly confirm this or explain, if I’m ( hopefully ) wrong?

CG_PegaCiiA · 2014-05-13T14:54:35.000Z

Hi All,

I am facing the same issue from yesterday. Could Please let me know what is the resolution for this issue.

Fail:InternalReason
Response Code : 401
Status Mesage : " response header has unrecognized name not found in HTTP response: Status "