Wordfence scanning failed

  • Resolved deshdeepak01

    (@deshdeepak01)


    4 years, 5 months ago

    Whenever I tried scanning my site, it get terminated with an error message i.e. “The scan has failed because we were unable to contact the Wordfence servers. Some sites may need adjustments to run scans reliably. Click here for steps you can try.”

    in addition, I’ve sent a diagnostic report to ‘[email protected]’.

    The page I need help with: [log in to see the link]

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

    (@wfphil)

    4 years, 5 months ago

    Hi @deshdeepak01

    We have a scan troubleshooting guide below:

    https://www.wordfence.com/help/scan/troubleshooting/

    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 deshdeepak01 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 deshdeepak01

    (@deshdeepak01)

    4 years, 5 months ago

    I’ve sent a diagnostic report to ‘[email protected]’ .

    Plugin Support wfphil

    (@wfphil)

    4 years, 5 months ago

    Hi @deshdeepak01

    The report is reporting a successful connection to our servers so it may just be related to the scanner.

    Can you ask your hosting provider if they are blocking outgoing connections to any of our IP addresses below:

    44.239.130.172
    44.238.191.15
    35.155.126.231
    54.68.32.247
    44.235.211.232
    54.71.203.174

    Thread Starter deshdeepak01

    (@deshdeepak01)

    4 years, 5 months ago

    My hosting provider told me that they are not blocking outgoing connections to any of your IP addresses.

    Plugin Support wfphil

    (@wfphil)

    4 years, 5 months ago

    Hi @deshdeepak01

    Thank you for the update.

    Can you downgrade to PHP 7.4 and let me know if that helps.

    Wordfence is compatible with PHP 8 but your theme or other plugins you use may not be compatible yet and causing a conflict.

    Thread Starter deshdeepak01

    (@deshdeepak01)

    4 years, 5 months ago

    how can I downgrade to PHP 7.4? please tell the procedure.

    Thread Starter deshdeepak01

    (@deshdeepak01)

    4 years, 5 months ago

    Even after downgrading PHP 7.4, the scan is getting fail. Now tell me what can I do?

    Plugin Support wfphil

    (@wfphil)

    4 years, 4 months ago

    Hi @deshdeepak01

    Thank you for the update.

    Please stay on PHP 7.4 whilst we run tests.

    – 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 below:

    Enable debugging mode (increases database load).

    – Disable the option below if it is enabled:

    Start all scans remotely (Try this if your scans aren’t starting and your site is publicly accessible).

    – Hit the SAVE CHANGES button.

    – Start a new scan.

    – If the scan fails with a message saying that the scan has failed, stop the scan and click on the VIEW FULL LOG link and copy the most recent 20 or so lines of the scan activity log and paste in a reply here. If that new browser tab fails to load then copy the most recent 20 or so lines of the scan activity log area from the Scan page itself.

    – Remember to disable Enable debugging mode (increases database load) after you have finished.

    Thread Starter deshdeepak01

    (@deshdeepak01)

    4 years, 4 months ago

    I’ve done every step which you’ve mentioned in your reply. Even after doing all steps, the result is the same i.e. ‘Scanning Failed’.

    Here is the scan activity log…

    [Jan 12 03:03:18:1641956598.455567:10:info] SUM_KILLED:A request was received to stop the previous scan.
