wfmark

Hi @superknjizara, Thank you for reaching out to us.

This error indicates that more memory needs to be allocated to PHP. PHP memory is cumulative meaning that the amount set in php.ini is shared between all plugins, themes, WordPress, and any other non-WordPress apps installed in the site folder. Normally, changing the Memory Limit in the php.ini file to 256M solves this problem but you already have this covered. Please see the recommendations below:

• Upgrade to PHP 7 or above since it introduced better memory handling.
• On your wp-config.php file, look for the wp_memory_limit and update it to 256M define(‘WP_MEMORY_LIMIT’, ‘256M’);
• Adjust the Wordfence performance options to the recommended settings. For a screenshot of my recommended Performance setting options – Click Here.
• Adjust the max_execution_time to 60. Sometimes, having a long execution time may cause the scan to timeout.

If the issue persists, please contact your site administrator or hosting provider and work with them to determine what is causing this issue since memory exhaustion may be occurring outside of PHP somewhere on the server.

Thanks,

Mark

@jeremyvtx,

Yes, you can request for a new  license key.  You can use the same email address to obtain license keys for all your sites. There’s no limit to the number of free sites a single email address can configure.

Thanks,

Mark.

Hi @qwik3r, Thank you for reaching out to us.

Is the user still having trouble logging in?

If you can’t see the IP address of the user under the blocking page, it is possible that the block has already expired. Blocks normally expire after the amount of time set under WordFence> Firewall> Manage Brute Force Protection > Amount of time a user is locked out.

If the user is still locked out, navigate to Wordfence>Tools>Live Traffic and filter out the user’s IP address. If there are any entries that match their IP address, expand the result and share a screenshot of the Live Traffic entry along with a screenshot of the blocking page they see when they log in.

Thanks,

Mark

@djwilko12, thanks for getting back

Wordfence loads a script for logged-in admins that monitors background requests that get blocked by the firewall, to alert you if something was blocked that might not need to be blocked. The option “Monitor Background Requests for False Positives” allows you to disable this script if you like, by unchecking either or both checkboxes. One is for the front-end of your site and the other for the administration section of your site. Disabling the monitoring script does not affect the firewall’s protection, but may make it harder to notice false positives (blocking actions that are not actually malicious).

Thanks,

Mark.

Hey @vidishp, and sorry for the delayed response.

You mentioned earlier that changing the theme to a default one resolved the issue and disabling WooCommerce solved the issue. Which is why I suspected it may be a conflict with your theme as WooCommerce is widely used and we haven’t seen any issues.

If the issue is still persistent, please try disabling all other plugins except for Wordfence, then trying again as it’s likely a plugin conflict issue. If it works as expected, then reenable your plugins one by one until the issue recurs to help find the cause.

Let me know how it goes.

Thanks, 

Mark

Hi @luisdesousa, Thank you for reaching out to us.

The username appears to be suspicious. I suspect a breach may have already taken place prior to the login attempt using an exploitable way in – such as a vulnerable plugin, compromised admin password, etc.
I would recommend that you follow our site cleaning steps below:

https://www.wordfence.com/docs/how-to-clean-a-hacked-wordpress-site-using-wordfence/

Make sure to get all your plugins and themes updated and update the WordPress core, too. As a rule, any time I think someone’s site has been compromised, I also tell them to update their passwords for their hosting control panel, FTP, WordPress admin users, and database. Make sure to do this because attack vectors around your hosting or database environments are outside of Wordfence’s influence as an endpoint firewall.

We recommend using long, unique passwords along with 2FA for your administrative accounts. This might assist if the attackers are using an existing compromised admin account to create this user and elevate the privileges.
You might also find the WordPress Malware Removal section in our Learning Center helpful: https://wordfence.com/learn/

If you’re unable to clean this up on your own, there are paid services that will do it for you. Wordfence offers one, and there are others. Per the forum rules, we’re not allowed to discuss Premium here, but please reach out to us at presales@wordfence.com if you have any questions about it.

Regardless, if you choose to clean it yourself or let someone else do so, we recommend that you make a full backup of the site beforehand.

Thanks,

Mark

Hi @oneoption, Thank you for reaching out.

In most cases, this is caused by permission issues.

Since permissions are set correctly on your site, in your FTP or hosting file manager, navigate to your wp-content/wflogs folder. You should be able to delete the wflogs folder or its contents entirely and Wordfence should try to repopulate it within 30 minutes. This may resolve the issue.

If you have persistent problems with file-writing permissions, you can bypass Wordfence’s requirements entirely by setting logs to use the MySQLi storage engine: https://www.wordfence.com/help/firewall/mysqli-storage-engine/Thanks,

Mark.

Hi @raju427, thanks for your question.

Per forum rules, we are not allowed to discuss the premium version on this forum. You can see our guide below on purchases and email us at presales@wordfence.com for further information on the feature.

https://www.wordfence.com/help/wordfence-premium/

Thanks,

Mark.