Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter purvabathe

    (@purvabathe)

    Hello @wfpeter,
    I have been awaiting a response from the plugin side, tried all the troubleshooting steps listed in the other tickets, but the Start New Scan button is still not clickable, also not able launch scan from central account and the root?cause of the issue has not yet been identified.

    The installed version of WordPress is 5.5.8, but as the plugin supports all versions 3.9 or higher, that is not the problem in this case.

    Actions taken so far in this:

    Would you please look into it? Please let me know what I need to do to start this scan process.

    Thanks in Advanced!

    Plugin Support wfpeter

    (@wfpeter)

    Hi @purvabathe, sorry for the delay and I appreciate the extra information.

    I think as you’ve tried some of the scan troubleshooting options for the errors we’re seeing already, it might be a good idea to drop us a diagnostic report. This way, we can look into your domain and the related Wordfence Central settings at the same time.

    If you can send one to wftest @ wordfence . com using the link 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,
    Peter.

    Thread Starter purvabathe

    (@purvabathe)

    Hi @wfpeter,

    Tried sending report from Wordfence > Tools > Diagnostics but getting error while sending report, I just emailed it from outlook, Please let me know if you received the report.

    Thanks you.

    Thread Starter purvabathe

    (@purvabathe)

    Hi @wfpeter,

    The issue reported in this ticket, https://www.ads-software.com/support/topic/cant-start-scan-using-cloudflare/ is one that I am also experiencing.

    I debugged more, into it and when I tried to turn off the DNS proxy, scan got worked! But since disabling the proxy is not recommended, we must come up with another alternative solution.

    Thank you and looking forward to your response!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Scan process ended after forking’ is closed to new replies.