wfmatt

Hi Frederic,

Based on the responses from your hosting company, I would say the responsibility to fix this issue lies with them. Killing processes that are consuming too much memory is an OS level defense to prevent the server from crashing. In the case of MySQL, the settings should be tuned so that MySQL uses an appropriate amount of memory for the services running on that server. Additionally, swap space could be added to the server for low-memory environments. We do take performance seriously, and strive to make Wordfence work on as many hosting environments as possible, but this issue looks to be the result of a server misconfiguration.

Thanks,
Matt Barry, Wordfence Lead Developer

Hi jbalyo,

I’ve confirmed this is a bug, and we will be releasing a fix for it in the next release. Sorry for any inconvenience!

Thanks,
Matt

Sorry to hear that you’re not satisfied with the new Live Traffic layout. I’ve filed a bug to address the issues with using button tags vs anchor tags, and pausing the Live Traffic feed upon scrolling past the first entry or hovering over the buttons. The fix will be available in an upcoming maintenance release.

Thanks Jo. I’ve filed a bug to address the plugin conflict with Opening Hour which will be fixed in an upcoming maintenance release.

wflogs is a new directory introduced in 6.1.1 which contains file necessary for the Web Application Firewall to run. The files and the directory itself need to be writable by the web server user for the Firewall to run, but the rest of Wordfence will continue to function normally otherwise.

@gbeddow To answer your question about the permissions on your files and directory, this can be caused by updating Wordfence via WP-CLI or another command line utility (run by the admin user in your case). I would recommend changing ownership of the files and the directory to your web server’s user and making them writable by only that user. We will be adding an installation process using WordPress’s File System API to help create those files with the correct permissions in a maintenance release in the near future.

Hi webmasa,

Under Wordfence > Diagnostics, can you click ‘Send Report by Email’ (at the bottom) to samples (at) wordfence.com? I haven’t been able to replicate this, but it may be a plugin conflict or something similar.

Thanks,
Matt

Hi gbeddow,

It looks like the config.php (currently 0600) file needs to be writable by the web server and the wflogs directory (currently 0755) itself also needs to be writable. You can either change the permissions on the file and directory, or change the owner to the web server’s user. Either way should work, let me know if you still run into issues.

Thanks,
Matt

Hi RayBoyd1455,

It should be safe to proceed, the Firewall installation procedure can include that file to maintain your site’s current functionality.

Thanks,
Matt

It’s possible it’s a plugin or theme conflict. If you post a list of installed plugins and themes, it could help to narrow things down.

Also, are these pages accessible once logged in?

/wp-admin/options.php
/wp-admin/network/

Hi allm,

I’ve confirmed this is a bug with the new version, we’ll be releasing an update in the near future to address it.

Thanks,
Matt

Hi caramiame,

Can you make a new post for this issue? I believe your multisite issue is different from opencuny’s.

Thanks,
Matt

Great, I’ll make a note that the .htaccess code configured the Firewall correctly.

If that’s the full path, the file /var/www/html/wp-content/plugins/wordfence/waf/bootstrap.php should exist. If it doesn’t, can you reinstall Wordfence? You should be seeing a fatal error on your site if it doesn’t.

If you’ve updated your php.ini with the auto_prepend_file setting, you should be able to see that value under Wordfence > Diagnostics > Click to view your system’s configuration in a new window (at the bottom), then find auto_prepend_file under Core.

Hi opencuny,

Are you able to provide more detail about the error? If you have error logs from the web server, that would be helpful in diagnosing the problem.

Thanks,
Matt

Hi FxMan,

If you’ve already completed the Firewall installation, you can change the .htaccess permissions back to 0444. Wordfence only needs write-access to it for the install.

Thanks,
Matt