• Resolved luminsol

    (@luminsol)


    Hi, just wanted to let you know that if you set Blank HTTP headers in the firewall section, cron will break. This is because the WordPress cron does not set any headers. This will result in the server’s IP address being added to the permanent block list. In my case, it was an IPv6 address.

    Not sure if there’s an easy way for the plugin to automatically detect the server’s IP address and whitelist them?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

    Hi @luminsol,

    WP security > Firewall > Advanced Settings tab have Allow list to allow IPs for which Firewall rules are not checked. Please add there your IP.

    https://snipboard.io/fay30S.jpg

    If still issue let me know.

    Regards

    Thread Starter luminsol

    (@luminsol)

    Yeah, that solves the problem, but you should make a note in the page so people are aware this can break cron and to add the IP address to the whitelist page.

    Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

    Hi @luminsol

    Glad to know that solved the problem,

    I will create an internal ticket for this, so if CRON running locally It should not allow a firewall rule.

    Regards

    Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

    Hi?@luminsol

    We have tried check by enabling the WP Security > Firewall > Internet bots tab – Ban POST requests that have a blank user-agent and referer: enabled.

    The general WordPress cron events run using WP control plugin and using php {pathtowp}/wp-cron.php but can not replicate the issue.

    Can you please let me know how the cronjob is set and how it is running for the WordPress?

    Regards

    Thread Starter luminsol

    (@luminsol)

    Nothing special, just the default WordPress cron setup. Perhaps it something to do with my web hosting server config. I don’t know. Anyway, you can close the case as I have now changed to Wordfence.

    Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Setting Blank HTTP headers breaks cron’ is closed to new replies.