Whoa there! The request token for this page is invalid. It may have already been used, or expired because it is too old. Please go back to the site or application that sent you here and try again; it was probably just a mistake


#1

We didn’t change anything and our development servers still work fine… however twitter connect is now giving this error

“Whoa there!
The request token for this page is invalid. It may have already been used, or expired because it is too old. Please go back to the site or application that sent you here and try again; it was probably just a mistake.”

Here is a sample oath request that is failing https://twitter.com/oauth/authenticate?oauth_token=16rRdCw4U24hPseNK0HjKA5ZoRiaGA8cOX9WO7nid8


#2

First, make sure that you’re using the correct paths – it’s https://api.twitter.com/oauth/authenticate (the api subdomain is required). Also make sure that there’s no clock drift on your servers – we return the current time in all of our requests in a Date header, which you can use to compare against your oauth_timestamp values and ensure they’re pretty close in sync.


#3

We didn’t change anything and our development servers still work fine… however twitter connect is now giving this error

“Whoa there!
The request token for this page is invalid. It may have already been used, or expired because it is too old. Please go back to the site or application that sent you here and try again; it was probably just a mistake.”

can you please help me ?


#4

Hello @episod.

today we re dong some changes in code, we change the library and now we are getting authentication but after authentication we are getting another error which is as below.

stdClass Object ( [errors] => Array ( [0] => stdClass Object ( [message] => Invalid or expired token [code] => 89 ) ) )

Can you please help me to solve this issue ?


#5

we are doing R&D and we got some other information and its below,

Ensure that your system’s timestamp is in sync with Twitter’s. We return the current time in the “Date” HTTP header with every request. If your request fails due to a timestamp mismatch, use this time to determine the delta between the system clock and our server clock and adjust your oauth_timestamps for subsequent requests accordingly.

Do you think this is a hosting time issue ? can anyone give me your feedback please?

Irshad Ahmad.


#6

facing the same issue.


#7

"The request token for this page is invalid. It may have already been used, or expired because it is too old. "

Our users are getting this error when trying to sign in.

Is this related to changes in your authentication methods announced on the news a few days ago?

Will we have to re-create our application credentials?
Will all our users have to re-authorize our app?


#8

