Scan process ended after forking.

Hi @nickabela,

Can you send a diagnostic report to wftest @ wordfence . com? You can find the link at the top of the Wordfence > Tools > Diagnostics page. Then select “Send Report by Email.”

Please add your forum username and respond here after you have sent it.

Hi @wftiffany,

I just sent the report.

Thanks @nickabela. A few updates can be made:

• Access to the wp-admin directory is blocked via a plugin that changes the login page. We actually don’t recommend hiding the login URL for reasons explained here: https://www.wordfence.com/blog/2017/10/should-you-hide-wordpress-login-page/ That being said, blocking access to /wp-admin/ is also blocking the WordPress AJAX handler, which is needed for scans to run. You can try deactivating this plugin to check if scans can run when it’s not in use.
• You can increase your wp_memory_limit value in the wp-config.php file to 256M. Currently, it’s only 40M.
• Lastly, you can set max_execution_time = 60 in your php.ini file. Wordfence’s scan only attempts to use half of this value by default. Larger values such as the 3600 you currently have set have been known to slow/kill scans in other sites.

Let me know if you continue to have issues.

@wftiffany thank you, it was hiding the login URL that was causing the issue. It was just weird because it’s been hidden for a while, but this just started happening today.

Thank you!