nlebrozec

Hi,

Great thread as I have read the same news and wondered how Wordfence would react to this change.
I have tested it on a staging environment and could not see any error so far…

But how can you tell the firewall extended protection (and the whole firewall in general) is still loading correctly?

Thanks to shed some light here ??
Nico

Hi there,

Have the same concern here as we use WP Engine and Wordfence. According to WP Engine Support, we should choose Apache + mod_php.
That’s what I’ve done so far…
Unfortunately, even if the .htaccess file has been modified accordingly it seems some problems are here based on the Diagnostics page.
Checking if web server can read from ~/wp-content/wflogs -> File “attack-data.php” does not exist, File “ips.php” does not exist, File “config.php” does not exist, File “rules.php” does not exist

And that’s true, these files do not exist in the wflogs folder.

I thought about permission issues but it seems that the web server user (wpe-user) is the same as the owner of the wflogs folder.

Running a WP CLI command generates a PHP Warning saying the rules.php file is missing, which is correct.

How can we get those files to be put in the wflogs folder as mine is empty apart from a “GeoLite2-Country.mmdb”.

I’ve also tried to delete this folder and every time it’s generated again, still none of the expected PHP files are present.

Any guidance is welcome to fix this and make sure the extended WAF is correctly working on WP Engine.

Regards,
Nico

Hi @wfdave and @wfgerald,

Just to let you that I am experiencing the same issue. wflogs existed. I deleted it but the issue persists. I have the same warning messages doing a WP CLI command for example:
wp plugin update –all –dry-run

Thanks for letting us know what this problem is.

Regards,
Nico