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


#1

I have received a report from the user that a timeline can not be retrieved with 401 error.
The same symptoms as the previous 401 error seems to have occurred.

https://dev.twitter.com/discussions/7913

”Calls to account/verify_credentials succeed, but calls to statuses/mentions or statuses/direct_messages fail are failing with authentication errors. "


#2

Are you using API v1 or API v1.1?

I’m investigating some similar reports.


#3

Hi.
Thanks to reply.
I use API v1.0.


#4

Can’t get stream api to run with 1.1. Was working fine yesterday.

One machine gets 401. On another, the connection succeeds but no data comes back (even for the ‘sample’ stream).

The 1.1 api call to statuses/user_timeline.json works on both with the same app/user tokens.


#5

Hi 401 when I try to retrieve trending topics. Account validation working OK.

1.1 API


#6

The spurious and bursty 401s should now be resolved. If you’re experiencing 401 issues of this nature still, please let us know.

If your 401s are more deterministic and consistent, it’s likely some other reason is the cause of your 401s. See [node:204] for more information on troubleshooting common OAuth issues.


#7

I am still getting error 34 on my API

https://twitter.com/statuses/user_timeline/theryanbeatty.json?callback=twitterCallback2&count=6&hashtag=1

been getting since yesterday…


#8

Your URL is outdated – verify your OAuth is performed correctly as well.

Instead of: https://twitter.com/statuses/user_timeline/theryanbeatty.json?callback=twitterCallback2&count=6&hashtag=1

You probably want: https://api.twitter.com/1/statuses/user_timeline.json?screen_name=theryanbeatty?callback=twitterCallback2&count=6

As far as I know, hashtag=1 is not a parameter accepted by this method.


#9

I still have increased number of 401 statuses.


#10

I still have issues with the 401 error. I am trying to get the statuses from the user’s home and it’s throwing up the 401 error. I am using MGTwitterEngine on the iOS platform


#11

Still getting random 401 errors on update.json


#12

Taylor,

I am experiencing the same problem on accessing the user timeline. It worked for few users and then I started experiencing this problem.
Can you help me on this?

