Scanning Stops

Hello Mighty Good,
you will be notified via your WordPress and Wordfence installation when the next release is out. Upgrade, and if the problem persists after that, get back to us.

You will be seeing more hits in Live traffic with the latest releases of Wordfence because the Live traffic shows more than it used to. It is more complete now.

Thanks wfasa,

Without getting too far off from the subject matter of this string, is it important to block ip addresses that look to be suspicious? With more of them in Live Traffic, it will obviously increase the amount of time needed to do this. Is there a URL you could post that would have direction on what should, or should not be, manually blocked?

Looking forward to the next release!

Cheers!

Same problem with me. Scan ran completely when I disabled ( unchecked) “Scan for signatures of known malicious files”

@kuleanadesign, @c7consulting I had same results. Scan ran successfully after unchecking “Scan for signatures of known malicious files”

Hello Mighty Good,
it’s difficult to make general rules about what exactly should be blocked because every site has it’s own target audience. Any specific block rule must be weighed against the risk of blocking legit traffic.

I would suggest you look for patterns in the unwanted traffic you are having on your site and add rules based on that in your Wordfence settings. For example, check “Pages not found” in the Live Traffic view. Are there some strange requests for pages that do not exist and that you know should never be directly requested there? If so, you can add the last part of the URLs in Options/Other options/Immediately block IP’s that access these URLs.

What invalid usernames are people using to try to bruteforce in to your site? You can find that information under Live Traffics “Logins and logouts”. Add those usernames to Options/Login Security Options/Immediately block the IP of users who try to sign in as these usernames. You can also select to “Immediately lock out invalid usernames” though that might cause unwanted blocks by people who type in the wrong username by accident.

You can also tweak your rate limiting rules to block more traffic. You can find information about recommended settings here.

Thanks wfasa!

Many of the bogus requests have come from URLs ending in /wp-admin — so I can’t block those, or I would also end up blocking myself, correct? Any options with this?

Any update on when the new Wordfence plugin update/release is coming?

Cheers!

Thanks wfasa, I’ve just updated to 6.1.4 and this has fixed the problem. Also a ton of other great updates and fixes!

Just got the update as well! All is better! Yipppee Do Da!!!!

Yes, it works fine now.

Super stuff, all ok now – back to business as usual!

Thanks to all who have confirmed that the bug “stored data not found after a fork: got boolean” has been fixed for you. If anyone did not get this fixed by installing the latest version, please make a new support request and describe your situation.

Mighty Good, yes there is a risk you could block yourself if you put in any real URLs in there. So you don’t want to do that. I haven’t seen a lot of requests that end with /wp-admin. I would need a bit more information on that so if you want me to look at it email a list of those hits to [email protected].