Report this

What is the reason for this report?

Wordpress Error

Posted on February 18, 2013

Hello, I have a droplet setup correctly running wordpress with Linux, nginx, MySQL, PHP (LEMP) stack on Ubuntu 12.10 X64 Server.

I got the following error in wordpress.

Warning: fopen(http://example.com/wordpress/wp-cron.php?doing_wp_cron=1361221148.57854199409284738473):failed to open stream: HTTP request failed! in /var/www/example.com/public_html/wordpress/wp-includes/class-http.php on line 921

Is this cron job related? If so how do i setup a cron job for wordpress, does it need one?



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Thanks dave, <br> <br>Yes you are correct. I added permissions to the wordpress directory to allow my ftp user to edit files in filezilla but that changed my permissions i had previously set for wordpress. <br> <br>The solution: <br>sudo chown -R www-data:www-data /var/www/example.com/public_html/wordpress <br> <br> <br>

it looks like wordpress has its own internal cron job but it’s unable to access that file. Have you tried to access the HTTP url manually to see what error word press is getting?

For reference, WordPress has it’s own internal CRON system which is fired off when visitors access your site. This is how scheduled posts are regulated. The same applies to [insert item] if it’s on a schedule (i.e. backups, etc). <br> <br>Normally when you see “doing_wp_cron” in the URL or error log, it’s due to the internal CRON being unable to run, or, you’ve disabled the internal CRON in favor of an external (i.e. crontab -e or through your control panel GUI). <br> <br>The downside, the internal CRON is fired off for each visitor, which can stress a server on larger sites. Just an FYI, if you’re running a large installation with quite a few visitors hitting the site at all hours of the day, an external CRON run may be better. That just from experience working with sites that continually see hundreds of thousands of [unique] visitors a month. On smaller installations it’s fine and really won’t do much harm, especially if you have your own VPS.

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.