Scan Stage Failed

  • Resolved cschultzie3

    (@cschultzie3)


    5 months, 2 weeks ago

    I’m getting Scan Stage Failed for the File Changes portion of a scan, and am stuck troubleshooting why. Tried following this article the best I could https://www.wordfence.com/help/scan/troubleshooting/#if-your-scans-arent-starting.

    On the diagnostics page, it says “wp_remote_post() test back to this server failed! Response was: 503 Service Unavailable”. In the database sections, there’s no errors so hoping that’s a good sign.

    “Start all scans remotely” didn’t help. I don’t have any under construction type plugins. I exported all the blocked IPs from WordFence (I think at least, used the button to export them) and the ones from that article aren’t in there. I’ve never done a country block on the US so they shouldn’t be blocked from that as I think they’re all US IPs but I could be wrong.

    GoDaddy confirmed that list of IPs was not blocked, and tried disabling CDN to no avail so that was enabled again. They even tried putting a default .htaccess in temporarily while CDN was disabled and the scan still fails so they put the real one back.

    I confirmed my /wp-admin/admin-ajax.php shows the zero per that article as well.

    I tried enabling the verbose logging, the option next to the “start all scans remotely”, thinking maybe that would say if it was an IP it couldn’t reach and which one, but I didn’t see that info when I viewed the log.

    Anywhere else I should look or anything else I should try? Thanks in advance for any help!

Viewing 1 replies (of 1 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @cschultzie3, thanks for the information above.

    When looking at the scan stages on the Wordfence > Scan page, does File Changes show as a yellow exclamation triangle instead of a green checkmark? Ensure the settings mentioned for that section are enabled in Wordfence > All Options > Scan Options > General Options: https://www.wordfence.com/help/scan/#scan-stages

    You could also ensure max_execution_time = 60 in php.ini, Wordfence’s scan only ever attempts to use half of this value by default but we have noticed issues with values higher than 60 (or when its set to 0, which is effectively no limit).

    Your WP_MEMORY_LIMIT could be set to 256M in wp-config.php. WooCommerce, for example, recommend trying 256M in some scenarios, so if you also have many hits on the site at once especially during a scan, a lower limit here could be reached fairly easily. Your PHP memory_limit value could also be adjusted to256M to accommodate this change.

    Failing the above, can you please try the following to get me some more information about the scan itself?:

    • Stop the existing scan if it is still running (The “Start New Scan” button turns into a “Stop” button while the scan is running).
    • Go to Wordfence > Scan > Manage Scan and locate the “Performance Options” section. Set “Maximum execution time for each scan stage” to 20.
    • Click to “Save Changes”.
    • Go to the Tools > Diagnostics page.
    • In the “Debugging Options” section check the circle “Enable debugging mode”.
    • If “Start scan remotely” is checked, uncheck this option.
    • 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.

    On some sites, this will correct the issue. 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. If this fixes the issue and scans run again, you can leave all the settings above except for “Enable Debugging Mode”.

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

    Thanks,
    Peter.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.

Tags