Error verifying credentials: Status code : 404

[GoogleCodeExporter]

Client (Pidgin, finch, empathy, etc): Pidgin
Client Version: 2.10.0
LibPurple Version: 2.10.0
PrplTwtr Version: 0.10.0
Operating System: Windows 7

Problem/Feature request (Be as specific as possible. Steps to reproduce are
especially helpful):

This morning I had just launched pidgin and see that the twitter account 
refused to launch. It's giving me "Error verifying credentials: Status code : 
404" message. Then I tried to update my PrplTwtr from 0.5.2 to 0.10.0 just in 
case.

I recreate my pidgin twitter account and re-register the OATH pin. But I still 
receive the same message.

Please help.

Original issue reported on code.google.com by donnie.b...@gmail.com on 25 Aug 2011 at 12:15

[GoogleCodeExporter]

Now that's funny.

I tried it a few moments later and it worked out. Maybe there's something wrong 
with the internet connection.

Original comment by donnie.b...@gmail.com on 25 Aug 2011 at 12:29

[GoogleCodeExporter]

I've been seeing periodic 404s as well. As near as I can tell, the URLs are 
correct, and twitter is in fact returning 404 (although their API documents 
suggest that 404 will never be used for a temporary error).

I'm pretty sure it's twitter's problem, not mine, but I'll let you know if I 
find anything.

I hope you're enjoying the new features in 0.10 since 0.5.2 :)

Original comment by mikeage on 25 Aug 2011 at 6:21

• Changed state: Accepted

[GoogleCodeExporter]

Error al recibir solicitud de token Error al leer de twitter.com: Error de 
entrada/salida

No hay forma de buscar el token de forma manual?

Original comment by mama21ma...@gmail.com on 25 Aug 2011 at 12:18

Attachments:

• tocken.png

[GoogleCodeExporter]

Without a log file, I can't do very much with that screen shot. But 99% of the 
time, that's a twitter.com problem.

Original comment by mikeage on 25 Aug 2011 at 12:20

[GoogleCodeExporter]

Also seeing this quite a lot yesterday and today.  Following @twitterapi to see 
if anything is said there.

Original comment by jh.xs...@gmail.com on 25 Aug 2011 at 7:46

[GoogleCodeExporter]

Along with this, also getting a 404 when trying to send a new tweet.

(03:05:25 PM) Error sending tweet: Status code: 404

Original comment by jh.xs...@gmail.com on 25 Aug 2011 at 8:06

[GoogleCodeExporter]

Issue 62 has been merged into this issue.

Original comment by mikeage on 10 Sep 2011 at 5:20

[GoogleCodeExporter]

I'm getting random but frequent 404s on the account too. Here's the log when it 
happens, (with hopefully all identifying/login info obfuscated)

(17:18:21) account: Connecting to account Gizmokid2005.
(17:18:21) connection: Connecting. gc = 084CCAA8
(17:18:21) prpl-twitter: logging in Gizmokid2005
(17:18:21) prpl-twitter: Sending GET request to: 
http://api.twitter.com/1/account/verify_credentials.xml ? 
oauth_callback=oob&oauth_consumer_key=<REMOVED>&oauth_nonce=110&oauth_signature_
method=HMAC-SHA1&oauth_timestamp=1315689501&oauth_token=<REMOVED>&oauth_signatur
e=<REMOVED>
(17:18:21) util: requesting to fetch a URL
(17:18:21) dnsquery: Performing DNS lookup for api.twitter.com
(17:18:21) dnsquery: IP resolved for api.twitter.com
(17:18:21) proxy: Attempting connection to 199.59.149.200
(17:18:21) proxy: Connecting to api.twitter.com:80 with no proxy
(17:18:21) proxy: Connection in progress
(17:18:21) proxy: Connecting to api.twitter.com:80.
(17:18:21) proxy: Connected to api.twitter.com:80.
(17:18:21) util: request constructed
(17:18:22) util: Response headers: 'HTTP/1.0 200 OK

Date: Sat, 10 Sep 2011 21:18:52 GMT

Server: hi

Status: 200 OK

X-Transaction: 1315689532-8155-38446

X-RateLimit-Limit: 350

ETag: "c0d32ec8e1cd38971ecd49ca98d31616"

X-Frame-Options: SAMEORIGIN

Last-Modified: Sat, 10 Sep 2011 21:18:52 GMT

X-RateLimit-Remaining: 341

X-Runtime: 0.01909

X-Transaction-Mask: a6183ffa5f8ca943ff1b53b5644ef1147e9be24b

Content-Type: application/xml; charset=utf-8

Content-Length: 2676

Pragma: no-cache

X-Access-Level: read-write-directmessages

X-RateLimit-Class: api_identified

X-Content-Type-Options: nosniff

