Curl Error 28 Operation Timed Out After 10000 Milliseconds
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta operation timed out after 10000 milliseconds with 0 bytes received Discuss the workings and policies of this site About Us Learn more operation_timeouted operation timed out after 10000 milliseconds with 0 bytes received about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack
Operation Timed Out After 0 Milliseconds With 0 Out Of 0 Bytes Received Paypal
Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you,
Operation Timed Out After Milliseconds With 0 Bytes Received
helping each other. Join them; it only takes a minute: Sign up Curl error: Operation timed out up vote 1 down vote favorite I have the following fatal error when trying to use Curl: PHP Fatal error: Uncaught HTTP_Request2_MessageException: Curl error: Operation timed out after 30000 milliseconds with 0 bytes received in /usr/share/php/HTTP/Request2/Adapter/Curl.php on line 200 Exception trace operation timed out after 5000 milliseconds with 0 bytes received Function Location 0 HTTP_Request2_Adapter_Curl::wrapCurlError('Resource id #12') /usr/share/php/HTTP/Request2/Adapter/Curl.php:200 1 HTTP_Request2_Adapter_Curl->sendRequest(Object(HTTP_Request2)) /usr/share/php/HTTP/Request2.php:959< in /usr/share/php/HTTP/Request2/Adapter/Curl.php on line 172 However, I can't see how to best debug it. There's no reference to any line of code I've written, only the HTTP_Request2 and Curl modules. What's the best approach to try and resolve this? php curl share|improve this question asked Feb 1 '14 at 17:25 alias51 1,878103383 have you tried debugging before and after the statements in your code that actually make the curl commands? try and find the offending request that way? from there you can try it command line, with the -v switch, and try and get more info that way. possibly the URL has now 404'd. –thescientist Feb 1 '14 at 17:30 add a comment| 1 Answer 1 active oldest votes up vote 8 down vote Your curl gets timed out. Probably the url you are trying that requires more that 30 seconds. If you are running the script through browser, then set the set_time_limit to zero for infinite se
here for a quick overview of the site Help Center Detailed answers to any
Curl "operation Timed Out After" Milliseconds
questions you might have Meta Discuss the workings and policies selenium operation timed out after 30001 milliseconds with 0 bytes received of this site About Us Learn more about Stack Overflow the company Business Learn more about operation timed out after 100000 milliseconds with 0 bytes received hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack http://stackoverflow.com/questions/21501159/curl-error-operation-timed-out Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Connection timed out after 10000 milliseconds in CURL and PHP Geocoder up vote 2 down vote favorite I have a script with a loop in which I execute the http://stackoverflow.com/questions/31472800/connection-timed-out-after-10000-milliseconds-in-curl-and-php-geocoder PHP geocoder function. The loop has more than 1000 iterations and the whole process takes some time. This is my script: for ($x = 0; $x < 1000; $x++) { //////////////////////////////////////////////////// // GECODE THE ADRESS AND GET THE COORDS $curl = new \Ivory\HttpAdapter\CurlHttpAdapter(); $geocoder = new \Geocoder\Provider\BingMaps($curl,$bingApikey); //$geocoder = new \Geocoder\Provider\MapQuest($curl,$mapQuestApikey); //$geocoder = new \Geocoder\Provider\ArcGISOnline($curl); //$geocoder = new \Geocoder\Provider\OpenStreetMap($curl); $result = $geocoder->geocode($matchesAdressRightValues[$x][0]); if (count($result)==0 || count($result)>1 ){ $bingSucUn = 'not_success'; array_push($arraySucUnsucBing,$bingSucUn); } else { //echo ('result'); //echo (count($result)); //echo ('Endresult'); $bingSucUn = 'success'; array_push($arraySucUnsucBing,$bingSucUn); } //var_dump($result); //////////////////////////////////////////////////// } // end for The problem is I get an error: ("Connection timed out after 10000 milliseconds"). How can I increase the limit? I have added this on top of my screen but its only for PHP not for the curl request: set_time_limit(0); Normally if I was using pure CURL and not integrated in the PHP Geocoder then I would do something like that: $ch = curl
past few weeks, but since last week, i always receive "Operation timed out after 30000 milliseconds with 0 bytes received". This look like an error https://twittercommunity.com/t/operation-timed-out-after-30000-milliseconds-with-0-bytes-received/11804 generated by tmhoauth.php when it doesn't receive any answer from the API after the timeout has been reached. I've try putting the timeout way higher and i still receive the same error. I'm just wondering if there's anything on twitter side that could cause this issue, but i guess this would have been reported already ... Just let me know operation timed where i can start to debug this! thanks, episod 2013-08-19 15:07:58 UTC #2 Are you on shared hosting? Sometimes IP addresses get temporarily blacklisted in response to abuse. ThatG33k 2013-08-19 15:13:44 UTC #3 I'm not, i'm on a dedicated server! I modified my script so it automatically retry on failure, and it can sometime takes up to 20 tries before operation timed out it goes through. So the code is working fine, but it seems like the API isn't answering back most of the time! ThatG33k 2013-08-19 17:21:00 UTC #4 I did a few tests under different classes (all PHP using cURL) and they all have the same issues, please note that using 1.1/statuses/update is working 100% of the time, but as soon as i add media, with 1.1/statuses/update_with_media it won't go through. episod 2013-08-19 17:35:16 UTC #5 OK, that rules out IP address blacklisting I think. When you say you retry on failure -- do you do so aggressively or are you using some kind of more exponential backoff? I know of some issues some developers have when uploading media -- what HTTP headers are you sending when you're making such a request? mnicolas80 2013-08-19 18:01:00 UTC #6 Hello,I am using Abraham Williams php code (https://github.com/abraham/twitteroauth) which was working perfectly,even after the API update from 1 to 1.1.Suddenly, the last days I rechecked the "update_with_media" method, which does not work (and it used to work). The code is the following:
$t