dmann258

Thanks for the info, wfasa

I uncommented the “Include conf/extra/httpd-mpm.conf” in the standard Apache httpd.conf file. Then in the httpd-mpm.conf file I added the ThreadStackSize 8388608 to the IfModule mpm_winnt_module section. After restarting the Apache service and upgrading to WordFence 6.1.14 the site was able to function without issues. Thanks for the help!

I have just completed the upgrade to PHP 5.6.25 using the same configuration at PHP 5.5 and got the following error once WordFence 6.1.14 was loaded for a few minutes. Note: the site does not generally lockup right away, sometimes it will function for up to 5 minutes before it stops responding. Here is the Windows Event Viewer information:

Faulting application httpd.exe, version 2.4.23.0, time stamp 0x577631b1, faulting module php5ts.dll, version 5.6.25.0, time stamp 0x57b60661, exception code 0xc00000fd, fault offset 0x0011f322, process id 0x86c, application start time 0x01d1fe56001984e1.

I have had the same issue on 1 of the 30 sites I support since WordFence 6.1.11 (6.1.10 still functions). The environment is a Windows 2008 Server running Apache 2.4.23 and PHP 5.5.38. If WordFence 6.1.11 or higher is activated the site may function for a few minutes, then users will get a Page cannot be displayed message. The Apache logs do not report any activity once the site stops functioning.

Here is the error from Windows Event Viewer:
Faulting application httpd.exe, version 2.4.23.0, time stamp 0x577631b1, faulting module php5ts.dll, version 5.5.38.0, time stamp 0x578fc4d8, exception code 0xc00000fd, fault offset 0x0011f082, process id 0xf64, application start time 0x01d1faf70a7d527e.

Can you please provide the file or database entry that is modified when one disables the Firewall. Perhaps manually updating the setting will allow it to appear correctly in the interface, regardless of the define (‘WFWAF_ENABLED’, false); setting in the wp-config.php.

Thanks for the reply. I had the same results as hmkay after disabling the config caching on the Diagnostics page.

Please note, while a WAMP environment is running on a Windows server, it is not IIS. I am running Apache, PHP and MySQL. I currently support over 30 sites in this environment and this is the first plugin that has not functioned correctly outside of an acknowledged programming issue in over 5 years. I have worked with a number of developers who did not even know the server was a Windows server because the Apache, PHP, and MySQL environment behaved the same as if it was running on Linux.