Invalid request token. 401. I’m not happy =(


#9

am also getting same problem can any body give me the solution for this problem


#10

Hello Episod,
I am a developer using Twitter 1.1 API for automatic tweet but every time twitter is asking for login and authorize how i fixed it please please help me…
I want to tweet on twitter in background process same as justunfollow.com and tweetlonger do.
Thanks in advance.


#11

we are experiencing same problem, how can we resolve. We have been trying to regenerate our API keys with no success.

debug log says the same time Token mis match.
05-03 11:20:21.494: W/DefaultRequestDirector(1963): Authentication error: Unable to respond to any of these challenges: {oauth=www-authenticate: OAuth realm=“https://api.twitter.com”}
05-03 11:20:21.564: W/System.err(1963): oauth.signpost.exception.OAuthNotAuthorizedException: Authorization failed (server replied with a 401). This can happen if the consumer key was not correct or the signatures did not match.
05-03 11:20:21.574: W/System.err(1963): at oauth.signpost.AbstractOAuthProvider.handleUnexpectedResponse(AbstractOAuthProvider.java:239)
05-03 11:20:21.574: W/System.err(1963): at oauth.signpost.AbstractOAuthProvider.retrieveToken(AbstractOAuthProvider.java:189)
05-03 11:20:21.574: W/System.err(1963): at oauth.signpost.AbstractOAuthProvider.retrieveRequestToken(AbstractOAuthProvider.java:69)
05-03 11:20:21.584: W/System.err(1963): at com.cyber.development.connect.core.SonetOAuth.getAuthUrl(SonetOAuth.java:58)
05-03 11:20:21.584: W/System.err(1963): at com.cyber.development.connect.core.OAuthLogin$1.doInBackground(OAuthLogin.java:125)
05-03 11:20:21.584: W/System.err(1963): at com.cyber.development.connect.core.OAuthLogin$1.doInBackground(OAuthLogin.java:1)
05-03 11:20:21.584: W/System.err(1963): at android.os.AsyncTask$2.call(AsyncTask.java:288)
05-03 11:20:21.584: W/System.err(1963): at java.util.concurrent.FutureTask.run(FutureTask.java:237)
05-03 11:20:21.584: W/System.err(1963): at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)
05-03 11:20:21.584: W/System.err(1963): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
05-03 11:20:21.584: W/System.err(1963): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
05-03 11:20:21.584: W/System.err(1963): at java.lang.Thread.run(Thread.java:841)


#12

05-03 11:20:21.494: W/DefaultRequestDirector(1963): Authentication error: Unable to respond to any of these challenges: {oauth=www-authenticate: OAuth realm=“https://api.twitter.com”}
05-03 11:20:21.564: W/System.err(1963): oauth.signpost.exception.OAuthNotAuthorizedException: Authorization failed (server replied with a 401). This can happen if the consumer key was not correct or the signatures did not match.
05-03 11:20:21.574: W/System.err(1963): at oauth.signpost.AbstractOAuthProvider.handleUnexpectedResponse(AbstractOAuthProvider.java:239)
05-03 11:20:21.574: W/System.err(1963): at oauth.signpost.AbstractOAuthProvider.retrieveToken(AbstractOAuthProvider.java:189)
05-03 11:20:21.574: W/System.err(1963): at oauth.signpost.AbstractOAuthProvider.retrieveRequestToken(AbstractOAuthProvider.java:69)
05-03 11:20:21.584: W/System.err(1963): at com.cyber.development.connect.core.SonetOAuth.getAuthUrl(SonetOAuth.java:58)
05-03 11:20:21.584: W/System.err(1963): at com.cyber.development.connect.core.OAuthLogin$1.doInBackground(OAuthLogin.java:125)
05-03 11:20:21.584: W/System.err(1963): at com.cyber.development.connect.core.OAuthLogin$1.doInBackground(OAuthLogin.java:1)
05-03 11:20:21.584: W/System.err(1963): at android.os.AsyncTask$2.call(AsyncTask.java:288)
05-03 11:20:21.584: W/System.err(1963): at java.util.concurrent.FutureTask.run(FutureTask.java:237)
05-03 11:20:21.584: W/System.err(1963): at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)
05-03 11:20:21.584: W/System.err(1963): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
05-03 11:20:21.584: W/System.err(1963): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
05-03 11:20:21.584: W/System.err(1963): at java.lang.Thread.run(Thread.java:841)


#13

@episod i’m also getting same problem,
i didn’t change anything but sometimes getting error,
Please suggest me the correct answer


#14

To solve this issue use “https” (secure) instead of “http” in your app.js file. This will get out of that message of request token invalid.


#15

I am experiencing this issue in one of my servers and Twitter header date and mine are the same, what could be wrong?


#16

experiencing this issue as well.
does this look like a valid request?

https://api.twitter.com/oauth/authorize?oauth_token=(u'wS5BBBBBBBSHaLAAABUhkqi7Q'%2C+u'PBwu9KSDokxJyF5z4mA8m9giokDXuTbK')


#17

i used token and token secret. you only need the request token


#18

Hi there:

1 year after the last post, I know, but my App has 3 years working fine an now I’m having the same issue. I’m looking for help.

I have regenerated the Twitter Key and secret but have no success. I have checked the Twitter server’s time and it mach my server’s time.

Some clients can login and some others don’t. One client told me that he cleared his history and after that was able to login.

I can’t ask every one to clear their cache. I’m using now a meta tag avoiding to cache my site, but this is going to slow down every one.

Any one has found a way to solve this?


#19

Did you ever get a resolution to this issue?


#20

Hah! Seeing from my own post that oath_token value is null/empty hmm, that’s a clue…