Can’t Run A Scan

  • Resolved NicheLabs

    (@allennichelabs)


    3 years, 2 months ago

    WordPress 5.8
    Wordfence 7.5.4

    When I attempt to run a scan I get the following message:
    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.

    I checked the diagnostics and found this:
    wp_remote_post() test back to this server failed! Response was: 400 Bad Request
    HTTP/1.1 400 Bad Request
    Date: Wed, 28 Jul 2021 14:20:56 GMT
    Server: Apache
    X-Robots-Tag: noindex
    X-Content-Type-Options: nosniff
    X-Frame-Options: SAMEORIGIN
    Referrer-Policy: strict-origin-when-cross-origin
    Expires: Wed, 11 Jan 1984 05:00:00 GMT
    Cache-Control: no-cache, must-revalidate, max-age=0
    Upgrade: h2,h2c
    Connection: Upgrade, close
    Content-Length: 1
    Content-Type: text/html; charset=UTF-8

    0

    I tried deactivating all plugins except Avada Core but I still couldn’t start a scan.
    I tried removing everything but the bare essentials from the .htaccess file

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support wfphil

    (@wfphil)

    3 years, 2 months ago

    Hi @allennichelabs

    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 wftest [at] wordfence [dot] com as the email and allennichelabs 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.

    Thread Starter NicheLabs

    (@allennichelabs)

    3 years, 2 months ago

    Thank you for your quick reply, I’ve sent the email.

    Email Diagnostic Report
    Diagnostic report has been sent successfully.

    Plugin Support wfphil

    (@wfphil)

    3 years, 2 months ago

    Hi @allennichelabs

    Thank you for the report.

    It shows that all of your WordPress and plugin cron jobs haven’t been running since the 23rd of July and are likely due to WordPress being unable to send requests back to itself as outlined by the 400 Bad Request error in the report.

    I see that you are using your own custom theme. Do you recall making any changes on the 23rd of July in terms of your theme, plugins or server configuration?

    Thread Starter NicheLabs

    (@allennichelabs)

    3 years, 2 months ago

    I discovered that Cron was disabled in the wp-config.php file so I just enabled it by changing
    define(‘DISABLE_WP_CRON’, true);
    to
    define(‘DISABLE_WP_CRON’, false);

    The site went live on June 10th. Our server did get hacked around that time as well and we spent a good amount of time cleaning up our server.

    I’ve run a scan on this site with WHM’s Imunify and it came back clean.

    The site is using the Avada theme so we don’t make any changes to the theme files themselves.

    Thread Starter NicheLabs

    (@allennichelabs)

    3 years, 2 months ago

    Any updates on this? I am still unable to start a scan on this site.

    Thread Starter NicheLabs

    (@allennichelabs)

    3 years, 2 months ago

    My apologies. I just learned that this client moved their site to another company and thus another server. I inadvertently still had my host file setup from when I pushed the site live so I could test it before the DNS was updated, so I was still able to see their site on our server.

    This would explain why I can’t get a scan to run. You can mark this as resolved.

    Plugin Support wfphil

    (@wfphil)

    3 years, 2 months ago

    Hi @allennichelabs

    Thank you for the update that you found out the cause and no need to say sorry!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Can’t Run A Scan’ is closed to new replies.