Following are the details…
[Tue Feb 04 15:50:14 MST 2014]Request:
[Tue Feb 04 15:50:14 MST 2014]GET https://api.twitter.com/1.1/statuses/user_timeline.json?user_id=788930424&include_my_retweet=true&count=500&page=1&include_entities=1&include_rts=1
[Tue Feb 04 15:50:14 MST 2014]OAuth base string: GET&https%3A%2F%2Fapi.twitter.com%2F1.1%2Fstatuses%2Fuser_timeline.json&count%3D500%26include_entities%3D1%26include_my_retweet%3Dtrue%26include_rts%3D1%26oauth_consumer_key%3DvtVBkWuRgRf4cKdzAbynw%26oauth_nonce%3D-517227779%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1391554214%26oauth_token%3D16890316-bo9Ar5XDopYygFA0tPHosWTyZ9f0jempL1dy2peI%26oauth_version%3D1.0%26page%3D1%26user_id%3D788930424
[Tue Feb 04 15:50:14 MST 2014]OAuth signature: PQW+R2rYFEaHyVim4jEb3b07+J4=
[Tue Feb 04 15:50:14 MST 2014]Authorization: **********************************************************************************************************************************************************************************************************************************************************************************
[Tue Feb 04 15:50:14 MST 2014]X-Twitter-Client-URL: http://twitter4j.org/en/twitter4j-3.0.5.xml
[Tue Feb 04 15:50:14 MST 2014]X-Twitter-Client: Twitter4J
[Tue Feb 04 15:50:14 MST 2014]Accept-Encoding: gzip
[Tue Feb 04 15:50:14 MST 2014]User-Agent: twitter4j http://twitter4j.org/ /3.0.5
[Tue Feb 04 15:50:14 MST 2014]X-Twitter-Client-Version: 3.0.5
[Tue Feb 04 15:50:14 MST 2014]Response:
[Tue Feb 04 15:50:14 MST 2014]HTTP/1.1 401 Unauthorized
[Tue Feb 04 15:50:14 MST 2014]content-type: application/json;charset=utf-8
[Tue Feb 04 15:50:14 MST 2014]x-frame-options: SAMEORIGIN
[Tue Feb 04 15:50:14 MST 2014]last-modified: Tue, 04 Feb 2014 22:50:14 GMT
[Tue Feb 04 15:50:14 MST 2014]x-rate-limit-remaining: 138
[Tue Feb 04 15:50:14 MST 2014]status: 401 Unauthorized
[Tue Feb 04 15:50:14 MST 2014]content-encoding: gzip
[Tue Feb 04 15:50:14 MST 2014]date: Tue, 04 Feb 2014 22:50:14 GMT
[Tue Feb 04 15:50:14 MST 2014]x-transaction: e54c3c5dcc8fa2f4
[Tue Feb 04 15:50:14 MST 2014]pragma: no-cache
[Tue Feb 04 15:50:14 MST 2014]cache-control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0
[Tue Feb 04 15:50:14 MST 2014]x-content-type-options: nosniff
[Tue Feb 04 15:50:14 MST 2014]x-xss-protection: 1; mode=block
[Tue Feb 04 15:50:14 MST 2014]x-rate-limit-limit: 180
[Tue Feb 04 15:50:14 MST 2014]expires: Tue, 31 Mar 1981 05:00:00 GMT
[Tue Feb 04 15:50:14 MST 2014]set-cookie: guest_id=v1%3A139155421492950504; Domain=.twitter.com; Path=/; Expires=Thu, 04-Feb-2016 22:50:14 UTC
[Tue Feb 04 15:50:14 MST 2014]set-cookie: lang=en
[Tue Feb 04 15:50:14 MST 2014]www-authenticate: OAuth realm=“https://api.twitter.com
[Tue Feb 04 15:50:14 MST 2014]content-length: 160
[Tue Feb 04 15:50:14 MST 2014]x-rate-limit-reset: 1391554585
[Tue Feb 04 15:50:14 MST 2014]server: tfe
[Tue Feb 04 15:50:14 MST 2014]strict-transport-security: max-age=631138519
[Tue Feb 04 15:50:14 MST 2014]x-access-level: read
[Tue Feb 04 15:50:14 MST 2014]{“request”:"/1.1/statuses/user_timeline.json?user_id=788930424&include_my_retweet=true&count=500&page=1&include_entities=1&include_rts=1",“error”:“Not authorized.”}

401:Authentication credentials (https://dev.twitter.com/pages/auth) were missing or incorrect. Ensure that you have set valid consumer key/secret, access token/secret, and the system clock is in sync.
{“request”:"/1.1/statuses/user_timeline.json?user_id=788930424&include_my_retweet=true&count=500&page=1&include_entities=1&include_rts=1",“error”:“Not authorized.”}

Relevant discussions can be found on the Internet at:
http://www.google.co.jp/search?q=ced778ef or
http://www.google.co.jp/search?q=0cd7cb18
TwitterException{exceptionCode=[ced778ef-0cd7cb18], statusCode=401, message=null, code=-1, retryAfter=-1, rateLimitStatus=RateLimitStatusJSONImpl{remaining=138, limit=180, resetTimeInSeconds=1391554585, secondsUntilReset=370}, version=3.0.5}
at twitter4j.internal.http.HttpClientImpl.request(HttpClientImpl.java:162)
at twitter4j.internal.http.HttpClientWrapper.request(HttpClientWrapper.java:61)
at twitter4j.internal.http.HttpClientWrapper.get(HttpClientWrapper.java:81)
at twitter4j.TwitterImpl.get(TwitterImpl.java:1929)
at twitter4j.TwitterImpl.getUserTimeline(TwitterImpl.java:171)
at ctxbot.Crawler.StoreFriendTimeline(Crawler.java:115)
at ctxbot.Crawler.main(Crawler.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120)
Failed to get timeline: 401:Authentication credentials (https://dev.twitter.com/pages/auth) were missing or incorrect. Ensure that you have set valid consumer key/secret, access token/secret, and the system clock is in sync.
{“request”:"/1.1/statuses/user_timeline.json?user_id=788930424&include_my_retweet=true&count=500&page=1&include_entities=1&include_rts=1",“error”:“Not authorized.”}