Title: Timeout issues Last modified: August 30, 2016 --- # Timeout issues * Resolved [shmulikk](https://wordpress.org/support/users/shmulikk/) * (@shmulikk) * [10 years, 6 months ago](https://wordpress.org/support/topic/timeout-issues-1/) * Hello, We are using the latest (4.3.1) version and we suffer from timeout issues from time to time, while the `backend/index.php` tries to communicate with 3rd party services like Google and Facebook (not anyone specific). I’ve grabbed more info using NewRelic and I can see that the `curl_multi_exec` run for 480 seconds( 8 minutes) before it timeout. The strange thing is that the timeout for the http client set in our shariff.json is 10 seconds for timeout and 5 seconds for connect_timeout. * Googling about it got me to a possibly related known defect in curl library where` curl_multi_exec` is known to ignore the timeouts: [http://sourceforge.net/p/curl/bugs/797/](http://sourceforge.net/p/curl/bugs/797/) * Another related post: [http://stackoverflow.com/questions/2297749/curl-multi-hanging-ignoring-timeout](http://stackoverflow.com/questions/2297749/curl-multi-hanging-ignoring-timeout) * 1. Does anyone else suffer from the same issue (occasional timeouts for the backend/ index.php script)? 2. Any chance someone already implemented the suggested fix/ workaround in the curl bug above? 3. Maybe I got it wrong and the issue is caused by something else – but for sure I see `curl_multi_exec` loading for 480 seconds every time a user get a timeout for getting social counts. * Best, Shmuel. * [https://wordpress.org/plugins/shariff/](https://wordpress.org/plugins/shariff/) Viewing 15 replies - 1 through 15 (of 17 total) 1 [2](https://wordpress.org/support/topic/timeout-issues-1/page/2/?output_format=md) [→](https://wordpress.org/support/topic/timeout-issues-1/page/2/?output_format=md) * [dzmitry_hubin](https://wordpress.org/support/users/dzmitry_hubin/) * (@dzmitry_hubin) * [10 years, 6 months ago](https://wordpress.org/support/topic/timeout-issues-1/#post-6553676) * Hi all, also interested to figure out how we can solve that issue. * Plugin Author [Jan-Peter](https://wordpress.org/support/users/starguide/) * (@starguide) * [10 years, 6 months ago](https://wordpress.org/support/topic/timeout-issues-1/#post-6553824) * Hey, * I’m sorry, I haven’t had the time yet to look into this. I’ll try to get to around it next week. * JP * [oliverkohl](https://wordpress.org/support/users/oliverkohl/) * (@oliverkohl) * [10 years, 5 months ago](https://wordpress.org/support/topic/timeout-issues-1/#post-6553851) * Hi, any update on this issue? I’m also curious how this can get resolved. * Thanks, Oliver * Thread Starter [shmulikk](https://wordpress.org/support/users/shmulikk/) * (@shmulikk) * [10 years, 5 months ago](https://wordpress.org/support/topic/timeout-issues-1/#post-6553856) * Hi JP, Any chance you take a look on it? Just to get some update?… * Best, Shmuel. * Thread Starter [shmulikk](https://wordpress.org/support/users/shmulikk/) * (@shmulikk) * [10 years, 5 months ago](https://wordpress.org/support/topic/timeout-issues-1/#post-6553857) * Adding a screenshot to make it easier: [http://snag.gy/wzbpB.jpg](http://snag.gy/wzbpB.jpg) * Plugin Author [Jan-Peter](https://wordpress.org/support/users/starguide/) * (@starguide) * [10 years, 5 months ago](https://wordpress.org/support/topic/timeout-issues-1/#post-6553864) * So, finally an update. * I completely rewrote the backend to replace the original backend from Heise and therefore also got rid of the whole ZendFramework. The new version is a lot lighter than the old one and uses all the nice tools WordPress provides. This should take care of all the timeout and cUrl issues. * The new version is currently in the testing phase and should, if we don’t find any major bugs, be release in the next couple of days. * Regards, JP * Thread Starter [shmulikk](https://wordpress.org/support/users/shmulikk/) * (@shmulikk) * [10 years, 4 months ago](https://wordpress.org/support/topic/timeout-issues-1/#post-6553865) * :thumbs-up: waiting to give that a test drive * Plugin Author [3UU](https://wordpress.org/support/users/3uu/) * (@3uu) * [10 years, 4 months ago](https://wordpress.org/support/topic/timeout-issues-1/#post-6553866) * Version 3.1 has the new backend now. Please give it a try. * Thread Starter [shmulikk](https://wordpress.org/support/users/shmulikk/) * (@shmulikk) * [10 years, 4 months ago](https://wordpress.org/support/topic/timeout-issues-1/#post-6553867) * Hi 3UU, I see the new 3.1 plugin here. * I will have it tested and get back with feedback until the end of the month. * Thanks. * Thread Starter [shmulikk](https://wordpress.org/support/users/shmulikk/) * (@shmulikk) * [10 years, 4 months ago](https://wordpress.org/support/topic/timeout-issues-1/#post-6553869) * It seems like the worst response time is now 45 seconds which is in line with the configured timeout for the googleplus backend. [http://snag.gy/D32L0.jpg](http://snag.gy/D32L0.jpg) * That’s good enough for me. (Tested 3.2.0) Thanks. * Plugin Author [Jan-Peter](https://wordpress.org/support/users/starguide/) * (@starguide) * [10 years, 4 months ago](https://wordpress.org/support/topic/timeout-issues-1/#post-6553870) * Hi shmulikk, * well, good to hear. I still think 45 seconds are kind of long to wait for some share counts. I’ll therefore reduced it with version 3.3.1. If it doesn’t work out, we might increase it again, but for the moment I would like to see, if we can live with a shorter timeout here. * Thanks for testing! * JP * Thread Starter [shmulikk](https://wordpress.org/support/users/shmulikk/) * (@shmulikk) * [10 years, 4 months ago](https://wordpress.org/support/topic/timeout-issues-1/#post-6553871) * Hi, Version 3.3.1 contain some odd files on the root dir (pot files) is it expected? * Plugin Author [Jan-Peter](https://wordpress.org/support/users/starguide/) * (@starguide) * [10 years, 4 months ago](https://wordpress.org/support/topic/timeout-issues-1/#post-6553872) * Hi, * just downloaded the current version from wordpress.org and there are no .pot files in the root dir. What are they called? * JP * Plugin Author [3UU](https://wordpress.org/support/users/3uu/) * (@3uu) * [10 years, 4 months ago](https://wordpress.org/support/topic/timeout-issues-1/#post-6553873) * There are no pot-files in the plugin. Please have a look at [https://plugins.svn.wordpress.org/shariff/trunk/](https://plugins.svn.wordpress.org/shariff/trunk/) However I have an idea of what it could be. Do you have an multi-language plugin installed like “CodeStyling Localization” or do you use “WPMU”? These tool try to check all strings in a new/updated plugin and use po/pot-files. * Thread Starter [shmulikk](https://wordpress.org/support/users/shmulikk/) * (@shmulikk) * [10 years, 4 months ago](https://wordpress.org/support/topic/timeout-issues-1/#post-6553874) * Strange I don’t see those files when downloading now… Forget it. Viewing 15 replies - 1 through 15 (of 17 total) 1 [2](https://wordpress.org/support/topic/timeout-issues-1/page/2/?output_format=md) [→](https://wordpress.org/support/topic/timeout-issues-1/page/2/?output_format=md) The topic ‘Timeout issues’ is closed to new replies. * ![](https://ps.w.org/shariff/assets/icon.svg?rev=2006307) * [Shariff Wrapper](https://wordpress.org/plugins/shariff/) * [Frequently Asked Questions](https://wordpress.org/plugins/shariff/#faq) * [Support Threads](https://wordpress.org/support/plugin/shariff/) * [Active Topics](https://wordpress.org/support/plugin/shariff/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/shariff/unresolved/) * [Reviews](https://wordpress.org/support/plugin/shariff/reviews/) ## Tags * [guzzle](https://wordpress.org/support/topic-tag/guzzle/) * [guzzlehttp](https://wordpress.org/support/topic-tag/guzzlehttp/) * [performance](https://wordpress.org/support/topic-tag/performance/) * [timeout](https://wordpress.org/support/topic-tag/timeout/) * 17 replies * 5 participants * Last reply from: [3UU](https://wordpress.org/support/users/3uu/) * Last activity: [10 years, 4 months ago](https://wordpress.org/support/topic/timeout-issues-1/page/2/#post-6553876) * Status: resolved