wfasa
Forum Replies Created
-
Hi all,
@asaracena thanks for your input. We have suspected this mainly affects GoDaddy sites for some reason but we haven’t yet been able to figure out exactly why. We’re continuously investigating to see if we can get to the bottom of it.
For anyone else reading this, if this has happened to you you can choose to disable automatic update of Wordfence and do the updates yourself manually instead. It’s not the most convenient solution but it should prevent it from happening again. It’s important that you then have Wordfence set to alert you about “warnings” so you can get notified when it’s time to update the plugin.
Hi @bobimg,
Emails should only be going to the email entered in the field to receive alerts. But anyone who is admin on a site can see the Wordfence plugin (unless it’s a multisite, then super admins are the only ones who can see it). Is it possible that the admin in question saw logins on the Wordfence Firewall Dashboard?If not, I’d suspect you may have a plugin on that site which forwards all emails that are sent via wp_mail to a specific address. Wordfence uses the WordPress core function wp_mail to send emails, and occasionally we’ll see some strange issues when other plugins hook in to wp_mail as well. It’s definitely not common but wanted to mention it just in case.
Hi @jedi82!
If you are no longer using Wordfence, you can delete all Wordfence related tables. It’s also possible to have Wordfence do this automatically for you if you enable the option to “delete Wordfence tables on deactivation” before you deactivate the plugin.Hi @essep,
This sounds like it might be a caching issue. Resources aren’t supposed to be cached in the WordPress admin environment but we do occasionally see that happening. This would explain why installing an older version works, the cache thinks those files exist but it doesn’t see the new ones.If you try clearing all cache in any WordPress plugins, content delivery networks and also in your browser, that would probably fix it. I’d recommend clearing them one at a time and testing in between so you can narrow down which one is causing it.
Hi @levdesign,
Sorry for the late reply. It is accurate that the files in the wflogs folder regenerate if they are deleted. The wflogs folder contains the files that make up the immediate memory of the Firewall. The reason for this is that the Firewall needs to load before WordPress itself loads and at this point, a connection to the database has not yet been established.Most likely this is what it looks like, meaning it’s a permissions problem with the wflogs folder. You can try adding this constant to the very start of wordfence-waf.php to see if that makes a difference:
define('WFWAF_LOG_FILE_MODE', 0660);If that helps, then it means that owner only write permissions don’t work with your wflogs, possibly because you have multiple server users running in the environment? The thing to look out for here is if there are other users running on the server other than the one WordPress is currently running as (you can see the name of this user on the Wordfence diagnostics page showing up as the “process owner”).
Let me know how it goes!
Hi @stephinseattle,
I believe the failing plugin updates on GoDaddy are a separate issue from the scan problems on Heart hosting. GoDaddy do have some specific configurations that may be related to those issues, but they are not setting options on Wordfence scan or anything like that.@macpheek, your issues definitely sound like the one described in the thread @singingcyclist linked to. Your host is setting Wordfence options in a way that makes the scan stop.
Forum: Plugins
In reply to: [Wordfence Security - Firewall, Malware Scan, and Login Security] Scan failedHi @hjorth007!
Sorry for the late reply. I would recommend you enable debug mode in Wordfence. This will make more details show up in the scan log which you may find helpful in figuring out what’s going wrong. You can enable debug mode via the option at the bottom of the Wordfence > Tools > Diagnostics page.The options I’d recommend for scan performance are:
Time limit that a scan can run in seconds: 0 (this will default to three hours)
Maximum execution time for each scan stage: 15
How much memory should Wordfence request when scanning: 256It sounds like it might be that you have a lot of large files on the server. If so, disabling the option “Scan images, binary, and other files as if they were executable” might help as well.
Hi @arswright!
Sorry for the late reply. I’m not sure exactly what happened here but it sounds like there may have been a problem with your database at the time. Possibly, the Wordfence tables weren’t created at all? You could look in the database, check specifically for wfConfig table and make sure it exists and that it’s not marked as crashed in the database. If it doesn’t exist, that’d likely be a problem with your database permissions.Hi @eatonz,
Sorry for the late reply. If everything is working fine, I would assume you actually do have the tables. We recently changed it so that all tables are supposed to have only lowercase letters. It could possibly be something related to that? We haven’t seen other reports of this as far as I know, and it’s not something we’ve seen in testing. If you are on a Windows server, or if you are migrating the site back and forth from Windows, that could possibly be it.Hi @flyinghippo,
Sorry for the late reply. Sending you an update via mail just now.Thanks cucocreative!
Sounds promising. I’ll keep an eye out!Hi again,
I don’t know for sure but I think we’ll likely do a blog post and an email. If you are subscribed to our newsletter, you get an email every time we post so you should then be able to find out that way.Forum: Plugins
In reply to: [Wordfence Security - Firewall, Malware Scan, and Login Security] MySQL57-RHHi again @michelandre,
If Duplicator displays the same information, what is the problem exactly?
Forum: Plugins
In reply to: [Wordfence Security - Firewall, Malware Scan, and Login Security] MySQL57-RHHi @michelandre,
The Wordfence specific diagnostics (Wordfence > Tools > Diagnostics > MySQL > version) displays the version WordPress is using.
The output in “Click here to display your system information” and the script I provided is not “wrong” information. It’s exactly what is in your system php configuration. Please see the PHP docs for reference: http://php.net/manual/en/function.phpinfo.php. Wordfence includes a function for viewing what your actual underlying PHP configuration is. The other plugins don’t. That’s the only difference.
Keep in mind that there are two options that are affected.
“Maximum execution time for each scan stage” should be 15
“Time limit that a scan can run in seconds” should be 0