WP-cron not working?

19 February, 2009 Joost de Valk 25 comments, leave your own!

So when I moved to the (DV) server at MediaTemple, it turns out that my WP-Cron stopped working. I didn't notice for a while, until I found out that the new version of Tweetbacks didn't work for me anymore, and this was using wp-cron.

The fix turned out to be very simple, after some debugging with the help of Donncha: in my /etc/hosts file, 127.0.0.1 pointed not only to localhost, but also to yoast.com, and when you opened 127.0.0.1, you didn't get yoast.com. So I removed yoast.com from that line, and restarted apache, and tadaa! wp-cron started working again.

This might also cause issues for other people, which is why I post about it. It might, for instance, explain why people are having issues with the WP-Super-Cache garbage collection not working.

Let me know in the comments if this helps you, or whether you had to do other things to get it working!

Update: I ended up switching hosts over issues like this one. I'm now on WestHost, and all seems to be good. More info on my WordPress hosting experiences here.

Liked this post?
Subscribe to the RSS feed or to weekly email updates, right now!

  • LinkedIn
  • Sphinn
  • Twitter
  • Facebook
  • del.icio.us
  • StumbleUpon
Categories: WordPress

18 Responses to “WP-cron not working?”

  2. By Peter Thu, February 19th, 2009 at 15:49

    Just know that by removing yoast.com from the /etc/hosts could in theory disrupt other services that depend on name resolving and ip security.
    Accessing your MySQL for example. MySQL could do name resolving and block your external IP (I assume yoast.com resolves to an external IP right now) access to the tables.

    What did you get when opened 127.0.0.1 in Apache?

  3. By Paw Thu, February 19th, 2009 at 16:18

    Amazing blog you have here on yoast.com, i like your writing style! I have addet your feed to my rss reader.. I will look forward to the next post.

    Paw

  4. By Dave Ward Thu, February 19th, 2009 at 17:03

    Watch out, because that /etc/hosts line gets regenerated every time your (dv) restarts. There's a thread about it on the (mt) forums (in the (dv) section).

  5. By brad hart Thu, February 19th, 2009 at 21:04

    I noticed this had quit working too. I wouldn't even no where to start editing the file you mention so thanks for mentioning this. I have reverted to the pre-cron version which worked just fine for me, I think you will have a lot of people people in this same boat. Other than this upgrade change this has been a fabulous plugin so safe.

  6. By Donncha O Caoimh Fri, February 20th, 2009 at 23:01

    It reverts the hosts file? Ouch, that's bad!

    Brad - you should try to get this working because other WordPress functions and plugins won't work properly either. WP Super Cache uses wp-cron to delete it's expired files automatically, and WordPress scheduled posts relies on it too.

  7. By Henri Sat, February 21st, 2009 at 19:14

    127.0.0.1 pointed to only pointed to localhost is very, very strange. How is it possible?

  8. By Steen Öhman Sun, February 22nd, 2009 at 11:12

    Thanks for the tip.

    Had a client with the same problem ... now solved!

    Great site you have here ... I will back - as they say in California.

  9. By Malice Sat, March 14th, 2009 at 17:33

    That pretty much explains why at times my wordpress didnt publish scheduled posts. :D

  11. By qdinar Sat, April 11th, 2009 at 13:50

    http://wordpress.org/extend/plugins/wp-super-cache/faq/ :

    Check your access_logs for wp-cron.php entries. Do they return a 404 (file not found) or 200 code? If it's 404 or you don't see wp-cron.php anywhere WordPress may be looking for that script in the wrong place.

    i have wpmu main domain linked to 127.0.0.1 and wp-cron.php returns "200", i see in log file. so i think it works.

    i do not know why it may not work.

  12. By Al Mon, April 27th, 2009 at 21:47

    Where's hosts? I went into etc and theres no hosts

  13. By Brad Touesnard Sat, July 18th, 2009 at 13:45

    I've written a blog post about the problem with Media Temple (dv) / Plesk configuration and how to fix it:
    http://bradt.ca/archives/fix-wordpress-missed-schedule-error-on-media-temple-dv-plesk/

  14. By Billige mobiltelefoner Fri, August 14th, 2009 at 10:43

    very nice wordpress block, i gust love the design.

  15. By smilesquare Thu, September 10th, 2009 at 04:38

    After my debugging I also found that some scheduled posts not put into the cron queue that why some scheduled post can post correctly, and some not.

  16. By Rene Silva Mon, November 23rd, 2009 at 00:39

    Thanks, thanks ... It worked like charm. Cheers.

  17. By Christine Mon, November 30th, 2009 at 23:03

    Thanks so much for this. This is not the first time I've experienced weirdness with my dv. (ie way things are supposed to be.) Thank you again. :)

  18. By Jehzeel Laurente Wed, December 2nd, 2009 at 18:37

    oh this is weird. I still can't fix it until now. Maybe I should move to westhost just like what you did. Hehehe.

2 Tweetbacks to “WP-cron not working?”

  1. By seomasterlist (seomasterlist) Sun, February 22nd, 2009 at 17:17

    WP-cron not working?: So when I moved to the (DV) server at MediaTemple, it turns out that my WP-Cron stopped wo.. http://tinyurl.com/cogscg

  2. By johnetec (johnetec) Wed, April 22nd, 2009 at 04:37

    I will be very glad when we are done moving domains to our new awesome vps. http://yoast.com/wp-cron-issues/

Comments closed, if you feel you have something to say:
drop me a line.

5 Trackbacks to “WP-cron not working?”

  1. WP Super Cache 0.9.1 - Thu, February 26th, 2009 at 14:14
  3. 如何安装使用WP Super Cache « Wordpress插件 - Thu, September 10th, 2009 at 17:30
  4. zzzch » WP Super Cache最详细教程 - Tue, September 22nd, 2009 at 14:56
  5. WP Super Cache使用全攻略 | win7研究社 - Sat, November 14th, 2009 at 16:44