I checked those and don’t think those are any of the reasons.
Actually on debug mode this is what I see
[Apr 13 02:45:08] Starting cron via proxy at URL https://noc1.wordfence.com/scanp/pwningroot.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&cronKey=4628009f44ede9ae5da9f899
[Apr 13 02:45:09] Scan process ended after forking.
Another known issue is if you have object cache enabled. If this is the case, then you should empty the cache and then try a new scan.
Otherwise, I would disable each extra plugin at a time to check if there is a conflict that prevents the scan from starting.
Maybe AJAX handler (admin-ajax.php) is being blocked somehow.
Tools / Diagnostics also could provide some useful info. Try check the log files there.
Hi @tacorocket,
Please go to (Wordfence > Tools > Diagnostics) and scroll down the page till “Send Report by Email” and send the report to “alaa [at] wordfence [dot] com”, make sure to include your forum username, I will take a look at this report and let you know my findings.
Thanks.
I got it to work. I had to change a config because while it was not blocked by WordPress there was a 401 error caused by the web server. Removed that roadblock and the scan ran wonderfully. Thank you for your time!
I’m glad you managed to get the scan working fine now, thanks for the update!
