wfmark

Hi @nmwoods123 , thanks for reaching out. We are sorry to hear you’re having problems with site speed.

Some Wordfence customers can experience problems at times when intensive processes such as scans are running. Hosting plans, the size of the website content, and the number of installed plugins tend to be the deciding factors in this, but a majority of the sites running Wordfence work without issues. 

We constantly work on making the plugin faster, perform better, and use less resources but there are no set amounts of RAM, CPU or database queries that we know Wordfence will definitely require in each use-case.

Could you please send us a diagnostic report to wftest@ wordfence.com?  You can find the link to do so at the top of the Wordfence > Tools > Diagnostics page. There, click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

Thanks,

Mark.

Hi @chiaraampartners ,thanks for reaching out.

These URLs normally show up in Google search/Search Console due to an automatic redirect to a search/home page when a 404 is hit on your site. This can be due to a misconfigured theme, or a redirect plugin purposely changing 404 behavior. When one of the wordfence_lh URLs is followed, the page should be totally blank in the browser.

The ones you are seeing are likely from Google remembering old URLs and trying them again to update their index. With time Google should recognize that those paths are not useful to crawl.

We used to recommend adding wordfence_lh and hid to the list of parameters that Google can ignore, but it looks like that feature has been removed from Google Search Console: https://searchengineland.com/google-search-consoles-url-parameter-tool-is-officially-not-working-383828

Thanks,
Mark.

Hi @sushilsth , thanks for reaching out.

Sometimes other plugins can cause issues with the Wordfence 2FA functionality. If the Sucuri firewall is the only differentiating factor from the other sites, you can try disabling it temporarily to see whether that solves the issue.

Please note that if you use a custom login page, it can also cause 2FA to not work right since our 2FA feature is only supported for the default WordPress login page and the custom login page for WooCommerce.

If none of the above works for you, please send a diagnostic report to wftest @ wordfence.com? You can find the link to do so at the top of the Wordfence Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

Thanks,

Mark.

Hi @muadmz , thanks for reaching out.

Could you please do the following steps for me:

• Go to the Wordfence > Tools > Diagnostics page
• In the “Debugging Options” section check the circle “Enable debugging mode”
• Click to “Save Changes”.
• CANCEL any current scan and start a NEW scan
• Copy the last 20 lines from the Log (click the “Show Log” link) or so of the activity log once the scan finishes and paste them in this post.

Wordfence > Tools > Diagnostic > Debugging Screenshot

This will help me see exactly what is happening when the scan fails.

Additionally, can you send a diagnostic report to wftest @ wordfence . com? You can find the link to do so at the top of the Wordfence > Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

NOTE: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email

Thanks,
Mark.

Hi @birken , thank you for reaching out to us.

The FormCraft 3 plugin seems to be overriding the WordPress upgrade hook and isn’t returning the expected format in this case. This will likely be addressed by Wordfence version 7.10.4 so that issues with other plugins don’t result in a fatal error during the scan.

Thanks,

Mark.

Hi @lia987 , thanks for reaching out.

You keep getting these notifications because you have enabled the option to receive an alert when a user is locked out from logging in. If you don’t wish to receive these alerts anymore, you can disable the “Alert when someone is locked out from login” option from Wordfence>All Options>Email Alert preferences. 

Depending on the site you’re running and the number of users on the site, you may need to review the lockouts in case another administrator is locked out. If you’re running a site with many users, it may be best to disable this option to avoid receiving many alerts.

For more information on email alert configuration options, check out the resources below https://youtu.be/d50knnGXNO4
https://www.wordfence.com/help/dashboard/alerts/

Let me know in case you have any questions.

Thanks,

Mark.

• This reply was modified 1 year, 6 months ago by wfmark.