[Plugin: WP Super Cache] Still getting wp-cron.php error after editing /etc/hosts

  • Michael Dance

    (@seventhsteel)


    13 years, 10 months ago

    Using the WP Super Cache Plugin, I’m getting the “Unfortunately WordPress cannot find the file wp-cron.php” error, so I took the steps outlined in the Plugin’s troubleshooting section and edited my /etc/hosts file to get rid of the 127.0.0.1 line. Then I restarted Apache. But I’m still getting the same error, so my question is…any other ideas?

    Also, will anything bad happen if I turn WP Super Cache on anyway?

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Arturo emilio

    (@anduriell)

    13 years, 10 months ago

    No actually you should try with
    127.0.0.1 yourdomain.com

    that will fix it. Sometimes if you have any hardware (like router or firewall) with webmin in port 80 it will not work.
    Would be very nice if WP and WPMU would check wp-cron.php other way than checking the url. But that’s not an issue for WP-supercache i think it’s a limitation from WP and WPMU.

    Thread Starter Michael Dance

    (@seventhsteel)

    13 years, 10 months ago

    Ah I gotcha, thanks. I added that, and it worked, the error message disappeared. Then I actually turned Super Cache on, and the error message came back. ?

    deanpence

    (@deanpence)

    13 years, 10 months ago

    Actually, /etc/hosts should typically read something like:

    127.0.0.1 localhost localhost.localdomain

    I was having this problem myself with a proper /etc/hosts file, but it was a newly transferred domain, and the local resolver was resolving the domain to the old IP. After I forced the resolver to dump its cache, wp-cron.php was once again visible.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘[Plugin: WP Super Cache] Still getting wp-cron.php error after editing /etc/hosts’ is closed to new replies.