Error with Facebook posts

Please see the answer in the FAQ – #1.10:
https://www.nextscripts.com/support-faq/#a110

I already saw it, before even posting. Tried sugested even changed to 30sec, add_filter(‘http_request_timeout’, function(){return 30;});

Strange thing is that everything works with TEST from settings, when story is posted imediately, even when doing repost from post.
Only problem is when post is scheduled, and needs to post to FB when it becomes alive.

You still need to talk to your server admin. There could be numerous reasons for this, such as active protection that blocks all outgoing connections from background services.

What background services ???
I have a talk with my server admin. cUrl operating normaly (proved by other plugins and stuff that work normaly). Maybe, just maybe FB problem, with not being able to fatch page in time. But why every time we tried manual post or test post from settings it works normaly. Just scheduled post are problem. They normally appear on our blog. So wp-cron is functional. Server cron also.

When you manually make a post it’s interactive session.
When cron makes a post it’s a background process.

Some servers could treat them differently. Also 5 seconds timeout is very short, please try to increase it.

As I said wp-cron (a virtual background cron process) is functioning just OK. No errors nowhere. Even in Log of your plugin (whera I turn on cron loging) no cron errors. Also as you may have read before, I already increase timeout to 30sec add_filter(‘http_request_timeout’, function(){return 30;});

If you are still getting

>> Operation timed out after 5001 millisecond

after you put

add_filter(‘http_request_timeout’, function(){return 30;});

it means that your server is set to ignore http_request_timeout parameter.

It’s another reason to talk to your server admin.

Me too have same problem. And googled and found out that many users who are using NextScripts have same problem. Twitter and others works without problem. But NextScripts and facebook have alweays same error. If you repost it, it works normally.

And I AM SERVER ADMIN! And in server side everything works fine. And Nextscripts plugins are only one which gives errors. And since NextScripts blaming server admins here, it means that they have not have any clue what’s wrong and they don’t know what his scripts doing. I am thinking to go back with IFTTT, it works without any problems.

If you are using a plugin (like NextScripts) which are not properly optimized, you may get this error. I am suggesting to go thru the optimization process. If you do not know how to optimize your plugin, then google search helps. Hopefully one day they will optimize that plugin. At the moment you need to check that source code yourself and rewrite it.

Also about that timeout, I do not suggest to rise it to 30. 5 should be okay, but 10s is max. Anything over that is too much. And if you add ot to your theme functions.php file, it does not help you. It would not work, because only timeout which matters is in wp-includes folder in class-http.php file. Change your timeout there to make it work. But as I said, anything over 5s means that this plugin is not optimized enough to work with default settings.

Hi edragonxx.

It’s so nice that you think you are smarter then us.

Here what we “don’t know” about our plugin. It’s actually quite simple.

Here is the whole code that makes a post to Facebook:
File /inc-cl/fb.api.php line 76:

$response = wp_remote_post( $destURL, array( 'method' => 'POST', 'httpversion' => '1.1', 'timeout' => 45, 'sslverify'=>false, 'redirection' => 0, 'body' => $mssg));

As you can see, we obviously not smart enough to do anything on our own.

Plugin does not connect to Facebook by itself.

It asks WordPress to do it by calling standard WordPress function wp_remote_post().

WordPress also does not connect to Facebook by itself when asked. It asks PHP to do it by calling standard php curl_exec() function.

PHP also does not connect to Facebook by itself when asked. It asks the system binary library that installed on the server and called “cURL” to do it.

That library connects to Facebook. That library generates error and passes it to PHP that passes it to WordPress that passes it to the plugin.

Only your hosting provider or server admin could answer why that system binary library generates that error and do something about that.

You as a server admin can go through your system logs and find the exact cause why the tcp call has failed.

Plugin, wordpress, and even php itself can’t access and analyze the system logs. All we can get from the is the error.

With all that said, lets try to follow your suggestion and optimize our code.

Let’s see what can be optimized in that one single call to that standard WordPress function wp_remote_post().

Right. There is nothing to optimize.

PS: Yes a lot of people have this issue. Mostly because all other issues we are fixing and people are not getting them anymore. Unfortunately this issue is coming from server misconfiguration and it is not possible to be fixed from our side.