Receiving 401 when retrieving request token

johnz_place · 2012-02-09T03:35:16.000Z

I have 5 web sites using the “Tweet This” WP plugin and I’ve always put a URL in the “call back” field and I still have yet to get the “Tweet This” WP Plugin to work on anyone of the sites.

I would like to know if it’s the plugin or Twitter? And how to get the plugin to work even once.

johnz_place · 2012-02-09T05:33:26.000Z

I found this response from the maker of “Tweet This” (Richard X. Thripp) describing why this error (the 404 error) may appear here:

http://richardxthripp.thripp.com/tweet-this/#comment-87745

The 404 error Richard says:

“That usually means the tweet was over 140 characters or you published an identical tweet to Twitter in the past 25 hours. Also, make sure the Twitter application is set to “Read & Write” access.”

The commenter atif said that everything was in order but he still got the error; however, when atif checked out Twitter he found that the tweet appeared in Twitter anyhow even with the error in the blog.

After reading this I checked out my Twitter after posting from one of my blogs and getting this error. I too found out to my surprise that the tweet made it to Twitter even with the error in my blog.

So, I have to recommend checking this out for your own blogs to see if your tweets are making it to Twitter anyhow even in spite of the errors in your blogs.

Also, make sure to read the original response following the link above to hear it from the maker of “Tweet This” himself Richard X. Thripp.

If you still have any questions taking them to the maker of the plugin may prove to be more fruitful anyhow as here.

John

kurrik · 2012-02-09T17:19:43.000Z

Thanks, John. Contacting the author of the plugin is great advice.

VinceJohnson4 · 2012-02-10T09:07:00.000Z

Please verify whether the device DATE and TIME are up to date. If not, then it might cause problems with the access token.

taccount3929 · 2012-02-15T06:08:36.000Z

I’m having same problem too. Please HELP!!!

taccount3929 · 2012-02-15T06:10:11.000Z

Here below is the error message.

Error during OAUth retreive request token
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.

Please HELP!!!

episod · 2012-02-15T15:51:44.000Z

Go through some of these steps in this post: [node:204]

Hiren_Sakhiya · 2012-02-21T06:23:43.000Z

What is cause of this : oauth.signpost.exception.OAuthNotAuthorizedException: Authorization failed (server replied with a 401).
I am testing OAuth integration with android application
thanks

episod · 2012-02-21T16:54:23.000Z

As has been indicated before – there’s not one cause of this – there’s many, and you’ll need to do some debugging on your own to rule things out. Take a look at [node:204].

aloncarmel · 2012-02-21T20:41:30.000Z

Same issue exactly here, random 401 for some users and perfect work for others. the 401 is caused on the callback for me. the first call for twitter. the request access key returns a 401 error. i used jmatai library from twitter recommended libraries and it returns the same. any updates?

aloncarmel · 2012-02-21T20:42:27.000Z

Im getting the feeling its not a code issue.

episod · 2012-02-21T21:29:39.000Z

Can you share the 401 you’re getting, including the sequence of events that lead to it? I’m not familiar with jmatai – have you tried using the API outside of the context of the library you’ve been using? Have you verified you’re using all the correct end points? A callback can’t “401” on you – unless you’re throwing the 401, since the callback is being executed on your server.

aloncarmel · 2012-02-25T16:33:36.000Z

The 401 is happening on callback page when I call for access token. I’ve used this library and flow hundred of times. Fails randomly. Clearing the API.twitter.com cookies fixes the issue per browser.

jojomooo · 2012-02-28T08:10:25.000Z

I am getting 401 error on new app account, old account still works,
Really need to deleiver solutions to client.
The remote server returned an error: (401) Unauthorized

Thanks

episod · 2012-02-28T15:36:20.000Z

You’ll need to help yourself out here to solve your problem. All OAuth issues like this are surmountable with careful concentration and better understanding of what each step of the process does and the possible pitfalls at each stage of the game. [node:204] can help you a lot here.

episod · 2012-02-28T15:37:02.000Z

Always use SSL in the OAuth sequence and don’t pass cookies to the API (you’re using OAuth for authorization, not cookies) and you can avoid this problem.

Kunstphrasen · 2012-02-29T09:01:11.000Z

had the same problem and solved it with recreating access token. hope it helps…

vitorio · 2012-03-21T16:52:52.000Z

THANKS!

MaoriMe1 · 2012-03-22T06:25:16.000Z

When creating your application, do not click the “create your access token” until you first click on Settings and change the Application Type to “Read, Write and Access direct messages”.
After your Twitter application has been updated to “Read, Write and Access direct messages”, click on the Home tab, and “create your access token”.
This should do the trick =)

junaidengg · 2012-04-10T09:22:53.000Z

When creating your application, do not click the “create your access token” until you first click on Settings and change the Application Type to “Read, Write and Access direct messages”.
After your Twitter application has been updated to “Read, Write and Access direct messages”, click on the Home tab, and “create your access token”.
This should do the trick =)

This helps me

Thanks MaoiMe