Could not authenticate you

[annkiit2]

has anyone found a solution yet or even the problem to say so

[tweetarchivist]

I’m also seeing this intermittently – a request that works one day fails the next day. I’m using https and the 1.1 api.

[ketan]

Seeing this error across my android app that has been working for over a year until this last week.

[kipusoep]

Same here, it was working fine, now I get “Could not authenticate you”…

[plainorfancy]

same issue

[brightchimp]

I have 2 versions of our app running - one on the old API, one on the new (v1.1). The new API failed to send tweets for an authenticated user (which it had sent tweets for previously). Switching to use the old API, the same tweet with the same credentials was sent first attempt.
The Twitter gem I’m using raised Twitter::Error::Unauthorized, the message from twitter was “Could not authenticate you”

Any thoughts/updates?

[recamilio]

I’m not sure if it’s directly related, but I realized that if the “status” param were way much over 140 characters, let’s say 180 characters, then you’ll probably get this error message (“Could not authenticate you”). I’m not an expert when it comes to HTTP or OAuth, but it might be some kind of data loss because the request is too long… I don’t know…
Anyway, I’ve limited the input field / textarea to 140, so the user isn’t able to send more than Twitter expects.
After doing that, I haven’t faced this error anymore…

[jaydipsinh121]

Hi Every One,
i am facing problem
{“message”: “Timestamp out of bounds”,“code”: 135}

I want to friend id using
https://api.twitter.com/1.1/friends/ids.json
header passing
Authorization: OAuth oauth_consumer_key=“key”, oauth_nonce=“blabla”, oauth_signature=“blabla”, oauth_signature_method=“HMAC-SHA1”, oauth_timestamp=“1364627646”, oauth_token=“blabla”, oauth_version=“1.0”

and data
count=5000&cursor=-1&screen_name=jaydipsinh121

Please help me to solve this problem.

[episod]

The error message you’re receiving is giving you a hint: your server’s clock is either ahead or behind the time understood by Twitter’s servers.

[moshenmouse]

I’m getting:

401
"error":“Could not authenticate you.”}*

I’m using the cURL command line provided by the OAuth Tool (modified so it actually works - why do you surround the https:… with single quotes?! This breaks curl ('https not supported) and makes me wonder whether the rest of the output from that page is correct):

curl --get --header ‘Authorization: OAuth oauth_consumer_key=“xwxxxxxxxxxxxxxxxxx”, oauth_nonce=“61e64d5fd93d2fb86b40482e1c399222”, oauth_signature=“xxxxxxxxxxxxxxx”, oauth_signature_method=“HMAC-SHA1”, oauth_timestamp=“1365169412”, oauth_token=“nnnnnnnnnn-xxxxxxxxxxxxxxxxxxxxxxxxxx”, oauth_version=“1.0”’ --verbose https://api.twitter.com/1/account/settings.json

I can’t see anything wrong, and the token values are the ones generated by Twitter. Timestamp is correct and the system clock is in synch.

[kurrik]

What platform are you on? It sounds like you don’t have OpenSSL installed, rather than an issue with the perfectly valid curl command which we present.

[moshenmouse]

Thanks for your reply Arne. I do have OpenSSL installed. I’m on Windows (perhaps this explains the 'https problem: I copied and pasted directly from the OAuth Tool page and it produces the error I stated. So perhaps not “perfectly valid” on Windows?). To install cURL I followed: http://guides.instructure.com/s/2204/m/4214/l/83393-how-do-i-install-and-use-curl-on-a-windows-machine

This seems to be fine. So I’m still at a loss as to know what the problem is or what to try next.

[moshenmouse]

Solved. Removal of single quotes fixes this. It really should state that the cURL command line on the OAuth Tool page will not work verbatim in a Windows command window.

curl --get https://api.twitter.com/1/account/verify_credentials.json --header “Authorization: OAuth oauth_consumer_key=xxxxxxxx, oauth_nonce=xxxxxxxx, oauth_signature=xxxxxxxx, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1365412723, oauth_token=nnnnn-xxxxxx, oauth_version=1.0” --verbose

Thanks.

[devmaheshrb458]

where shou

[sudhiid]

Fatal error: Uncaught exception ‘TwitterException’ with message ‘Could not authenticate you.’ in /home/thecolor/public_html/Twitter-PHP/twitter.class.php:238 Stack trace: #0 /home/thecolor/public_html/Twitter-PHP/twitter.class.php(104): Twitter->request(‘statuses/update’, Array) #1 /home/thecolor/public_html/Twitter-PHP/examples/send.php(7): Twitter->send(‘I am fine’) #2 {main} thrown in /home/thecolor/public_html/Twitter-PHP/twitter.class.php on line 238

plz help me

[TNRT66]

Received Could not authenticat you with (401) Unauthorized at 3:46 CDT 6/3/12. Then Tweets posted alright until 6/4/13 12:28:16 AM when 403 Forbidden Status is duplicate. Code is posting fine now. Has Twitter changed something on a temporary basis or was this just a quirk? I want to be sure the code is ready for June 11.
Using RESTv1.1, pin authorization, and only posting to a few accounts. Using LinqToTwitter library.
6/3/2013 3:49:16 PM
Could not authenticate you
The remote server returned an error: (401) Unauthorized.
Tweet = I-65 S in Davidson Co Vehicle Disabled at EXIT 79: ARMORY DR. at 3:30 PM 6/3 est clear by 4:00 PM 6/3 (CT
Acct info = TN511

Checked API status and saw Twitter had issues yesterday at the time I received the errors. I will assume that was the issue. Thanks

[julipinheiro1]

&

[teamhacketyhack]

Hi,

I’m getting the following error when trying to authenticate through my rails app with a ‘sign in with twitter button’,

Could not authorize you from Twitter because “Timeout”.

I’m a newbie developer so unsure what the solution would be. Any pointers?

[itsvipins]

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

[chethanjn]

{“errors”:[{“message”:“Timestamp out of bounds”,“code”:135}]},
hi, iam also getting this error,i know the problem but i dont know the solution,please suggest solution in javascript…
thank you