Is anyone else seeing increased 401 errors over the past 48 hours?

episod · 2012-06-27T14:18:52.000Z

Thanks Paul! By the way, be sure and move from /statuses/replies.json as it hasn’t been a valid, documented API method now for a few years. You’re probably after /statuses/mentions.json instead. Good time as any to make sure you’re up to date with all your API paths and not using any deprecated methods: [node:6296].

TheUberGuy · 2012-06-27T16:56:09.000Z

Thanks for the heads up, I completely missed that one when I went through a few months ago.

TheUberGuy · 2012-06-27T17:05:52.000Z

Would we not be seeing this error if we were already using /statuses/mentions.json ? We are changing anyway in a release shortly, but wanted to know if we should be putting out some type of emergency fix.

episod · 2012-06-27T17:41:50.000Z

Nah, using statuses/replies versus statuses/mentions isn’t related to this issue – just noticing and want to make sure you’re prepared

gubrack · 2012-06-27T17:43:37.000Z

Due to a temporary failure, you may need to retry the previous operation… @UberSoc eror (?)

TheUberGuy · 2012-06-27T17:49:21.000Z

It is greatly appreciated that you noticed and said something, I’m kicking myself for not catching that months ago.

scopeapp · 2012-06-27T18:05:43.000Z

to be fair, we switched form statuses/replies to statuses/mentions yesterday, and a lot of the 401s stopped.

replies was consistently returning 401s, but mentions wasn’t in testing.

It was a drop-in replacement too

Although, my impression was that the issues were somehow related to rate limiting per-ip, as development boxes often didn’t have the issue, so if that’s true, that could also explain it if the limiting was per-method per-ip

Conchimartin · 2012-06-27T23:06:08.000Z

I have problem too in some ocassion, more when i try upload photo

andy957 · 2012-06-28T00:48:17.000Z

Same error as @gubrack w/UberSocial.

zechariahs · 2012-06-28T01:48:08.000Z

I’ve been having this problem since yesterday. I use @Tweetbot as a client.

Paul_Several · 2012-06-28T02:05:41.000Z

thank you

episod · 2012-06-28T02:10:18.000Z

Hoped to get a fix out for you all today, but looks like it will be tomorrow. Will update the thread and ticket if it will be any longer. Thanks for hanging in there.

GDRPempress · 2012-06-28T05:37:35.000Z

For almost 24 hours now, on tweetdeck and twitter, I am getting “Twitter API unable to authenticate.”

I count on twitter for work.

No help from twitter support as of yet.

I have cleared cookies and cache but STILL unable to receive @ messages, there are no updates, and no streaming, and no mentions.

I am able to receive DM’s with my twitter handle, but nothing else.

Someone, anyone, suggestions, please??? Twitter is vital for my work.

Thank you.

liy_liyana · 2012-06-28T07:20:07.000Z

I’m not able to see mention on my ubersocial for iphone. It keep checking my status account and still no mention appears. someone please help me. Thank you.

SatScenes · 2012-06-28T08:51:00.000Z

I have cron’d code which picks up new @replies to this account only. It has been returning 401 now for the past 48 hours. I have tried re-authenticating. On Tuesday it was doing it intermittently. It is now doing it on every call (every 10 minutes).

The request is: http://api.twitter.com/1/statuses/replies.json?count=200&include_entities=true&since_id=217365510059339777

The Authorization: header was: OAuth oauth_consumer_key=“InGec0wsGXiK266jWUhOGQ”,oauth_nonce=“8o04h1wrvOOBn4RCxw6pF4EoOW8”,oauth_signature=“WAC73Bh6BAJ0M14uSMKGsOevkbU%3D”,oauth_signature_method=“HMAC-SHA1”,oauth_timestamp=“1340872664”,oauth_token=“16719737-PsjtIiFm05bLnqWowj2xBfaDgiCs8j2CeGuo9O6Z0”,oauth_version=“1.0”

Hope that helps.
Cliff.

MySmileInspires · 2012-06-28T14:52:04.000Z

I’m having a similar problem. I’m a user of UberSocial and whenever I try to check my Timeline on interactions a message pops up and says " Error validating twitter credentials could not authenticate OAuth ". I’m 15 and totally oblivious as to what is going on. I re-installed it 3 times, revoked access to the app and the problem is still occurring.

MySmileInspires · 2012-06-28T14:53:17.000Z

Your lucky cause iPhone has tons of apps for twitter. Blackberry only has UberSocial and the regular twitter app .

episod · 2012-06-28T14:59:14.000Z

Unrelated, you should switch to using the statuses/mentions endpoint – statuses/replies is not valid and has not been a documented API method in years. You may find it just disappearing one day.

If you’re trying to get replies or mentions for an account, polling the REST API is not the most efficient means – you really should consider using User Streams instead.

episod · 2012-06-28T14:59:47.000Z

Hi @MySmileInspires – the problem isn’t you at all but just Twitter. We hope to have the issue fixed today and then your app should work again!

Noojib32 · 2012-06-28T17:16:21.000Z

We have been seeing significantly more 401 errors over the past 48 hours. Calls to account/verify_credentials succeed, but calls to statuses/mentions or statuses/direct_messages fail are failing with authentication errors