wfmark

Hi @hebhansen,

I couldn’t find your diagnostic report. Please try the below instead:

Navigate to Wordfence > Tools > Diagnostic page and then click the “Export” button. Send the txt file to [email protected]. Add your forum username in the subject and respond here once done. Let me know once you have sent the report.

Thanks,

Mark.

Hi @lcolvin, Thank you for reaching out.

The only other workaround is if you have added your site to Wordfence Central. You can add your public-facing IP address to the Allowlisted IP addresses that bypass 2FA under the the Login Security options.

You can also have another admin user disable 2FA on your account for you.

If none of the above options work,  you will need to use FTP/SFTP — or any file manager your web host provides via their administration panel to disable Wordfence manually.Let me know if you need any further assistance.

Thanks,

Mark.

Hi @rezaulkarim01, Thank you for reaching out.

What can we do for you please? Your question wasn’t quite clear. If possible, could also share a screenshot of the problem you are facing please.

Thanks,

Mark.

Hi @jamieburchell, Thank you for reaching out.

Sometimes it’s been known for a scan to start running around the same time as automatic/manual plugin updates are performed, so picks up the outdated plugins at the start but won’t realize plugins have been updated by the time it ends.

On the free version of Wordfence, a quick scan runs every day, and a full scan runs every 72 hours. The quick scan does check for WPScan vulnerabilities and repository versions, but an updated repository status against your installed plugin list will not refresh until the next full scan is run manually or automatically. This may mean the notice of a modified plugin persists between scans.

Thanks,

Mark.

Hi @wiezo, Thank you for reaching out.

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 are able to save changes on SmartCrawl. Once done, switch the WAF from Learning Mode back to Enabled and Protecting and test to see whether it works as expected.

https://www.wordfence.com/help/firewall/learning-mode/ is an amazing resource for learning more about the WAF and learning mode.

Thanks,

Mark.

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

Please try to clear cache (site plugins and local browser). You can also try to log in from a different internet browser where all browser extensions have been disabled. If you don’t have the same issue in the other internet browser where all browser extensions have been disabled then that indicates a browser extension in your normal browser is breaking our JavaScript.

If you still have the same issue in the other internet browser then your theme or another plugin may be loading JavaScript on our admin pages and creating a conflict.Disable all other plugins except Wordfence , then try 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 the issue persists,  access wp-admin while keeping a Browser Console open to see if you can detect any JavaScript errors or files that fail to load. If you see any red errors in the console, please take a screenshot and send it to me.

Let me know what you find.

Thanks,

Mark.

Hi @mdtarik, thank you for reaching out.

Do you have 2FA and/or reCAPTCHA enabled in Wordfence? It seems like the message you’re seeing is down to a problem when logging in.

Have you also hidden your WordPress login pages with a plugin? Some plugins and operations require the default WordPress paths so it could be worth disabling any plugins that modify this location and see if the authentication issue gets solved. Currently, Wordfence’s 2FA and reCAPTCHA only works with default login/registration pages for WordPress and WooCommerce so custom paths and pages will likely encounter problems such as this.

Thanks,

Mark.

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

As Wordfence has already been deleted, please try to clear cache (site plugins and local browser) and disable all other plugins except Elementor , then try 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 re-enable your plugins and theme one by one until the issue recurs to help find the cause.

Let me know how it goes.

Thanks,

Mark.

Hi @justin77,?thank you for reaching out.

Usually with regards to site speed, some Wordfence customers can experience problems at times when intensive processes such as scans are running although shared hosting plans, size of website content, and number of installed plugins tend to be the deciding factors in this as the majority of our ~5m site installations work without issue.

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

For a screenshot of my recommended Performance setting options – Click Here.

Aside from this, I notice your max_execution_time value is 300, which has been found to be detrimental to scan speed. We have seen issues arise when this number is above 60, so I would suggest altering this before going further.

Your WP_MEMORY_LIMIT is 40M and could be set to 128M or 256M in wp-config.php. WooCommerce, for example, recommends 64M minimum, so if you also have many hits on the site at once especially during a Wordfence scan, a lower limit here could be reached fairly easily. Your PHP memory_limit value could also be adjusted to 128M or 256M to accommodate this change.

I hope this helps you out!

Thanks,

Mark.

Hi @hebhansen,

Please send a diagnostic report to [email protected]. 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 @russellcardiff, Thank you for sending the diagnostic report.

Please use FTP or your hosting file manager to delete the wflogs directory located in the following path:

~/wp-content/wflogs

Loading any page on your site will create a new wflogs directory and all files needed inside.

Once done, please try switching to Enabled mode and let me know whether that makes a difference.

Thanks,

Mark

Hi @wattsyourwebsite, Thank you for getting back to us.

• 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 on the Scan page.

If the scan fails again, copy the last 20 lines or so from the Log (click the “Show Log” link) once the scan finishes and paste them in the post.

Additionally, please send a diagnostic report to [email protected]. 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 @wpmakenorg, Thank you for getting back to us.

Could you please try clicking the specific buttons to review and accept the Agreements?

Wordfence dashboard notifications can also be disabled under Wordfence> All Options> General Wordfence Options> Dashboard Notifications.

Let me know how it goes.

Thanks,

Mark.

Hi @michael2010, Thank you for sending the diagnostic report and apologies for the delayed response.

Everything looks good on the report.

Please try all of our troubleshooting tips centered around this type of error message.

https://www.wordfence.com/help/scan/troubleshooting/#scan-process-ended-after-forking?

From the error log,  I noticed you have high value set for the max_execution_time . Sometimes, a higher max_execution_time value has been found to be detrimental to scan speed. We have seen issues arise when this number exceeds 60, although Wordfence will only attempt to use half of this value by default. don’t have some performance options set. 

Go to your Wordfence > Scan > Manage Scan and locate the “Performance Options” section. Set “Maximum execution time for each scan stage” to 20. For a screenshot of my recommended Performance setting options – Click Here.

Adding “20” for the “Maximum execution time for each scan stage” tells the scan to pause every 20 seconds and start again where it left off, which makes the scan more performance-friendly for some servers. Once done, go to Wordfence > Scan > Scan Options and Scheduling and check to see if the bottom two options in General Options are disabled. It would be best to have those disabled for now (Scan files outside your WordPress installation, Scan images, binary, and other files as if they were executable)

Additionally, confirm that the Scan Option is set to Standard. Be sure to save your changes in case you make any changes here.

Please try running scan with the updated settings and let me know whether you have any issues.

Thanks,

Mark.

• This reply was modified 11 months, 2 weeks ago by wfmark.

Hi @spierbouwers, Thank you for sending the diagnostic report.

From the diagnostic, I can see the Scan Results under the Scan Issues section.

It is possible that this could be due to a browser extension breaking our JavaScript.  Try from a different internet browser where all browser extensions have been disabled – don’t use a private or incognito session.

If you don’t have the same issue in the other internet browser where all browser extensions have been disabled then see if you have the issue still in your normal browser.  If you do then that indicates a browser extension in your normal browser is breaking our JavaScript.

If you still have the same issue in the other internet browser then your theme or another plugin may be loading JavaScript on our admin pages and creating a conflict.

Let me know what you find.

Thanks,

Mark.