Mark Maunder
Forum Replies Created
-
Hi guys,
We fixed an issue that was causing blank usernames to be logged in login failures a while ago. Strange to see it occurring again. I know you’ve confirmed you’re running 5.1.5.
Any chance you can post a screenshot with any sensitive info redacted?
Regards,
Mark.
You can send it to samples@wordfence dot com. We will add detection for this.
Thanks for posting.
Regards,
Mark.
Hi,
This has nothing to do with update interval. Your server is running out of memory and 64 megs is not enough to run a complex WordPress site with Wordfence.
You’re going to have to upgrade it to 128 megs. Then make sure you adjust memory_limit in your PHP.ini file and restart your web server. Then try another scan and you should not run out of memory.
Regards,
Mark.
Hi Yuri,
Yes it definitelly does. Also when you enable Falcon Engine we will detect if you’re running Nginx and give you an Nginx specific configuration.
Regards,
Mark.
I’m not sure I understand the question.
We protect your entire website. Not just your SSL pages.
Regards,
Mark.
Try setting the following option to 10:
Maximum execution time for each scan stage
This is on your Wordfence options page. Then save, then retry a scan. Might help the scan finish.
Also consult with your hosting provider, ask them if there are any errors in our error logs you should be worried about.
Regards,
Mark.
I think that was just a display bug we fixed in Wordfence. Shouldn’t happen again. I would not worry about it.
Regards,
Mark.
Hi,
You can enable an option on performance setup that will put a footer into your HTML source indicating if the page was cached. Enable this, save, clear the cache, then check the home page footer to tell if it’s cached or not.
Regards,
Mark.
Forum: Plugins
In reply to: [WP Activity Log] .htaccess file corruptionHey guys,
We were contacted via our premium support and given a link to this thread. I just did a brief look at WP Security Audit Log’s code and I don’t see anywhere they open/modify the .htaccess (as WPWhiteSecurity mentioned above) so I don’t think it’s them.
I also don’t think it’s us because we use advisory file locking when we edit .htaccess which prevents multiple web server threads from conflicting, or even conflicts with other plugins trying to modify the .htaccess, provided they’re also using file locking (flock()).
So… I think it may be another plugin that is not using file locking. My suggestion is to do a search in the source code of all your plugins for “.htaccess” without quotes and where you find they’re modifying it, check if they’re calling the flock() function before hand to avoid conflicts. If not, you found the culprit.
Regards,
Mark.
PS: WPWhiteSecurity sorry to jump your forums, but I hope that helped a little.Forum: Reviews
In reply to: [Wordfence Security - Firewall, Malware Scan, and Login Security] SuspiciousPlease click the usernames in the reviews to verify who they are before making baseless accusations.
The ‘ads’ you receive are actually alert emails that you chose to receive from your website. They contain a small footer reminding you that you’re using the free version of our plugin.
Any suspicious login attempt we show you includes the IP address. You can use the WHOIS facility we include to find out exactly which network that IP address is on and contact the ‘abuse’ email for that network to report the attacker. It would be both stupid and criminal (according to the CFAA act) for us to send fake hack attempts.
Kind regards,
Mark.
Hi,
Sounds like you may have a problem with your web server. Check to make sure you haven’t run out of disk space or inodes. You might want to log a support call with your hosting provider.
Regards,
Mark.
Hi,
Thanks for the great feature suggestion.
Yes you need to enter a relative URL e.g. /my-bad-url/mypage.html
We’ll add this to the documentation.
Regards,
Mark.
OK thanks.
Here’s what we’re going to do about this: We’re going to add monitoring that tests that API call to see if it is intermittently failing. If we find it’s failing we’ll fix it.
Regards,
Mark.
OK thanks very much, we’ll get this resolved.
Regards,
Mark.