Wordfence website Scan failing

  • Resolved ramardent

    (@ramardent)


    1 week, 5 days ago

    Hi there,

    I am having trouble to scan my website using Wordfence. I am using free version of the plugin.

    I have followed the steps provided here https://www.wordfence.com/help/scan/troubleshooting/.

    The error displayed in scan fail is “Scan Failed: 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.(opens in new tab)The error returned was:There was an error connecting to the Wordfence scanning servers: cURL error 28: Resolving timed out after 10000 milliseconds“.

    I have turned on the Debugging Mode and these are the logs I found in log file: 

    Nov 13 09:40:29] Asking Wordfence to check URLs against malware list.
    [Nov 13 09:40:29] Checking 1208 host keys against Wordfence scanning servers.
    [Nov 13 09:41:44] Wordfence used 27.38 MB of memory for scan. Server peak memory usage was: 110.38 MB
    [Nov 13 09:41:44] Scan terminated with error: There was an error connecting to the Wordfence scanning servers: cURL error 28: Resolving timed out after 10000 milliseconds
    [Nov 13 10:14:41] Contacting Wordfence to initiate scan
    [Nov 13 10:15:01] Wordfence used 2 MB of memory for scan. Server peak memory usage was: 83 MB
    [Nov 13 10:15:01] Scan terminated with error: There was an error connecting to the Wordfence scanning servers: cURL error 28: Resolving timed out after 10000 milliseconds
    [Nov 13 10:17:35] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=add619440049726b4ccd6927518de23144527ed8566f105ef52d1382ffba09c91af0441fd2edbc962d7a2105cc36f87c288f33939a1c7f0cc5272ff2bbd695b9&s=eyJ3cCI6IjYuNi4yIiwid2YiOiI4LjAuMCIsIm1zIjpmYWxzZSwiaCI6Imh0dHBzOlwvXC91dGVoaXJlLnRyYWRpZXNwZWMuY29tLmF1Iiwic3NsdiI6MjY5NDg4NDk1LCJwdiI6IjguMS4yMyIsInB0IjoiY2dpLWZjZ2kiLCJjdiI6IjcuODEuMCIsImNzIjoiT3BlblNTTFwvMS4xLjFtIiwic3YiOiJBcGFjaGUiLCJkdiI6IjUuNi41MSIsImxhbmciOiIifQ&action=timestamp
    [Nov 13 10:17:42] Ajax request received to start scan.
    [Nov 13 10:17:42] Entering start scan routine
    [Nov 13 10:17:42] Got value from wf config maxExecutionTime: 0
    [Nov 13 10:17:42] Got max_execution_time value from ini: 60
    [Nov 13 10:17:42] getMaxExecutionTime() returning half ini value: 30
    [Nov 13 10:17:43] Test result of scan start URL fetch: array ( 'headers' => WpOrg\Requests\Utility\CaseInsensitiveDictionary::__set_state(array( 'data' => array ( 'date' => 'Tue, 12 Nov 2024 23:17:42 GMT', 'server' => 'Apache', 'x-robots-tag' => 'noindex', 'x-content-type-options' => array ( 0 => 'nosniff', 1 => 'nosniff', ), 'expires' => 'Wed, 11 Jan 1984 05:00:00 GMT', 'cache-control' => 'no-cache, must-revalidate, max-age=0', 'referrer-policy' => array ( 0 => 'strict-origin-when-cross-origin', 1 => 'no-referrer', ), 'x-frame-options' => 'sameorigin', 'strict-transport-security' => 'max-age=31536000; includeSubDomains; preload', 'x-xss-protection' => '1; mode=block', 'x-permitted-cross-domain-policies' => 'none', 'content-type' => 'text/html; charset=UTF-8', ), )), 'body' => 'WFSCANTESTOK', 'response' => array ( 'code' => 200, 'message' =
    [Nov 13 10:17:43] Starting cron with normal ajax at URL https://utehire.tradiespec.com.au/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&scanMode=highsensitivity&cronKey=3b88bb87f4c9799b6dd8c03028ed181b&signature=ee9a697994cd3d25832c780112067f48d9cfecfd4fff4163ab4215eb3b352914
    [Nov 13 10:17:44] Scan engine received request.
    [Nov 13 10:17:44] Verifying start request signature.
    [Nov 13 10:17:44] Fetching stored cronkey for comparison.
    [Nov 13 10:17:44] Checking cronkey: 3b88bb87f4c9799b6dd8c03028ed181b (expecting 3b88bb87f4c9799b6dd8c03028ed181b)
    [Nov 13 10:17:44] Checking saved cronkey against cronkey param
    [Nov 13 10:17:44] Checking if scan is already running
    [Nov 13 10:17:44] Requesting max memory
    [Nov 13 10:17:44] Setting up error handling environment
    [Nov 13 10:17:44] Setting up scanRunning and starting scan
    [Nov 13 10:17:44] Contacting Wordfence to initiate scan
    [Nov 13 10:17:44] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=add619440049726b4ccd6927518de23144527ed8566f105ef52d1382ffba09c91af0441fd2edbc962d7a2105cc36f87c288f33939a1c7f0cc5272ff2bbd695b9&s=eyJ3cCI6IjYuNi4yIiwid2YiOiI4LjAuMCIsIm1zIjpmYWxzZSwiaCI6Imh0dHBzOlwvXC91dGVoaXJlLnRyYWRpZXNwZWMuY29tLmF1Iiwic3NsdiI6MjY5NDg4NDk1LCJwdiI6IjguMS4yMyIsInB0IjoiY2dpLWZjZ2kiLCJjdiI6IjcuODEuMCIsImNzIjoiT3BlblNTTFwvMS4xLjFtIiwic3YiOiJBcGFjaGUiLCJkdiI6IjUuNi41MSIsImxhbmciOiIifQ&action=log_scan
    [Nov 13 10:17:44] Wordfence used 0 B of memory for scan. Server peak memory usage was: 81 MB
    [Nov 13 10:17:44] Scan terminated with error: There was an error connecting to the Wordfence scanning servers: cURL error 6: Could not resolve host: noc1.wordfence.com
    [Nov 13 10:17:44] Scan process ended after forking.
    [Nov 13 10:20:27] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=add619440049726b4ccd6927518de23144527ed8566f105ef52d1382ffba09c91af0441fd2edbc962d7a2105cc36f87c288f33939a1c7f0cc5272ff2bbd695b9&s=eyJ3cCI6IjYuNi4yIiwid2YiOiI4LjAuMCIsIm1zIjpmYWxzZSwiaCI6Imh0dHBzOlwvXC91dGVoaXJlLnRyYWRpZXNwZWMuY29tLmF1Iiwic3NsdiI6MjY5NDg4NDk1LCJwdiI6IjguMS4yMyIsInB0IjoiY2dpLWZjZ2kiLCJjdiI6IjcuODEuMCIsImNzIjoiT3BlblNTTFwvMS4xLjFtIiwic3YiOiJBcGFjaGUiLCJkdiI6IjUuNi41MSIsImxhbmciOiIifQ&action=timestamp
    [Nov 13 10:23:45] Ajax request received to start scan.
    [Nov 13 10:23:45] Entering start scan routine
    [Nov 13 10:23:45] Got value from wf config maxExecutionTime: 0
    [Nov 13 10:23:45] Got max_execution_time value from ini: 60
    [Nov 13 10:23:45] getMaxExecutionTime() returning half ini value: 30
    [Nov 13 10:23:46] Test result of scatch: arn start URL feray ( 'headers' => WpOrg\Requests\Utility\CaseInsensitiveDictionary::__set_state(array( 'data' => array ( 'date' => 'Tue, 12 Nov 2024 23:23:45 GMT', 'server' => 'Apache', 'x-robots-tag' => 'noindex', 'x-content-type-options' => array ( 0 => 'nosniff', 1 => 'nosniff', ), 'expires' => 'Wed, 11 Jan 1984 05:00:00 GMT', 'cache-control' => 'no-cache, must-revalidate, max-age=0', 'referrer-policy' => array ( 0 => 'strict-origin-when-cross-origin', 1 => 'no-referrer', ), 'x-frame-options' => 'sameorigin', 'strict-transport-security' => 'max-age=31536000; includeSubDomains; preload', 'x-xss-protection' => '1; mode=block', 'x-permitted-cross-domain-policies' => 'none', 'content-type' => 'text/html; charset=UTF-8', ), )), 'body' => 'WFSCANTESTOK', 'response' => array ( 'code' => 200, 'message' =
    [Nov 13 10:23:46] Starting cron with normal ajax at URL https://utehire.tradiespec.com.au/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&scanMode=highsensitivity&cronKey=51151b2f6a146bc3d4909df40428edf8&signature=6077cf73c606f326c7d87fd92bd758ef036d7a26bb920e16301dae4837c6fe81
    [Nov 13 10:23:47] Scan engine received request.
    [Nov 13 10:23:47] Verifying start request signature.
    [Nov 13 10:23:47] Fetching stored cronkey for comparison.
    [Nov 13 10:23:47] Checking cronkey: 51151b2f6a146bc3d4909df40428edf8 (expecting 51151b2f6a146bc3d4909df40428edf8)
    [Nov 13 10:23:47] Checking saved cronkey against cronkey param
    [Nov 13 10:23:47] Checking if scan is already running
    [Nov 13 10:23:47] Requesting max memory
    [Nov 13 10:23:47] Setting up error handling environment
    [Nov 13 10:23:47] Setting up scanRunning and starting scan
    [Nov 13 10:23:47] Contacting Wordfence to initiate scan
    [Nov 13 10:23:47] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=add619440049726b4ccd6927518de23144527ed8566f105ef52d1382ffba09c91af0441fd2edbc962d7a2105cc36f87c288f33939a1c7f0cc5272ff2bbd695b9&s=eyJ3cCI6IjYuNi4yIiwid2YiOiI4LjAuMCIsIm1zIjpmYWxzZSwiaCI6Imh0dHBzOlwvXC91dGVoaXJlLnRyYWRpZXNwZWMuY29tLmF1Iiwic3NsdiI6MjY5NDg4NDk1LCJwdiI6IjguMS4yMyIsInB0IjoiY2dpLWZjZ2kiLCJjdiI6IjcuODEuMCIsImNzIjoiT3BlblNTTFwvMS4xLjFtIiwic3YiOiJBcGFjaGUiLCJkdiI6IjUuNi41MSIsImxhbmciOiIifQ&action=log_scan
    [Nov 13 10:23:47] Scan process ended after forking.
    [Nov 13 10:24:07] Wordfence used 0 B of memory for scan. Server peak memory usage was: 81 MB
    [Nov 13 10:24:07] Scan terminated with error: There was an error connecting to the Wordfence scanning servers: cURL error 28: Resolving timed out after 10000 milliseconds

    Can anyone help me please?

    Regards.

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter ramardent

    (@ramardent)

    Hi, this is the screenshot of Connectivity under Diagnostics https://ibb.co/mThcY7h

    Thread Starter ramardent

    (@ramardent)

    Under Scan Options and Scheduling >> Performance Options, I input the Maximum execution time for each scan stage to 30, it started scanning files but then again stopped after a while with same error Scan Failed.

    Plugin Support wfpeter

    (@wfpeter)

    Hi @ramardent, thanks for getting in touch and providing so much useful information straight away.

    The?cURL error 6 in your diagnostics, rather than being a “blocked” type message is stating its failure to reach the intended destination (our servers) altogether. This will impact scans, updates, etc. and I believe is the main reason for your timeout.

    Our IP addresses that sometimes need to be allowed in load balancers, server-side firewalls etc. are available for your reference in our help documentation: https://www.wordfence.com/help/advanced/#servers-and-ip-addresses

    My first instinct, unless you’re running on?Cloudflare?or?LiteSpeed?where whitelisting our IPs or?a configuration change to the noabort?code could help, would be to see if your host can see a fundamental reason why your site would be having trouble making any outbound connections. They could try running?curl -v https://noc1.wordfence.com/?for you to send us the output. It’s not a perfect test since it’s not within PHP, but it may show if the server’s resolver is getting the wrong IP.

    Many thanks,
    Peter.

    Hi @ramardent,

    If you don’t mind, please allow me to help.

    Potential Solutions:

    1. Visit this link and go through every item.
    2. If using Cloudflare, Whitelist in Cloudflare the Wordfence IPs provided by @wfpeter. Also, make sure you have enabled this setting in Wordfence.
    3. It appears you’re using Cloudflare Turnstile (CT). If your CT settings are incorrect or not connecting properly to your server (host, etc.), this could be part of your problem. Currently, your website is showing a CT failure message. You could also try disabling CT to see if that helps.
    4. Review and solve your website’s console errors. It appears some are being caused by your .htaccess file which could be another source of your issue.
    5. Once you perform the above checks, clear all of your cache layers and perform a new Wordfence scan. Yes, clearing cache many times solves this issue.

    If satisfied with the above, please consider closing this topic as “Resolved.”

    Cheers!

    Note: I’m not affiliated with Wordfence. Simply offering goodwill support.

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

Tags