Operation timed out after 30000 milliseconds with 0 bytes received

ThatG33k · 2013-08-22T12:25:36.000Z

I really think there’s something new implemented in the API that blocks our requests, it’s maybe not a bug on Twitter side, but they must have added some kind of specifications about the headers that the library is not explicit about.

Either curl http version, or content-type for multipart etc…

It would be nice to have these informations from twitter, so at least we can try fixing the library, it’s hard to code a library without knowing what the API expect exactly.

Thanks @episod for your time on this issue, with more users adding to this thread, and i see more discussions being created about similar issues, i think this is something worth looking into with the API team so we can get a fix rolling ASAP.

Please continue adding informations to this thread if you get any, i’ll do my best to debug the library (it’s not mine) and try to figure out what Twitter expect and causes the issue.

ss_tatar · 2013-08-22T13:41:00.000Z

Abraham Williams library:
nothinf is special in media parameter. This is a services. It was working very well until 2 days ago.
Here is details.

stdClass Object
(
[errors] => Array
(
[0] => stdClass Object
(
[code] => 195
[message] => Missing or invalid url parameter
)

)
TwitterOAuth Object
(
[http_code] => 403
[url] => https://api.twitter.com/1.1/statuses/update_with_media.json
[host] => https://api.twitter.com/1.1/
[timeout] => 30
[connecttimeout] => 30
[ssl_verifypeer] =>
[format] => json
[decode_json] => 1
[http_info] => Array
(
[url] => https://api.twitter.com/1.1/statuses/update_with_media.json
[content_type] => application/json;charset=utf-8
[http_code] => 403
[header_size] => 748
[request_size] => 202
[filetime] => -1
[ssl_verify_result] => 20
[redirect_count] => 0
[total_time] => 9.672
[namelookup_time] => 0
[connect_time] => 0.203
[pretransfer_time] => 0.609
[size_upload] => 198775
[size_download] => 70
[speed_download] => 7
[speed_upload] => 20551
[download_content_length] => 70
[upload_content_length] => 198775
[starttransfer_time] => 0.609
[redirect_time] => 0
)

[useragent] => TwitterOAuth v0.2.0-beta2
[sha1_method] => OAuthSignatureMethod_HMAC_SHA1 Object
    (
    )

[consumer] => OAuthConsumer Object
    (
        [key] => YLbZeH5gxxxxxxx
        [secret] => yG1T9dTo4PntqV2hNrluXxxx
        [callback_url] => 
    )

[token] => OAuthConsumer Object
    (
        [key] => 1010497213-acs3r2NzT6wl77i8wujbwZcp7txxxxxx
        [secret] => uUrcW7WyMnk7podGRtdxxxxxx
        [callback_url] => 
    )

[http_header] => Array
    (
        [cache_control] => no-cache, no-store, must-revalidate, pre-check=0, post-check=0
        [content_length] => 70
        [content_type] => application/json;charset=utf-8
        [date] => Thu, 22 Aug 2013 13:41:17 GMT
        [expires] => Tue, 31 Mar 1981 05:00:00 GMT
        [last_modified] => Thu, 22 Aug 2013 13:41:17 GMT
        [pragma] => no-cache
        [server] => tfe
        [set_cookie] => guest_id=v1%3A137717887722122270; Domain=.twitter.com; Path=/; Expires=Sat, 22-Aug-2015 13:41:17 UTC
        [status] => 403 Forbidden
        [strict_transport_security] => max-age=631138519
        [x_access_level] => read-write
        [x_frame_options] => SAMEORIGIN
        [x_rate_limit_limit] => 15
        [x_rate_limit_remaining] => 14
        [x_rate_limit_reset] => 1377179767
        [x_transaction] => 8178818b1cba8110
        [x_mediaratelimit_class] => photos
        [x_mediaratelimit_limit] => 100
        [x_mediaratelimit_remaining] => 94
        [x_mediaratelimit_reset] => 1377264173
    )

)

episod · 2013-08-22T13:46:56.000Z

Just because it was working before, doesn’t mean it was working for the right reasons. I’m still looking into overall what has changed here, but the code present in the twitteroauth library doesn’t allow you to explicitly create a multipart request nor does it handle the unique situation of a non-typical POST body when generating the OAuth signature basestring (it includes parameters like status and media[] when neither of these parameters should be in the basestring).

Essentially, with the way that twitteroauth sends the request, there’s no way for our API to use standards-compliant means to evaluate the POST body of the request. An earlier version of our backend allowed these malformed requests for some reason, but that looks to be a bug rectified in the most recent backend implementation.

episod · 2013-08-22T14:08:07.000Z

I am sure something is different as well. I’m still looking into this, now working with tmhOAuth to explore what’s going on.

I’ll give you some insight: Twitter has been around for a few years now. It was originally a site and service built in Ruby on Rails, but nowadays most components and services that make up Twitter are component-based and written in a language called Scala. Recently statuses/update and statuses/update_with_media moved from the Ruby on Rails implementation to a Scala implementation – they try their best to match the old behavior, but they also make corrections to unspecified quirks that may have been allowed in older, less rigorous implementations.

The differences can often be subtle and I think that’s what we’re tracking down right now.

ss_tatar · 2013-08-22T14:27:00.000Z

Thank you.
Here is code sample maybe that helps.


$connection = new TwitterOAuth(CONSUMER_KEY, CONSUMER_SECRET, $access_token['oauth_token'], $access_token['oauth_token_secret']);
$content = $connection->get('account/verify_credentials');
$filename = “asdasdsasda.jpg”;

$handle = fopen($filename, “rb”);

$image = fread($handle, filesize($filename));

fclose($handle);
$params = array(‘media[]’ => “@{$image};Content-Type=multipart/form-data;filename={$filename}” ,

‘status’   => ‘my status UPDATE’);

$response =$connection->post(‘statuses/update’, $params);

ThatG33k · 2013-08-22T15:22:49.000Z

I really appreciate the update, and i know you’re doing your best. I know it’s not easy as CTRL+F and replacing a piece of code.If we can find what’s causing this issue, i guess the libraries will be updated to correspond, and add headers informations to be compliant.

thanks,

ThatG33k · 2013-08-23T10:18:45.000Z

Here some more info, i include a complete TCP stream, and a screenshot of wireshark.

here the tcp stream … i removed my keys of course, and i did it without SSL to grab all the info.

http://pastebin.com/HtXX6ttD

And i also took a screenshot of wireshark results, there’s a lot of TCP retransmission, and a weird error at the end

“20 13.037826 198.245.51.14 199.16.156.104 HTTP 1514 [TCP Retransmission] Continuation or non-HTTP traffic (JPEG JFIF image)”

SmeshKelsta · 2013-08-23T11:15:48.000Z

Hi all. We’re seeing a different but similar problem with connecting to the streaming API and getting back empty responses.

It’s only happening to us when connecting to the Twitter API from the AWS EU region in Ireland. At the moment we’re investigating whether it might be some sort of intermittent routing problem.

Is anyone else who’s getting 0 byte responses hosting their stuff on the AWS EU region?

ThatG33k · 2013-08-23T13:10:28.000Z

I’m not at all in the AWS infrastructure, not even in EU! After many traceroutes to api.twitter.com, there’s a lot of dropped packets along the way after it reached the first gateway on twitter side. I guess it all depends on where you’re coming from, i’ll try to spot one IP that’s responding fine so i can see if my theory is fine.

I tested my uploading speed, and it’s beautiful i can get my full 100mbit/s without problems, so i doubt my connection is the problem, but for some reason uploading to twitter is throttled at very low bandwidth and causes my upload to never complete within the timeout.

ThatG33k · 2013-08-23T13:43:57.000Z

It’s working now … without any modifications on my side. I was doing some debugging when it went through without any issues, and very fast (way faster than it was before) … so i guess something got change on twitter side.

Can you all test now? It should be back to normal!

EDIT: And it’s no longer working … wow

zmotrin · 2013-08-23T14:59:54.000Z

it still does not work for me.

episod · 2013-08-23T15:00:24.000Z

Thanks for the updated information. I’ll forward it on to our team. This is sounding more and more like a network connectivity issue between some regions or ISPs and Twitter. The investigation continues. Thank you for your patience everyone.

mnicolas80 · 2013-08-23T16:41:38.000Z

It’s not working for me too. Long timeout response without posting…

ss_tatar · 2013-08-23T17:10:34.000Z

Still same over here.

zmotrin · 2013-08-25T02:55:44.000Z

Still not working for me… Any update or new informations ?

ss_tatar · 2013-08-25T05:00:58.000Z

it’s been 4 days for me.

photorator1 · 2013-08-26T09:46:36.000Z

I got same issue using php and oauth that just stopped working. Nothing was changed in the code… was working, then just stopped.

The gist is this:
Error fetching remote https://api.twitter.com/1.1/statuses/update_with_media.json [ status 403 ] {“errors”:[{“code”:195,“message”:“Missing or invalid url parameter”}]}

ensight · 2013-08-26T10:16:05.000Z

Same issue here, it times out regardless of the size of media uploaded, and returns nothing (not even an HTTP header code). It worked fine previously.

JuanRentG · 2013-08-26T16:38:22.000Z

Last time it worked for me is August 21st with Abraham Williams code from there i’ve bee getting error codes 195, http code 0 or even null response. I have tried Abraham Williams php code (https://github.com/abraham/twitteroauth) , Matt Harris php code(https://github.com/themattharris/tmhOAuth/) and (https://github.com/J7mbo/twitter-api-php) all dont work at all for statuses/update_with_media.json

ss_tatar · 2013-08-26T17:38:30.000Z

Could anybody solved this problem ?