Viewing 5 replies - 1 through 5 (of 5 total)
  • I would never chmod anything to 000

    chmod 000 denies read, write, and execute permission to yourself, your group, and everyone else.

    Joe

    (@shopping-guide)

    A lot of requests from where? If these are third party ip addresses you should be looking at setting up adequate firewall security rules.

    Joe

    Thread Starter romson

    (@romson)

    Yes, i know, but now that wp-cron is chmod 000 it seems my site is loading faster. What is the downside of wp-cron at chmod 000?

    Thread Starter romson

    (@romson)

    I was having a ddos on my site and wp-cron was getting a lot of requests from 192.168.xx.xx IP’s

    When i blocked the IP in my .htaccess it just changed. Now i have blocked the whole range.

    This is also why i turned wp-cron to chmod 000 to avoid it from being read. It;s just i don’t know what the downside is of leaving wp-cron at 000. Do you possibly know that?

    Joe

    (@shopping-guide)

    The 192.168.xx.xx IP’s are from a local source, i.e. your server’s firewall/router internal addresses, not an external third party.

    CHMOD 000 is effectively disabling/deleting the wp-cron file since nobody can access or use it, which I don’t think is a wise idea, because WordPress will likely be carrying out regular maintenance tasks through the cron jobs file.

    Joe

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘CHMOD 000 wp-cron.php’ is closed to new replies.