Could not authenticate you

moshenmouse · 2013-04-05T14:00:00.000Z

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 · 2013-04-05T16:54:02.000Z

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 · 2013-04-08T08:23:00.000Z

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 · 2013-04-08T09:30:00.000Z

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 · 2013-04-11T14:46:37.000Z

where shou

sudhiid · 2013-06-04T10:11:00.000Z

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 · 2013-06-04T17:03:18.000Z

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 · 2013-07-13T04:13:14.000Z

&

teamhacketyhack · 2013-07-21T19:36:06.000Z

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 · 2013-10-20T10:07:41.000Z

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

chethanjn · 2013-12-23T12:09:16.000Z

{“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

aleclarsoniv · 2014-02-07T06:49:55.000Z

Generate your timestamp with this, in order to get seconds since Unix epoch.
(new Date() / 1000).toString()

BENOIND · 2014-03-03T10:54:20.000Z

Hi All,

Am receiving “User’s credentials have not been verified yet.” message.
When User credentials have verified?

yogesh_marakana · 2014-04-22T13:15:41.000Z

hi, iam also getting this error,i know the problem but i dont know the solution,please suggest solution in javascript

thankyou

vikasdiyer · 2014-05-13T05:00:53.000Z

Including write permissions to the app fixes the “Could not authenticate issue”

borntobethe1 · 2014-05-28T01:27:00.000Z

I am having the same problem please get back to me

DedeHader · 2014-06-06T11:50:43.000Z

hello

sdhanavath · 2014-07-16T09:18:00.000Z

Hi, I’m having same problem…
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.
message - Could not authenticate you
code - 32

sherif_k · 2015-09-19T10:23:39.694Z

You’ll need to go to twitter.com and generate a one-time password to use for login

claudeschneider · 2017-03-09T22:41:11.642Z

We’ve seen a few of these errors in the last hour (5 tweets failed so far, out of ~200 successful). It’s happening for several different users, and there’s no common theme regarding the content they’re posting.

We’ve not changed our code for a while, and all other posts are going out fine.

Could someone at Twitter confirm if this is a temporary issue they’re facing, or something we need to look into - and if so, any suggestions for what to look for.