ilicmac

Hi Janet,

Apologies for the slight delay. I was struggling to deactivate the plugin as the site had extended protection enabled manually. I couldn’t locate any of the relevant files to remove the extended protection. I eventually managed with the help of Wordfence Assistant, which allowed me to “remove all Wordfence data in the database and elsewhere”.

I have now reinstalled Wordfence and sent the diagnostics report by email.

Look forward to hearing from you.

Tamara

Hi Janet,

Thank you for getting back to me – appreciate your time.

The permissions for the WordPress site’s directories are already 775, which grants greater access than 755. I don’t believe downgrading would make a difference but please do let me know if you disagree.?

I don’t have a wflogs folder at all to check its permissions.??

Process owner is www-data for all existing WordPress directories.

Thank you for suggesting I switch to using the MySQLi storage engine instead. Not sure if I did something wrong but the issue hasn’t been resolved. I defined WFWAF_STORAGE_ENGINE?in wp-config.php above the “/* That’s all, stop editing! Happy blogging. */ ” line as instructed and updated the file paths.

I didn’t have an existing wordfence-waf.php file so I created one. You can see its entire contents in the screenshot below:

Diagnostics report before setting Wordfence to use MySQLi:

Diagnostics report after setting Wordfence to use MySQLi:

The only difference is that the red ‘X’ has disappeared from the wflogs related tests. Not sure if that means anything? I have sent a report by email so hopefully you / your team can take a look. 

Thank you for your energy and patience.

Tamara