• Resolved rokkashthomas

    (@rokkashthomas)


    I work for an agency and almost all of our sites are using the free version of WordFence. Lately scans have been stopping on a number of our sites despite using settings like ‘start scan remotely’ and ‘low resource scanning’. I noticed that a majority of them are showing ‘wp_remote_post() test back to this server failed! Response was: 200 OK’ in the diagnostics tab.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @rokkashthomas, thanks for highlighting your issue to us.

    Can you do the following so I can get the information I need to help you?

    • Kill the existing scan if it is still running (The “Start New Scan” button turns in to a “Stop” button while the scan is running)
    • 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”
    • 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 Log (click the “Show Log” link) or so of the activity log and paste them in the post.

    On occasion, this fixes it straight away. That’s because 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. If this fixes the issue and scans run again, you can leave all the settings above except for “Enable Debugging Mode”.

    If you’re still experiencing problems after the above, it would be great to grab a copy of your diagnostic report so we can look further into the issue for you. Please navigate to Wordfence > Tools > Diagnostics. Here you can select SEND REPORT BY EMAIL. Please include your forum username (@rokkashthomas) and reply to this message to confirm that you’ve sent it.

    Thanks,

    Peter.

    Thread Starter rokkashthomas

    (@rokkashthomas)

    Hi Peter,

    Setting the max execution time to 20 seems to have fixed the issue. Thanks for your help!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Scans stopping’ is closed to new replies.