Hi,
Sorry for the trouble. Wordfence is not officially supported on Windows platforms (see https://docs.wordfence.com/en/Wordfence_system_requirements ), but we have heard of users having success.
We have had some reports of issues using the new firewall feature on Windows servers, so if you have trouble with it, you can add this line to wp-config.php to disable the firewall feature:
define('WFWAF_ENABLED', false);
If you’ve already enabled the “Extended Protection”, add the code to the wordfence-waf.php file instead, just below the “<?php” line.
Other Wordfence features will still work normally in this case.
-Matt R
Thanks for the fast reply Matt. Appreciate it!
I see that Extended Protection says it’s enabled, and its behavior supports that, but I have not added any code to the php.ini file (we have multiple sites on the server, so not sure how that would work). So I will try to disable the firewall in the config file. Again, I really appreciate the fast reply. We are unable to submit any posts with an iframe in them, and cannot whitelist.
I just added define('WFWAF_ENABLED', false); to the wp-config file and it didn’t appear to change anything. Any thoughts on that?
Oops. Wrong site! Perhaps it will work if I put the code in the right place. (duh)
OK – I confirmed that it is in the right place now, and when I go to the firewall page, the button is still indicating enabled, and protecting. Shouldn’t this be red now?
Hi,
The WFWAF_ENABLED line might have been too far down in the wp-config.php file, if it was after the last section — if the Extended Protection wasn’t enabled, that is most likely.
The latest version of Wordfence does fix the issues on Windows servers though, so let us know if you’re still having any trouble after updating. Thanks!
-Matt R
