Scan Failed (tried everything)

  • Resolved ridethetides

    (@ridethetides)


    6 years, 6 months ago

    Please help, this is my error:

    Scan Failed
    The scan has failed to start. This is often because the site either cannot make outbound requests or is blocked from connecting to itself. Click here for steps you can try.

    and: The current scan looks like it has failed. Its last status update was 14 mins ago. You may continue to wait in case it resumes or stop and restart the scan. Some sites may need adjustments to run scans reliably.

    I’ve tried swapping from Limited, to Standard, to High Sens – no difference.

    I’ve tried starting scans remotely
    No under construction plugins
    /wp-admin is not password protected
    The table _wfStatus looks fine in phpMyAdmin
    /wp-admin/admin-ajax.php loads a 0

    Can I get help? I can run another with debug mode and send that diagnostics. Thank you!

    • This topic was modified 6 years, 6 months ago by ridethetides.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support wfphil

    (@wfphil)

    Hi @ridethetides,

    I am sorry to hear you are having trouble with your scans.

    I would like to have a look at your Wordfence diagnostics report. Please go to the top of the “Diagnostics” tab on the Wordfence “Tools” page. There will be a “SEND REPORT BY EMAIL” button to send the diagnostics report. Enter phil [at] wordfence [dot] com as the email and @ridethetides as the forum username please.

    Once you have emailed me the diagnostics report can you reply here to let me know that it has been sent. This is important in the unlikely event that your installation of WordPress is having an issue with sending mail.

    Also, can you do the following so I can get further information I need to help you

    Kill the existing scan if one is still running by pressing the “STOP SCAN” button.

    Click on the “Scan Options and Scheduling” link.

    In the “Performance Options” section set “Maximum execution time for each scan stage” to 20.

    Hit the “SAVE CHANGES” button.

    Go to the bottom of the “Diagnostics” tab on the “Tools” page and expand the “Debugging Options” section.

    Enable the option “Enable debugging mode (increases database load)“.
    Hit the “SAVE CHANGES” button.

    Start a new scan.

    When the scan has definitely failed, click on the “EMAIL ACTIVITY LOG” link to email the scan activity log and send to phil [at] wordfence [dot] com

    • This reply was modified 6 years, 5 months ago by wfphil.
    • This reply was modified 6 years, 5 months ago by wfphil.
    Thread Starter ridethetides

    (@ridethetides)

    Hello @wfphil I have sent the diagnostics email.

    Plugin Support wfphil

    (@wfphil)

    Hi @ridethetides,

    I received the diagnostics report but I haven’t received the scan activity log. Did you send the scan activity log? If not please send using these instructions:

    Kill the existing scan if one is still running by pressing the “STOP SCAN” button.

    Click on the “Scan Options and Scheduling” link.

    In the “Performance Options” section set “Maximum execution time for each scan stage” to 20.

    Hit the “SAVE CHANGES” button.

    Go to the bottom of the “Diagnostics” tab on the “Tools” page and expand the “Debugging Options” section.

    Enable the option “Enable debugging mode (increases database load)“.

    Hit the “SAVE CHANGES” button.

    Start a new scan.

    When the scan has definitely failed, click on the “EMAIL ACTIVITY LOG” link to email the scan activity log and send to phil [at] wordfence [dot] com

    Thread Starter ridethetides

    (@ridethetides)

    Thanks @wfphil I just sent that to you. During that scan I got the following warning:

    [OCT 04 12:17:58] Warning: Creating default object from empty value in /home/(this is my directory)/public_html/wp-content/plugins/js_composer/include/classes/updaters/class-vc-updating-manager.php on line 118

    Notice: Undefined property: stdClass::$sections in /home/(this is my directory)/public_html/wp-content/plugins/js_composer/include/classes/updaters/class-vc-updating-manager.php on line 119 0

    Plugin Support wfphil

    (@wfphil)

    @ridethetides

    Thank you for sending the diganostics report and scan activity.

    The scan completed for the scan log that you sent. If any PHP error logging takes place while a scan is running then that will be shown in the scan log too.

    The PHP warning appears to be for the WPBakery Visual Composer plugin. If you see it on every scan then it is likely it is hooking in to some core function which we use to check for updates.

    Either way, you can let WPBakery know about the warning if you have the latest version of the plugin installed.

    Hi @ridethetides,

    We haven’t heard back from you in a while so I’ve gone ahead and marked this thread as resolved.

    if you’re still having issues with Wordfence, please feel free to open another thread.

    Thanks!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Scan Failed (tried everything)’ is closed to new replies.