X-Revision: DEV

Expires: Tue, 31 Mar 1981 05:00:00 GMT

Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0

X-MID: 597c70cf2d90c46c00d2b0b21eface9378f01d7a

X-RateLimit-Reset: 1315691722

Set-Cookie: k=66.227.242.36.1315689532152190; path=/; expires=Sat, 17-Sep-11 
21:18:52 GMT; domain=.twitter.com

Set-Cookie: guest_id=v1%3A131568953215689020; domain=.twitter.com; path=/; 
expires=Tue, 10 Sep 2013 09:18:52 GMT

Set-Cookie: lang=en; path=/

Set-Cookie: twid=u%3D71058343%7CN84YmycaV3wxVHXiNijdyTe44Bk%3D; 
domain=.twitter.com; path=/

Set-Cookie: _twitter_sess<REMOVED>; domain=.twitter.com; path=/; HttpOnly

Vary: Accept-Encoding

Connection: close

'
(17:18:22) util: parsed 2676
(17:18:22) prpl-twitter: Valid response, calling success func
(17:18:22) prpl-twitter: Valid response, calling success func
(17:18:22) prpl-twitter: twitter_api_get_friends
(17:18:22) prpl-twitter: Sending GET request to: 
http://api.twitter.com/1/statuses/friends.xml ? 
cursor=-1&oauth_callback=oob&oauth_consumer_key=<REMOVED>&oauth_nonce=111&oauth_
signature_method=HMAC-SHA1&oauth_timestamp=1315689502&oauth_token=<REMOVED>&oaut
h_signature=<REMOVED>
(17:18:22) util: requesting to fetch a URL
(17:18:22) dnsquery: Performing DNS lookup for api.twitter.com
(17:18:22) dnsquery: IP resolved for api.twitter.com
(17:18:22) proxy: Attempting connection to 199.59.149.200
(17:18:22) proxy: Connecting to api.twitter.com:80 with no proxy
(17:18:22) proxy: Connection in progress
(17:18:22) proxy: Connecting to api.twitter.com:80.
(17:18:22) proxy: Connected to api.twitter.com:80.
(17:18:22) util: request constructed
(17:18:22) util: Response headers: 'HTTP/1.0 404 Not Found

Date: Sat, 10 Sep 2011 21:18:52 UTC

Server: tfe

Connection: Keep-Alive

'
(17:18:22) connection: Connection error on 084CCAA8 (reason: 0 description: 
Status code: 404)
(17:18:22) prpl-twitter: post_failed called for account Gizmokid2005, error 2, 
message Status code: 404
(17:18:22) account: Disconnecting account Gizmokid2005 (047E0E88)
(17:18:22) connection: Disconnecting connection 084CCAA8
(17:18:22) prpl-twitter: Freeing requestor
(17:18:22) gtkprpltwtr: twitter_conv_icon_remove_conversation_conv_icons conv 
Timeline: Home

Original comment by Gizmokid...@gmail.com on 10 Sep 2011 at 9:21

[GoogleCodeExporter]

I should also add, that occasionally it'll timeout instead of simply 404'ing. 
My guess is a twitter issue, but I've seen nothing on @twitterapi or their RSS 
feeds about any issues.

Original comment by Gizmokid...@gmail.com on 10 Sep 2011 at 9:24

[GoogleCodeExporter]

Issue 63 has been merged into this issue.

Original comment by mikeage on 11 Sep 2011 at 9:40

[GoogleCodeExporter]

I've been having the same 404 error, which started some time on Friday. In 
order to reconnect I have to repeatedly click the check box for my twitter 
account in account manager window. Even then someimes it still takes several 
minutes before it decides to reconnect. Not sure what's going on, glad know I'm 
not the only one. Have not seen anything on the twitter site about this issue. 
I'm using the latest version of piggin and the twitter plugin.

Original comment by fourt...@gmail.com on 11 Sep 2011 at 5:49

[GoogleCodeExporter]

tweetdeck work
twidge work

happening?

Original comment by mama21ma...@gmail.com on 11 Sep 2011 at 9:46

[GoogleCodeExporter]

I started getting this error a few weeks ago, but it would still connect every 
once in a while. However, a couple days ago I got this error yet again, except 
it has not reconnected ever since. Using v0.10.0. and Pidgin 2.10.0.

Original comment by kojir...@gmail.com on 12 Sep 2011 at 12:36

[GoogleCodeExporter]

Just a brief update:

I have absolutely no idea what's wrong.

I keep trying to get a wireshark capture to confirm that the HTTP requests look 
the same, but turning off HTTPS seems to fix the problem. I would think it's 
one server somewhere at api.twitter.com that's misbehaving, but I've never seen 
anything on their status updates. I'll keep you all posted...

