Local Supertweet Proxy code installed, but "Could not authenticate you" Code: 32 errors

[Ross]

Hello,

I followed the process on http://www.supertweet.net/about/localproxy/  to the letter I think, and it all went fine.  Right up to the end, when a PIN was returned and I entered that plus a desired password.

Let's say my twitter ID is @tweetingdude  and the password I made up to use with the returned PIN was letme_tweet.
I tried to test the result with a cmdline curl command:

curl -u tweetingdude:letme_tweet -d "status=Test one two three" http://10.0.0.1:8080/1.1/statuses/update.json

… and the result is consistently:

{"errors":[{"message":"Could not authenticate you","code":32}]}

If I put in

curl -u tweetingdude:JUNKTEXT -d "status=Test one two three" http://10.0.0.1:8080/1.1/statuses/update.json

…the result is then:

{"request":"/1.1/statuses/update.json","error":"invalid username/password"}

Which is reassuring that I prob have the right credentials going in.

QUESTION - is that first "errors" message coming from Supertweet or Twitter?

Any suggestion what else to try to get this working?  I must be doing something wrong.

-Ross.

[Mr Blog]

I believe that error 32 is coming from Twitter, but you can tell for sure by examining the 'X-TwitterAPI-Status' header returned in the response by the proxy. If the 'X-TwitterAPI-Status' header is NOT there, then the error is coming from the proxy and not from the Twitter API) - and if the header is there, then the response is a direct copy of whatever Twitter returned. View the headers with curl -h.

Make sure the clock on your server is set correctly (with NTP or similar). The PIN is only good for a little while.

[Mr Blog]

Sorry.

To clarify, once accepted successfully, the access token generated from the PIN should be good forever (effectively), but the time between seeing the PIN and completing the setup form is short.  But if that succeeds, you should be ok after that.

Look in the $(HOME)/.supertweet/jos directory for an access token to ensure that really happened (that an access token was created).  What platform are you on?

[Ross]

Thanks a few things to check there.  Will do and report back.

R.

[Ross]

My "date" command gives me time of 16:49:10 EST 2014  at the same time a failed Tweet via curl returns:

HTTP/1.1 401 Unauthorized
Date: Fri, 07 Feb 2014 21:49:02 GMT
Content-Type: application/json; charset=ISO-8859-1
Date: Fri, 07 Feb 2014 21:49:03 GMT
Vary: Accept-Charset, Accept-Encoding, Accept-Language, Accept
Accept-Ranges: bytes
X-TwitterAPI-Status: 401
Server: Restlet-Framework/2.0snapshot
Content-Length: 63

So, within 8seconds.   Is that close enough for the key algorithm? 
Also looking in  $(HOME)/.supertweet/jos  I see a Token there  (looks like a numericly titled file, with xml formate innards. 

Does "X-TwitterAPI-Status: 401" mean the error is coming from Twitter or the proxy do you think?

Rgds,
Ross.

[Mr Blog]

Again, if the 'X-TwitterAPI-Status' is present it means the result is from Twitter. That header is only inserted by the proxy upon getting a result from Twitter.

The "X-TwitterAPI-Status: 401" means Twitter returned a HTTP 401 error. That "code 32" is sort of their generic error and usually not very helpful. I would suggest trying the sign-in process again to create a new token:  http://localhost:8080/setup/access

[Ross]

 Regenerated keys, tokens etc. Authed other twitter accts - all failed. BUT...
 now problem solved... 

 My issue was clarity around the instructions for setup of the Admin user.  Instructions say:

You will be prompted for a username and password. The default is admin/admin - you can change this by editing the $HOME/.supertweet/adminusers file and restarting the proxy.

This came across to me as simply a user id for access to the proxy, which could remain admin/admin or any other arbitrary choice. It would be clearer to say:  "You MUST change this to set the user name to equal the twitter ID of the app-owner, and some arbitrary password"

Or at least that seems to have done it.  Once I made the user in adminusers the same as my twitter acct name for the app, then I was able to authorize my other twitter account and send a tweet out.

Whew.  :)

[David Beckemeyer]

Changing the admin/admin password I believe is a coincidence - it
should be independent of the Twitter username(s).

But we're glad you got it working!

> --
> You received this message because you are subscribed to the Google Groups
> "SuperTweet MyAPI Proxy" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to supertweet-myapi-...@googlegroups.com.
> To post to this group, send email to
> supertweet-...@googlegroups.com.
> Visit this group at http://groups.google.com/group/supertweet-myapi-proxy.
> For more options, visit https://groups.google.com/groups/opt_out.

[Ross]

Oh - so it must have been something wonky fixed by a restart and regeneration of the keys. 

Thx for the info - will play with that a bit more.

R.

> email to supertweet-myapi-proxy+unsub...@googlegroups.com.