Scan failed

  • Resolved noelie33

    (@noelie33)


    1 month ago

    Hi,

    I’m having some issue with the Wordfence scan : “The current scan looks like it has failed. Its last status update was 20 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 to fix it by changing the maximum execution time to 20 and I also enable debugging mode

    but nothing changes…

    This are my last 20 lines or so of the activity log. Can you please help me ? Thanks in advance

    [Mar 11 17:33:13:1773246793.724854:4:info] Calling Wordfence API v2.27:https://noc1.wordfence.com/v2.27/?k=203d60a2adbbf487e59c23429c06f72f36419b2ffb4903886bafa05af210c4faa03542556dec797fe7bfe4f3ce7f437b337eb4ac4ef3216fc4c2b58bea2e75e793cbfd6c8be3bba2bac56a074660809c&s=eyJ3cCI6IjYuOS40Iiwid2YiOiI4LjEuNCIsIm1zIjpmYWxzZSwiaCI6Imh0dHBzOlwvXC9jaG9jb2xhdGluZS1mcmVuY2gtYWNhZGVteS5jb20iLCJzc2x2IjoyNjk0ODg1MTEsInB2IjoiOC4yLjI5IiwicHQiOiJsaXRlc3BlZWQiLCJjdiI6IjguMTQuMSIsImNzIjoiT3BlblNTTFwvMS4xLjF3Iiwic3YiOiJMaXRlU3BlZWQiLCJkdiI6IjExLjguMy1NYXJpYURCLWxvZyIsImxhbmciOiIifQ&action=timestamp

    [Mar 11 17:26:13:1773246373.898148:2:info] Scanned contents of 529 additional files at 9.38 per second

    [Mar 11 17:26:12:1773246372.383996:2:info] Scanned contents of 523 additional files at 9.52 per second

    [Mar 11 17:26:11:1773246371.343209:2:info] Scanned contents of 512 additional files at 9.50 per second

    [Mar 11 17:26:08:1773246368.520304:2:info] Scanned contents of 490 additional files at 9.60 per second

    [Mar 11 17:26:07:1773246367.469901:2:info] Scanned contents of 478 additional files at 9.56 per second

    [Mar 11 17:26:06:1773246366.336273:2:info] Scanned contents of 473 additional files at 9.68 per second

    [Mar 11 17:26:05:1773246365.278298:2:info] Scanned contents of 457 additional files at 9.56 per second

    [Mar 11 17:26:02:1773246362.980423:2:info] Scanned contents of 456 additional files at 10.02 per second

    [Mar 11 17:26:01:1773246361.977928:2:info] Scanned contents of 433 additional files at 9.73 per second

    [Mar 11 17:26:00:1773246360.951302:2:info] Scanned contents of 404 additional files at 9.29 per second

    [Mar 11 17:25:59:1773246359.877314:2:info] Scanned contents of 389 additional files at 9.17 per second

    [Mar 11 17:25:58:1773246358.872712:2:info] Scanned contents of 365 additional files at 8.82 per second

    [Mar 11 17:25:57:1773246357.821384:2:info] Scanned contents of 353 additional files at 8.75 per second

    [Mar 11 17:25:56:1773246356.176754:2:info] Scanned contents of 336 additional files at 8.68 per second

    [Mar 11 17:25:55:1773246355.168168:2:info] Scanned contents of 318 additional files at 8.44 per second

    [Mar 11 17:25:54:1773246354.164118:2:info] Scanned contents of 303 additional files at 8.26 per second

    [Mar 11 17:25:52:1773246352.805668:2:info] Scanned contents of 297 additional files at 8.41 per second

    [Mar 11 17:25:51:1773246351.357051:2:info] Scanned contents of 293 additional files at 8.65 per second

    [Mar 11 17:25:50:1773246350.314033:2:info] Scanned contents of 279 additional files at 8.50 per second

    [Mar 11 17:25:49:1773246349.290731:2:info] Scanned contents of 258 additional files at 8.11 per second

    [Mar 11 17:25:46:1773246346.983261:2:info] Scanned contents of 232 additional files at 7.86 per second


Viewing 4 replies - 1 through 4 (of 4 total)
  • ssasidharan

    (@ssasidharan)

    1 month ago

    Wordfence recently deprecated their V1 and V2 API endpoints.

    DEPRECATION NOTICE: Versions 1 and 2 of the Vulnerability Data Feed API will be disabled on March 9, 2026 and will stop responding to requests with vulnerability data.

    You should update your implementations to Version 3 of the Vulnerability Data Feed API as soon as possible. The only change is that Version 3 requires authentication with a free API Key, available from your Wordfence.com Account. Read the documentation for more details.

    So you would probably need to update the API endpoint to V3

    Thread Starter noelie33

    (@noelie33)

    1 month ago

    Thank you for your reply. I’ve read the documentation but I can find where to change the API in wordfence plugin. Do I just need to change the authentification ?

    Thank you for your help

    Plugin Support wfmargaret

    (@wfmargaret)

    4 weeks ago

    Hi @noelie33,

    Thank you for reaching out! Just to clarify, the API endpoint in your scan log is the internal Wordfence scan API that the plugin uses to communicate with our servers during scans. This is completely separate from the Vulnerability Data Feed API that was recently deprecated. You don’t need to change anything related to API versions, and that deprecation notice doesn’t apply here.

    Looking at your scan log, I suspect your site is running on a LiteSpeed web server. LiteSpeed has a feature called “External Application Abort” that can silently kill long-running PHP processes like Wordfence scans. This could explain why your scan starts normally, processes files for a while, and then just stops with no real error message.

    We have a guide and a video walkthrough specifically for this:

    Documentation: https://www.wordfence.com/help/advanced/system-requirements/litespeed/
    Video walkthrough: https://youtu.be/SXvfSaY1q_c

    The short version is that you’ll need to add a small code block to your site’s .htaccess file (above the # BEGIN WordPress line) to prevent LiteSpeed from aborting the scan process. The video walks through the steps.

    Please give that a try and let us know how it goes!

    Thanks,
    Margaret

    Thread Starter noelie33

    (@noelie33)

    3 weeks, 6 days ago

    Hi Margaret,

    Thank you for your message, I’ve add the code block and so far the issue seems fix !

    Thank you so much again 🙂

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

You must be logged in to reply to this topic.