Could Not Authenticate You Twitter Error
Contents |
via /1.1/statuses/update for a year or so. a week ago it started returning HTTP 401 {"errors":[{"code":32,"message":"Could not authenticate you."}]} for all of my users. i hadn't changed twitter error 32 could not authenticate you any of my relevant code or app settings recently. here's the particularly odd
Could Not Authenticate You Twitter Error Unauthorized
part: when i try it in my local environment with the same code, twitter app key/secret, and even the
Authenticate Twitter Account
exact same user access token key/secret, it works fine. it only fails in production. i'm on google app engine using tweepy. (tried versions 2.2 and 3.3, the latest. both fail.) could app
Authenticate Twitter Api Javascript
engine's external facing IPs have been blacklisted or graylisted somehow? more details in this github issue. any ideas? thanks in advance! andypiper 2015-04-28 08:48:13 UTC #2 Is there any chance that the time on your server has drifted or is inaccurate? this kind of thing could happen if the OAuth signature timestamps are off. schnarfed 2015-04-28 14:48:23 UTC #3 thanks for the quick reply @andypiper! could not authenticate you twitter php and that's a really great guess, i definitely wouldn't have thought of it. unfortunately it's not the issue here; i don't personally control the server time (it's a PaaS), but i know they run NTP, and i confirmed that the clock is accurate to within ~2s. kidneybingos 2015-04-29 04:36:17 UTC #4 Wondering if you're having success with this. As far as I can tell, you are the only person having issues similar to mine. To wit: I am running App Engine (Python). No issues in dev_appserver; only in production. I am also using Tweepy and have tried both versions. One difference from your issue, although it might not really be a difference if you have only tried POST requests, is that this is also happening on GET requests to the search API. GET requests work fine most of the time, but if there is punctuation in my query ('q' parameter), most commonly an apostrophe, it always fails with the 32 "Could not authenticate you" error (but again, only in prod; punctuation causes no issue in dev). It does not appear to be an encoding issue. I have verified that the
"could not authenticate you" Error "could not authenticate you" Posted on by JaimeJCandau Home › Forums › TAGSExplorer Questions/Issues › Error "could not authenticate you" Tagged:authenticate, error This topic contains 6 replies, has 4 code 32 message could not authenticate you twitter voices, and was last updated by rob999999999999 11 months, 2 weeks ago. Viewing 7 twitter oauth could not authenticate you posts - 1 through 7 (of 7 total) Author Posts May 22, 2015 at 4:32 pm #480 JaimeJCandauParticipant Hi all, Kept getting tweepy could not authenticate you this error for a while "could not authenticate you". After racking my brains, turns out it's because I was using "non-URL characters" (in my case what's BAGmovies") - it broke the whole thing SOLUTION = Use https://twittercommunity.com/t/post-to-statuses-update-json-started-hitting-error-32-could-not-authenticate-you-with-no-code-changes/36495 URL friendly characters Just in case it helps someone else… @Martin - Love the tool, million thanks!!!!! May 26, 2015 at 6:36 pm #481 mhawkseyKeymaster Hi Jamie - thanks for identifying the problem and sharing 🙂 June 8, 2015 at 4:16 am #493 CHfortagsParticipant Hi, I'm having this problem too. The error message reads: Oops something went wrong. Twitter says:{"errors":[{"code":32,"message":"Could not authenticate you."}]} I have checked the settings and they all seem correct. https://tags.hawksey.info/forums/topic/error-could-not-authenticate-you/ Any ideas? I'm keen to get started! Thanks June 8, 2015 at 8:20 am #494 mhawkseyKeymaster Hi, Can you confirm three things: in your Twitter app settings the callback URL is on the callback field and not the website url in your Twitter app settings the sign in to Twitter is unchecked you are not signed in to multiple Google accounts or that your default account is the one you are using with TAGS June 8, 2015 at 5:00 pm #496 CHfortagsParticipant Hi, Thanks for your message. I just tried again, and I'm in. I opened up a new sheet and rebooted. Other than that, I didn't change anything, so I'm not sure what the problem was, but it authenticated this time, so all is well! Thanks June 8, 2015 at 6:40 pm #497 mhawkseyKeymaster Thanks for letting me know. Have fun! October 21, 2015 at 1:47 pm #564 rob999999999999Participant Same issue here: Oops something went wrong. Twitter says:{"errors":[{"code":32,"message":"Could not authenticate you."}]} I'm using TAGS 6.0ns to get favorites/list. 1. No whitespace in API keys. 2. Callback URL is correctly set https://script.google.com/macros/ 3. Signed into incognito window into Google (with only one account) and Twitter. It seems to work despite showing this error message, however it only grabs the last 397 twitter favorites, instead of the la
DocumentationBest PracticesAPI OverviewUpcoming changes to TweetsObject: UsersObject: TweetsObject: EntitiesObject: Entities in ObjectsObject: PlacesTwitter IDsConnecting to Twitter API using TLSUsing cursors to navigate collectionsError Codes & ResponsesTwitter LibrariesAPI StatusPlaybooksEventsCase StudiesManage My AppsTerms of UseError Codes & ResponsesHTTP https://dev.twitter.com/overview/api/response-codes Status CodesThe Twitter API attempts to return appropriate HTTP status codes for every request.CodeTextDescription200OKSuccess!304Not ModifiedThere was no new data to return.400Bad RequestThe request was invalid or cannot be otherwise served. An accompanying error message will explain further. In API v1.1, requests without authentication are considered invalid and could not will yield this response.401UnauthorizedAuthentication credentials were missing or incorrect.Also returned in other circumstances, for example all calls to API v1 endpoints now return 401 (use API v1.1 instead).403ForbiddenThe request is understood, but it has been refused or access is not allowed. An accompanying error message will explain why. could not authenticate This code is used when requests are being denied due to update limits. Other reasons for this status being returned are listed alongside the response codes in the table below.404Not FoundThe URI requested is invalid or the resource requested, such as a user, does not exists. Also returned when the requested format is not supported by the requested method.406Not AcceptableReturned by the Search API when an invalid format is specified in the request.410GoneThis resource is gone. Used to indicate that an API endpoint has been turned off. For example: "The Twitter REST API v1 will soon stop functioning. Please migrate to API v1.1."420Enhance Your CalmReturned by the version 1 Search and Trends APIs when you are being rate limited.422Unprocessable EntityReturned when an image uploaded to POST account / update_profile_banner is unable to be processed.429Too Many RequestsReturned in API v1.1 wh