WP-cron not working?
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. More info on my WordPress hosting experiences here.
oh this is weird. I still can’t fix it until now. Maybe I should move to westhost just like what you did. Hehehe.
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. :)
Thanks, thanks … It worked like charm. Cheers.
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.
very nice wordpress block, i gust love the design.
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/
Where’s hosts? I went into etc and theres no hosts
http://wordpress.org/extend/plugins/wp-super-cache/faq/ :
Try my plugin: http://blog.5ubliminal.com/48 . And … it works ;)
That pretty much explains why at times my wordpress didnt publish scheduled posts. :D
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.
127.0.0.1 pointed to only pointed to localhost is very, very strange. How is it possible?
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.
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.
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).
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
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?
I have a related post on WordPress missed schedule on my blog.