WFBrian
Forum Replies Created
-
Hi,
I don’t have an exhaustive list of critical events but they are defined as events that you have to take hands-on action on to resolve. Plug-in updates require you to manually update them so they are deemed critical. Another example would be if Wordfence detected a malicious file on your site. That would require you to investigate the issue and take action.
Hope that helps,
BrianLooks like it could be a database problem. Check you database tables and see if any problems are noted.
If you find errors, I’d recommend trying a clean install. Remove Wordfence and table data and then reinstall.
-Brian
Hi Greg,
Make sure all of your themes and plugins are up-to-date. Also, try changing themes to the default theme and disable plugins one at a time. Does the issue go away? If so, note the plugin or theme causing the issue. Here are some more tips…
https://www.wordfence.com/docs/how-to-clean-a-hacked-wordpress-site-using-wordfence/
If you have questions on the Premium version, please email here:
presales [at] wordfence.com
Thanks!
BrianHi Thom,
Currently, we do not offer that as an option. Others have asked as well. I can pass it along to the development team.
Thanks!
BrianHi,
Will you check the option to enable debugging mode and post the end of the log file where it hangs? That will give me more data to look at.
Thanks!
BrianIt looks like the error is happening when it scans the cacheing directory. Will you try to temporarily disable cacheing and then try another scan?
Thanks!
BrianHi,
Have you had scans complete previously on this site? Is your test install that you performed the workaround on a similar setup as your live site?
Yes, looks like you have plenty of memory. Have you tried adjusting the maximum execution time for scans?
https://support.wordfence.com/support/solutions/articles/1000011129-my-scans-don-t-finish-what-can-i
Thanks!
BrianHi,
Looking at that last post error…Is your host using the latest version of OpenSSL? That would be something to ask them as this error points to a certificate encryption issue. Try disabling SSL and see what happens. Go to Wordfence Options page, and uncheck “Enable SSL Verification” near the bottom of the page. Now try running another test.
Thanks!
BrianAlan,
Yes, here’s what to try in order.
-Make sure your host has enough memory allocated to your site.
-Try disabling live traffic.
-Try the settings described here (you may have seen this already):-Brian
The dash notation is what I posted in the first response. This should be correct for the square bracket notation:
2400:cb00:[0-ffff]:[0-ffff]:[0-ffff]:[0-ffff]:[0-ffff]:[0-ffff]
I don’t think whitelisting the CloudFlare IP’s is necessary.
Cloudflare links to our support doc..
Hi Alan,
Removing the database just removes the Wordfence tables and does not affect WordPress or any other plugins.
The server requirements are located here:
http://docs.wordfence.com/en/Wordfence_system_requirements
Make sure they have enough memory allocated to your site.
Let us know if that helps or not.
-BrianHi,
Sorry to hear you’re having trouble with scans completing. The issue usually boils down to not having enough system resources. Make sure to double-check the system requirements. Are you on a shared hosting platform? You may want to try disabling Live Traffic if you are to save processor cycles.
Actually, removing completely and reinstalling is a good option to try. There may be an issue with your install that is causing the issue as well.
-Brian
Hi,
Try this as the range as it is 2400:cb00::/32 expanded:
2400:cb00:0:0:0:0:0:0 – 2400:cb00:ffff:ffff:ffff:ffff:ffff:ffff
Here is a blog post Mark made about Wordfence and IPv6 support:
I’ve found this too helpful for converting/expanding IPv6 addresses and ranges.
https://www.ultratools.com/ipv6Tools
-Brian
Jenny,
Thanks for the clarification. We currently do not have the ability to display to the user how many times they have incorrectly logged in. The default lockout threshold is 20 incorrect attempts over the time period that is set. The lockout settings are there to keep automated attackers from gaining access. With the standard settings, a human who gets locked out probably does not know their password or is trying to gain authorized access.
Here’s some more info from the documentation on locking users out.
http://docs.wordfence.com/en/Wordfence_options#Lock_out_after_how_many_login_failures
Thanks,
BrianHi,
I’ll pass this along. Thanks for the suggestion!
-Brian