[Jan 12 03:03:18:1641956598.455071:1:info] Scan stop request received.
[Jan 12 03:03:09:1641956589.933231:1:error] <br /> <b>Deprecated</b>: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
[Jan 12 03:03:09:1641956589.931030:2:error] Scan terminated with error: The Wordfence scanning servers are currently unavailable. This may be for maintenance or a temporary outage. If this still occurs in an hour, please contact support. [404]
[Jan 12 03:03:09:1641956589.929074:2:info] Wordfence used 0 B of memory for scan. Server peak memory usage was: 91 MB
[Jan 12 03:03:09:1641956589.750498:4:error] Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice (8192) File: /home1/nmbtoymy/public_html/mypathtofitness/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php Line: 91
[Jan 12 03:03:09:1641956589.749893:4:error] Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice (8192) File: /home1/nmbtoymy/public_html/mypathtofitness/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php Line: 82
[Jan 12 03:03:09:1641956589.744774:4:error] Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice (8192) File: /home1/nmbtoymy/public_html/mypathtofitness/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php Line: 68
[Jan 12 03:03:09:1641956589.744347:4:error] Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice (8192) File: /home1/nmbtoymy/public_html/mypathtofitness/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php Line: 51
[Jan 12 03:03:09:1641956589.743635:4:error] Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice (8192) File: /home1/nmbtoymy/public_html/mypathtofitness/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php Line: 40
[Jan 12 03:03:09:1641956589.487360:4:error] http_build_query(): Passing null to parameter #2 ($numeric_prefix) of type string is deprecated (8192) File: /home1/nmbtoymy/public_html/mypathtofitness/wp-includes/Requests/Transport/cURL.php Line: 345
[Jan 12 03:03:09:1641956589.481640:4:error] Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice (8192) File: /home1/nmbtoymy/public_html/mypathtofitness/wp-includes/Requests/Cookie/Jar.php Line: 111
[Jan 12 03:03:09:1641956589.481331:4:error] Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice (8192) File: /home1/nmbtoymy/public_html/mypathtofitness/wp-includes/Requests/Cookie/Jar.php Line: 102
[Jan 12 03:03:09:1641956589.480986:4:error] Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice (8192) File: /home1/nmbtoymy/public_html/mypathtofitness/wp-includes/Requests/Cookie/Jar.php Line: 89
[Jan 12 03:03:09:1641956589.480582:4:error] Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice (8192) File: /home1/nmbtoymy/public_html/mypathtofitness/wp-includes/Requests/Cookie/Jar.php Line: 73
[Jan 12 03:03:09:1641956589.480102:4:error] Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice (8192) File: /home1/nmbtoymy/public_html/mypathtofitness/wp-includes/Requests/Cookie/Jar.php Line: 63
[Jan 12 03:03:09:1641956589.478532:4:info] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=65b569e9a3a6c8e62d68599c61794d9399a3b107ad1854100fb86c31541d0860e7a1ebb1a0464f59db132328fdcf0ff42c1cae29eed4d3c21389bfec758a966d&s=eyJ3cCI6IjUuOC4zIiwid2YiOiI3LjUuNyIsIm1zIjpmYWxzZSwiaCI6Imh0dHBzOlwvXC9teXBhdGh0b2ZpdG5lc3MuY29tIiwic3NsdiI6MjY5NDg4MzUxLCJwdiI6IjguMS4xIiwicHQiOiJjZ2ktZmNnaSIsImN2IjoiNy44MC4wIiwiY3MiOiJPcGVuU1NMXC8xLjEuMW0iLCJzdiI6IkFwYWNoZSIsImR2IjoiNS43LjIzLTIzIiwibGFuZyI6IiJ9&betaFeed=0&action=log_scan
[Jan 12 03:03:09:1641956589.477839:1:info] Contacting Wordfence to initiate scan
[Jan 12 03:03:09:1641956589.469562:10:info] SUM_PREP:Preparing a new scan.
[Jan 12 03:03:09:1641956589.466198:4:info] Setting up scanRunning and starting scan
[Jan 12 03:03:09:1641956589.466044:4:info] Setting up error handling environment
[Jan 12 03:03:09:1641956589.465851:4:info] Requesting max memory
[Jan 12 03:03:09:1641956589.464900:4:info] Checking if scan is already running
[Jan 12 03:03:09:1641956589.464276:4:info] Checking saved cronkey against cronkey param
[Jan 12 03:03:09:1641956589.464085:4:info] Checking cronkey: 50d0b28484d83b4414433427bd721634 (expecting 50d0b28484d83b4414433427bd721634)
[Jan 12 03:03:09:1641956589.463835:4:info] Fetching stored cronkey for comparison.
[Jan 12 03:03:09:1641956589.463568:4:info] Verifying start request signature.
[Jan 12 03:03:09:1641956589.463173:4:info] Scan engine received request.
[Jan 12 03:03:08:1641956588.628373:4:info] Scan process ended after forking.
[Jan 12 03:03:07:1641956587.625979:4:info] Starting cron with normal ajax at URL https://mypathtofitness.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&scanMode=standard&cronKey=50d0b28484d83b4414433427bd721634&signature=a3d26485e2d2a7b73b1c6b00931d73e0b5618dea8ebd62da9c30bd1752062a5e
[Jan 12 03:03:07:1641956587.624519:4:info] Test result of scan start URL fetch: array ( 'headers' => Requests_Utility_CaseInsensitiveDictionary::__set_state(array( 'data' => array ( 'date' => 'Wed, 12 Jan 2022 03:03:07 GMT', 'content-type' => 'text/html; charset=UTF-8', 'x-robots-tag' => 'noindex', 'x-content-type-options' => 'nosniff', 'expires' => 'Wed, 11 Jan 1984 05:00:00 GMT', 'cache-control' => 'no-cache, must-revalidate, max-age=0', 'x-frame-options' => 'SAMEORIGIN', 'referrer-policy' => array ( 0 => 'strict-origin-when-cross-origin', 1 => 'no-referrer-when-downgrade', ), 'vary' => 'Accept-Encoding,X-Forwarded-Proto,User-Agent', 'cf-cache-status' => 'DYNAMIC', 'expect-ct' => 'max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"', 'server' => 'cloudflare', 'cf-ray' => '6cc32654583031bb-LAX', 'content-encoding' => 'gzip', ), )), 'body' => 'WFSCANTESTOK',
[Jan 12 03:03:05:1641956585.565482:4:info] getMaxExecutionTime() returning config value: 20
[Jan 12 03:03:05:1641956585.565276:4:info] Got value from wf config maxExecutionTime: 20
[Jan 12 03:03:05:1641956585.564736:4:info] Entering start scan routine
[Jan 12 03:03:05:1641956585.563277:4:info] Ajax request received to start scan.
[Jan 12 03:02:55:1641956575.206527:10:info] SUM_KILLED:A request was received to stop the previous scan.
[Jan 12 03:02:55:1641956575.205726:1:info] Scan stop request received.
[Jan 12 03:02:32:1641956552.266240:1:error] <br /> <b>Deprecated</b>: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
[Jan 12 03:02:32:1641956552.265767:2:error] Scan terminated with error: The Wordfence scanning servers are currently unavailable. This may be for maintenance or a temporary outage. If this still occurs in an hour, please contact support. [404]
[Jan 12 03:02:32:1641956552.265437:2:info] Wordfence used 0 B of memory for scan. Server peak memory usage was: 91 MB
[Jan 12 03:02:32:1641956552.185159:4:error] Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice (8192) File: /home1/nmbtoymy/public_html/mypathtofitness/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php Line: 91
[Jan 12 03:02:32:1641956552.184805:4:error] Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice (8192) File: /home1/nmbtoymy/public_html/mypathtofitness/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php Line: 82
[Jan 12 03:02:32:1641956552.184498:4:error] Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice (8192) File: /home1/nmbtoymy/public_html/mypathtofitness/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php Line: 68
[Jan 12 03:02:32:1641956552.184038:4:error] Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice (8192) File: /home1/nmbtoymy/public_html/mypathtofitness/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php Line: 51
[Jan 12 03:02:32:1641956552.183358:4:error] Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice (8192) File: /home1/nmbtoymy/public_html/mypathtofitness/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php Line: 40
[Jan 12 03:02:31:1641956551.951398:4:error] http_build_query(): Passing null to parameter #2 ($numeric_prefix) of type string is deprecated (8192) File: /home1/nmbtoymy/public_html/mypathtofitness/wp-includes/Requests/Transport/cURL.php Line: 345
[Jan 12 03:02:31:1641956551.947030:4:error] Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice (8192) File: /home1/nmbtoymy/public_html/mypathtofitness/wp-includes/Requests/Cookie/Jar.php Line: 111
[Jan 12 03:02:31:1641956551.946621:4:error] Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice (8192) File: /home1/nmbtoymy/public_html/mypathtofitness/wp-includes/Requests/Cookie/Jar.php Line: 102
[Jan 12 03:02:31:1641956551.945894:4:error] Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice (8192) File: /home1/nmbtoymy/public_html/mypathtofitness/wp-includes/Requests/Cookie/Jar.php Line: 89
[Jan 12 03:02:31:1641956551.945032:4:error] Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice (8192) File: /home1/nmbtoymy/public_html/mypathtofitness/wp-includes/Requests/Cookie/Jar.php Line: 73
    Plugin Support wfphil

    (@wfphil)

    4 years, 4 months ago

    Hi @deshdeepak01

    Thank you for the update.

    The reason that your scans are failing is because you are using a nulled premium version of Wordfence that may have come prepackaged with malware. See our article below:

    https://www.wordfence.com/blog/2021/07/nulled-wordpress-plugins/

    You will need to delete Wordfence and all Wordfence database tables and reinstall the official version of Wordfence.

    We recommend that you also follow our site cleaning guide below:

    https://www.wordfence.com/docs/how-to-clean-a-hacked-wordpress-site-using-wordfence/

    Wordfence can only be obtained from the ww.wp.xz.cn plugin repository and a Wordfence premium license key can only be obtained from wordfence.com

Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘Wordfence scanning failed’ is closed to new replies.