Original comment by mikeage on 12 Sep 2011 at 1:44

[GoogleCodeExporter]

I'm already not using HTTPS if that's any help...

Original comment by Gizmokid...@gmail.com on 12 Sep 2011 at 1:57

[GoogleCodeExporter]

Disabled https and the error changed from 404 to Status code:0.

Original comment by kojir...@gmail.com on 12 Sep 2011 at 2:42

[GoogleCodeExporter]

Status code:0 almost always succeeds for me on the next retry

Original comment by mikeage on 12 Sep 2011 at 3:05

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I don't know if this is relevant or not, but is a recent bug being worked on 
giving 404s.  https://dev.twitter.com/discussions/1288

It seems to be with deleting a tweet though.  There are not any initialization 
tests that would be doing something similar?

Original comment by jh.xs...@gmail.com on 12 Sep 2011 at 12:54

[GoogleCodeExporter]

turning off HTTPS worked for me, hitting "re-enable" in the bottom of the buddy 
list failed to turn it back on I had to explicitly enable it from the accounts 
drop down

I tried enabling and disabling but the https was hit or miss, however hitting 
"re-enable" at the bottom never worked

Win XP x86 SP3
prpltwtr-0.11.0
Pidgin 2.9.0 (libpurple 2.9.0)

Original comment by jtzero...@gmail.com on 12 Sep 2011 at 2:34

[GoogleCodeExporter]

I can confirm that "re-enable" doesn't actually do anything. Actually, it often 
does; the account is only disabled after you click re-enable!

I don't know why, but that's more b/c I haven't had a chance to look into it. 
The 404 is a more interesting issue for me.

Original comment by mikeage on 12 Sep 2011 at 2:37

[GoogleCodeExporter]

*by it I mean the account not https

Original comment by jtzero...@gmail.com on 12 Sep 2011 at 2:40

[GoogleCodeExporter]

There have been a couple times today where it is failing every time for many 
(30?) tries in a row.  Like now for example. It goes along fine for 30 minutes 
to an hour, and then I get Error verifying credentials: Status code 404

Original comment by jh.xs...@gmail.com on 12 Sep 2011 at 7:37

[GoogleCodeExporter]

If it's worth anything, I have the issue as well, and never used HTTPS, tried 
enabling and disabling; and updating to 0.11, but no go. It doesn't seem to 
follow any pattern.

Original comment by Hetdegon on 12 Sep 2011 at 9:11

[GoogleCodeExporter]

possible solution

Original comment by mama21ma...@gmail.com on 12 Sep 2011 at 11:04

Attachments:

• 404.jpg

[GoogleCodeExporter]

Issue 66 has been merged into this issue.

Original comment by mikeage on 28 Sep 2011 at 9:32

[GoogleCodeExporter]

i've got the same problem...

The twitter function of Instantbird and the Plugin microblog-purple works fine..

But this Apps are not so comfortable like prpltwtr.

Please fix it :-)

Original comment by schuhman...@gmail.com on 28 Sep 2011 at 4:23

[GoogleCodeExporter]

There is a cycle with these symptoms that occurs with each new release.

With a new prpltwitr install, the 404s go away. Things work without a hitch, no 
re-enabling required for some time. 

At some point, the 404s start again. I have multiple twitter accounts, and the 
return of the 404s happens on the same day across all accounts, though not at 
the same time. They seem to be offset by hours, possibly as much as a day. 

They get worse over time. Even with the recent improvements in silent failing, 
the MTBF requiring the user to press a button to re-enable each account gets 
smaller and smaller. 

This reaches a terminal state where no amount of re-enabling reconnects 
accounts.

I installed 0.11.0 on September 13 and as of this morning (September 28), I'm 
at the terminal state.  

My only guess is that there is some sort of rate-limiting at work. 

I'm not sure whether the relevant metric is time or requests? or tweets 
received?

A possible metric that can safely be ruled out is tweets sent. I never tweet on 
two of my accounts but they fail at roughly the same time as the others.  

Lastly, my experience thus far indicates that if there was a 0.12 release, no 
matter what modifications it contained, the cycle would restart. 

Original comment by telejes...@gmail.com on 28 Sep 2011 at 5:44

[GoogleCodeExporter]

Interesting theory, #28, but there's no way for twitter.com to differentiate 
different versions. I don't update any user agent or other identifying 
information (if I were using the streaming API, they'd require me to, but for 
the REST API, it's not required, and I don't do it).

I'd tend to agree with you that it's rate limiting of some form, although the 
official docs do not list 404 as a rate limited response. 

Original comment by mikeage on 1 Oct 2011 at 5:51

[GoogleCodeExporter]

This appears to have been resolved a long time ago.

Original comment by mikeage on 6 Jun 2012 at 12:26

• Changed state: Invalid