wfmark
Forum Replies Created
-
Hi @astima, Thank you for reaching out to us.
Most web host accounts have set limits on resources. If this limit is breached, a “508 Resource Limit Is Reached” error is triggered, and your site will be temporarily inaccessible.
256MB is generally what we recommend using, though it is not completely uncommon to need to use 512MB or more for sites running a larger number of plugins. One thing to keep in mind is it is not likely that Wordfence is using all the memory, but rather all the plugins active at any given time, or potentially one or two problematic or conflicting plugins.
One thing to do is to go through all your plugins and make sure you are actually using all of them. Every plugin you have activated uses a part of your available memory, so the more plugins you have active, the more memory your site needs.
Whilst we are constantly working on making the plugin faster, perform better, and use less resources, there are not set amounts of RAM, CPU or database queries that we know Wordfence will definitely require in each use-case or hosting environment. This is also not a widespread problem across our sizeable customer base but does crop up from time to time with certain configurations.
Before making an assessment from my side about what the cause might be, it’d be great if I could grab a copy of your site diagnostics which you can send 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: For the fastest response time, please make sure and add any information or questions directly to this topic and not the email address above unless asked.
Thanks,
Mark.
Hi @loano1, thanks for making us aware.
Even though Wordfence is tested with PHP 8+ and release candidates, there may be some deprecation notices such as these currently, which flag features of PHP that will change in a later release but still work as intended.
These notices will be fixed in upcoming releases to ensure compatibility with future PHP versions, often as WordPress moves towards officially supporting them too. At the moment PHP 8.3 has “beta support” for WordPress 6.4, but this is a good chart to keep an eye on: https://make.wordpress.org/core/handbook/references/php-compatibility-and-wordpress-versions/
I’ll pass the messages you’ve provided on to ensure we’re looking in that area.
Thanks,
Mark.
Hi @ojkprabhu, thanks for your contacting us!
In some instances with load balanced databases and web sites, the scan will stop with this exact error. In Wordfence > Scan > Scan Options > General Options, this has been known to be fixed by disabling the “Scan file contents for malicious URLs” option.
If that doesn’t work, check your maximum execution time:
- Cancel any existing scans.
- Go to your Scan > Scan Options and Scheduling page and locate the “Performance Options”
- Set “Maximum execution time for each scan stage” to 20 on the options page
- Click to “Save Changes”
- Try another scan.
If you continue to experience problems, you can also take the following steps so that I can grab some information to help you:
- Go to the Tools > Diagnostics page
- In the “Debugging Options” section check the circle “Enable debugging mode”
- Click to “Save Changes”.
- Start a new scan.
- Copy the last 20 lines from the activity log (click the “Show Log” link) once the scan finishes and paste them here.
There could also be issues around caching, allowlisting of IPs, or a problem with the database itself (depending on your platform) so it might still be necessary to troubleshoot further, but seeing what exactly the scan was trying when it failed would be useful.
Thanks,
Mark.
Hi @sscoder, Thank you for reaching out to us.
I’d suggest clearing cache (site plugins and local browser) and disabling all other plugins except for Wordfence, then trying again to see if there’s a plugin or theme conflict causing the issue. You could also revert to a default theme, such as Twenty Twenty-Three.
If it works as expected, then reenable your plugins and theme one by one until the issue recurs to help find the cause.
If there’s a plugin or theme conflict, I would suggest changing the Wordfence Web Application Firewall into Learning Mode. From the Wordfence Dashboard, click on Manage WAF. Then you will see Basic Firewall Options > Web Application Firewall Status. Change the option to Learning Mode. Now confirm that you can view settings page. Once done, switch the WAF from Learning Mode back to Enabled and Protecting and test to see that you can still view the settings page.
https://www.wordfence.com/help/firewall/learning-mode/ is an amazing resource for learning more about the WAF and learning mode.
Let me know how it goes.
Thanks,
Mark.
Hi @richj615, Thank you for reaching out to us.
Please share more details about the issue you need assistance with and we will be happy to assist you.
Thanks,
Mark.
@said303, Thank you for the update.
I am glad that we were able to figure out where the problem was.Thanks,
Mark.
Hi @zimanranaitsirc, Thank you for reaching out to us.
We are not allowed to discuss the premium version on this forum. Please reach out to presales@wordfence.com with a description of your issue.
We will be happy to assist you.
Thanks,
Mark.
Hi @scipadilla, Thank you for reaching out.
Could you please try to deactivate and reactivate Wordfence from the plugins area of your site? This solves the issue for some customers.
We have seen possible issues installing keys automatically more than 24 hours after generation. Additionally, if you are in a different browser than the one used when requesting your Free Wordfence license, you will be unable to automatically install it. In those cases, you will need to manually copy and paste the key from the email to complete the activation of Wordfence Security.
Aside from verifying that you did not copy only part of the license key, I would check whether you can install the license when Wordfence is the only active plugin on your site. There could be a Javascript conflict with another plugin potentially stopping the code executing the verification check.
In some cases, disabling caching plugins resolves the issue.
Let me know how it goes.
Thanks,
Hi @dimalifragis,
We did not receive the screenshot requested. Are you experiencing any problems while forwarding it?
Let us know if you are still experiencing the same 404 errors.
Thanks,
Mark.Hi @quintor
We did not receive your email. Are you having any problems forwarding the email?
We would like to know the kind of email that you are receiving from Wordfence to see why there is no hint to unsubscribe.
Thanks,
Mark.
Hi @juridiscord, thank you for reaching out.
Are you able to access the Live Traffic page?
If you could open the Live Traffic Page by navigating to Wordfence> Tools> Live Traffic and try to open the pages that return 404 errors. If there are any entries on the Live Traffic page, expand the result and share a screenshot of the Live Traffic entry with me so I can take a look.
Additionally, could 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 @hellosite, Thank you for reaching out.
Wordfence works well with most of the WordPress plugins. Some features/functionality may be the same as other security plugins features. So you would choose which plugin you want to handle that functionality and turn off the feature in the other plugin to avoid conflicts or a strain your site resources.
Thanks,
Mark.
Hi @morgegames, Thank you for reaching out to us.
The cURL error 28 is a common error and usually temporary. Kindly reach out again to your hosting provider so that they can take a look at the issue with the cURL library on your hosting server. Confirm that they haven’t blocked Wordfence’s scanning server’s IP address range from accessing your site. Our servers’ IP addresses are listed here https://www.wordfence.com/help/advanced/#servers-and-ip-addresses
If the issue persists, 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.
Looking forward to hearing from you.
Thanks,
Mark
Hi @miminou, thanks for reaching out.
Are you seeing the exact same result when logging in using a private/incognito window, and even a browser different to your default choice? If it does, do you have any caching plugins or caching on your hosting server that could be cleared to see if that improves the situation?
If the issue still persists, are you seeing 404 errors in your browser console for scripts related to Wordfence?
Thanks,
Mark.Hi @emran4005,
As per the forum guidelines below, please open your own topic (if the above reply does not work for you), and we would be glad to assist you:
“Unless users have the exact same version of WordPress on the same physical server hosted by the same hosts with the same plugins, theme, and configurations, then the odds are the solution for one user will not be the same for another. For this reason, we recommend people start their own topics.”
Thanks,
Mark.