wfmark

Hi @miminou, thank you for getting back to us.

Could you run Wordfence as your only-enabled plugin and revert to a default theme such as TwentyTwenty-Three to see if there’s a plugin or theme conflict causing the issue. If it works as expected, then reenable your plugins and theme one by one until the issue recurs to help find the cause.

Additionally, can you log in while keeping a Browser Console open to see if you can detect any JavaScript errors or files that fail to load. If you see any red errors in the console, please take a screenshot and send it to me.

Thanks,

Mark

Hi @drgonzo3000, Apologies for the delayed response.

For the Browser user-agent to ignore option on Live Traffic, this is a single user-agent. Wildcards and multiple entries are not handled. 

For List of comma separated IP addresses to ignore, it does seem to work expected from your explanation,but please note that this option only applies to the general Live Traffic records, like showing pageviews. Security-related events such as logins are still included.

For the allowlist services, it looks like StatusCake added a new IP address that isn’t currently on our allowlist — I’ve passed this on to the Development Team and they are working on updating the list. Ideally, services like this should use a DNS PTR record to identify their own servers, rather than using the default AWS domains, but there are several services that don’t do that, unfortunately. For that reason, we don’t recommend blocking all AWS traffic.

Thanks,

Mark.

Hi @adamhideseek, thank you for reaching out.

If you are having technical problems and you cannot set the “Web Application Firewall Status” to “Disabled”, you can instead set a constant. If you have the “Protection Level” set to “Basic WordPress Protection”, you can add this code to your WordPress “wp-config.php” file, just below the line about “WP_DEBUG”. If you have the “Protection Level” set to “Extended Protection”, the code should be added to the “wordfence-waf.php” file, before the line that begins with “if”:

define('WFWAF_ENABLED', false);

Thanks,

Mark.

Hi @solventweb, Thank you for getting back.

That’s right. As all the timestamps are current, there’s no cause for concern.

If any rule updates fail, you will see an error message on the Wordfence Dashboard. 

Thanks,

Mark.

Hi @dimalifragis, Thank you for sending the screenshots and apologies for the delayed response.

I have confirmed that this is a racing issue. It happens if the hits are coming in fast and in parallel, and the server is fast enough to process them in parallel.

It looks like  some of the hits were happening so close together that when Wordfence checks the rate limit, just before the limit is hit, a few of the hits see that the rate limit has not been hit yet — but each of them count as the first hit that should be blocked, so they add a block record.

This is unavoidable without adding a locking mechanism, which would slow down the site in order to avoid timing issues from overlapping hits, so this is expected behavior. Since these blocks are not permanent, they will all be removed when they expire.

Thanks,

Mark.

Hi @alaminmollik,

Thank you for reaching out.

We have seen possible issues installing keys automatically more than 24 hours after generation. Additionally, if you are in a different browser than the one used when requesting your Free Wordfence license, you will be unable to automatically install it. In those cases, you will need to manually copy and paste the key from the email to complete the activation of Wordfence Security.

Aside from verifying that you did not copy only part of the license key, I would check whether you can install the license when Wordfence is the only active plugin on your site. There could be a Javascript conflict with another plugin potentially stopping the code executing the verification check.

In some cases, disabling caching plugins resolves the issue.

Let me know how it goes.

Thanks,

Mark

Hi @ojkprabhu, thanks for your contacting us!

In some instances with load balanced databases and web sites, the scan will stop with this exact error. In Wordfence > Scan > Scan Options > General Options, this has been known to be fixed by disabling the “Scan file contents for malicious URLs” option.

If that doesn’t work, check your maximum execution time:

• Cancel any existing scans.
• Go to your Scan > Scan Options and Scheduling page and locate the “Performance Options”
• Set “Maximum execution time for each scan stage” to 20 on the options page
• Click to “Save Changes”
• Try another scan.

If you continue to experience problems, you can also take the following steps so that I can grab some information to help you:

• Go to the Tools > Diagnostics page
• In the “Debugging Options” section check the circle “Enable debugging mode”
• Click to “Save Changes”.
• Start a new scan.
• Copy the last 20 lines from the activity log (click the “Show Log” link) once the scan finishes and paste them here.

There could also be issues around caching, allowlisting of IPs, or a problem with the database itself (depending on your platform) so it might still be necessary to troubleshoot further, but seeing what exactly the scan was trying when it failed would be useful.

Thanks,

Mark.