The HTTP response test get a false http status (503)

Same here. After upgrading to 3.0.4 this error started to show up.
The error is not present in backup jobs where I just run a optimize or check of the database.

My failing job includes:
DB Check
DB Backup
DB Optimize
XML export
Plugins

The screen error says:

The HTTP response test get a error "Connection time-out"The HTTP response test get a false http status ()

There is no php errors, so this is a connection issue, added in 3.0.4 ??

After re-reading the changelog, I guess this error come from the following:

Added: Server connection test on run now.

EDIT: READ PLEASE:

if I create a job which is actually doing a DB Check + DB Optimize, this error is present too. Evidently, the conenction test is done here too.

That’s the same setup on my backup, with both check and optimize, so we have similar setups.

By chance, what php version is your server running? I’ve got 5.3.21 and I’m thinking this could be the problem since it seems his latest update requires 5.3.33.

From the plugin front page…
To use the Plugin with full functionality PHP 5.3.3 with mysqli, FTP,gz, bz2, ZipArchive and curl is needed.

What do you think?

I have

• PHP 5.2.17 with mysqli, FTP, gz, bz2, zip, curl.
• MySQL 5.5.30.
• WP 3.5.1.
• cURL 7.24.
• Alternative WP Cron: Off.
• PHP Memory limit: 256 MB

Okay, now looking @ the plugin front page again, it reads both…

WordPress 3.2 and PHP 5.2.6 required!

To use the Plugin with full functionality PHP 5.3.3 with mysqli, FTP,gz, bz2, ZipArchive and curl is needed.

…so which is it? I’m not asking you, I’m just trying to figure it out myself!

Let’s hope the author comes by since it seems he’s getting closer to getting a handle on resolving the plugin issues.

The responce test ist a simple HTTP Request to the Server itself.

That will be done on every time ‘run now’ will clicked.

If this massge pop’s up the job can’t startet normely.

This massage can pop’s up if:
– the hoster not allow this kind of connections (WP_ALTERNATE_CRON can help)
– the blog behind a autentication (401) and the autehntication data not entered (Settings | Network ).
– The Server can not resolve its own hostname.
– A plugin or theme blogs the request (will be done in frontend)
– and many more.

Best is fixing the real problem. Because the WordPress cron works in the same way.

So Daniel, are you saying that there is “fix” coming soon???

The reason I ask, even though I’m getting the http request message, it is still not taking a backup and the last backup I have was with the previous version.

Would you recommend that we go back to version 2 until this gets resolved?

@automatedkid If version 2.x worked as expected in your hosting environment and version 3.x doesn’t, opting for a temporary downgrade sounds reasonable.

I agree, Caspar, thanks for the comment. I already downloaded the previous version, just hoping to hear whether there is another update in the pipeline or not.

I will stick to version 3.0.3 since that was the last version that actually work well.

I am having the same problem and solved it by removing the ‘Anticipate’ plugin from Elegant Themes. Hope this helps someone.

You can test it again eith the version that is now out.

Same problem here. Upgraded 3.0.7 and now it’s broken and throws that message. Very sad.

OK. Uninstalling, reinstalling and reconfiguring the plugin fixed my problem.