Wordfence Scan taking too long

  • Resolved insocialdev

    (@insocialdev)


    3 years, 3 months ago

    Good day,

    The Wordfence scan for this site is taking too long and I am hoping to get advice on how to fix it.

    I’ve already tried to set the “Maximum execution time for each scan stage” to 20 with no change/improvement. Each scan runs 40+ minutes each time, but it used to only take 5-10 mins.

    I’ve also already ran the Debugging and I’ve copy pasted the last 20 lines at the bottom of this post.

    Kindly advise, thank you.

    ———-

    [Dec 16 19:12:10:1639681930.374813:4:info] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=5c7842c31381817e26664d0a8818a542690177745518839012d441d0a4ec45fa0e0c875e2cd4c53d11f006f29572e29b989ff7944338340d2de7acd2ec2f22175466b0877ba1f3879bf974e83e4d21a1&s=eyJ3cCI6IjUuOC4yIiwid2YiOiI3LjUuNyIsIm1zIjpmYWxzZSwiaCI6Imh0dHBzOlwvXC9maXhhd3JlY2suY29tIiwic3NsdiI6MjY5NDg4MzM1LCJwdiI6IjcuMy4zMCIsInB0IjoiY2dpLWZjZ2kiLCJjdiI6IjcuNzkuMSIsImNzIjoiT3BlblNTTFwvMS4xLjFsIiwic3YiOiJBcGFjaGUiLCJkdiI6IjUuNy4yNi0yOS1sb2ciLCJsYW5nIjoiIn0&betaFeed=0&action=record_scan_metrics
[Dec 16 19:12:10:1639681930.371174:10:info] SUM_FINAL:Scan complete. You have 6 new issues to fix. See below.
[Dec 16 19:12:10:1639681930.370135:1:info] Scan Complete. Scanned 14265 files, 18 plugins, 7 themes, 13 posts, 0 comments and 10302 URLs in 46 minutes 25 seconds.
[Dec 16 19:12:10:1639681930.369050:2:info] Wordfence used 46.66 MB of memory for scan. Server peak memory usage was: 48.66 MB
[Dec 16 19:12:10:1639681930.367665:1:info] -------------------
[Dec 16 19:12:10:1639681930.359419:10:info] SUM_ENDOK:Scanning for suspicious site options
[Dec 16 19:12:10:1639681930.345998:2:info] Done examining URLs
[Dec 16 19:12:10:1639681930.344779:4:info] Using MySQLi directly.
[Dec 16 19:12:10:1639681930.343710:4:info] Gathering host keys.
[Dec 16 19:12:10:1639681930.341955:2:info] Examining URLs found in the options we scanned for dangerous websites
[Dec 16 19:12:10:1639681930.313337:10:info] SUM_START:Scanning for suspicious site options
[Dec 16 19:12:10:1639681930.301709:10:info] SUM_ENDOK:Scanning for admin users not created through WordPress
[Dec 16 19:12:09:1639681929.983153:4:info] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=5c7842c31381817e26664d0a8818a542690177745518839012d441d0a4ec45fa0e0c875e2cd4c53d11f006f29572e29b989ff7944338340d2de7acd2ec2f22175466b0877ba1f3879bf974e83e4d21a1&s=eyJ3cCI6IjUuOC4yIiwid2YiOiI3LjUuNyIsIm1zIjpmYWxzZSwiaCI6Imh0dHBzOlwvXC9maXhhd3JlY2suY29tIiwic3NsdiI6MjY5NDg4MzM1LCJwdiI6IjcuMy4zMCIsInB0IjoiY2dpLWZjZ2kiLCJjdiI6IjcuNzkuMSIsImNzIjoiT3BlblNTTFwvMS4xLjFsIiwic3YiOiJBcGFjaGUiLCJkdiI6IjUuNy4yNi0yOS1sb2ciLCJsYW5nIjoiIn0&betaFeed=0&action=suspicious_admin_usernames
[Dec 16 19:12:09:1639681929.973563:10:info] SUM_START:Scanning for admin users not created through WordPress
[Dec 16 19:12:09:1639681929.962205:10:info] SUM_ENDBAD:Scanning for old themes, plugins and core files
[Dec 16 19:12:07:1639681927.558635:4:info] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=5c7842c31381817e26664d0a8818a542690177745518839012d441d0a4ec45fa0e0c875e2cd4c53d11f006f29572e29b989ff7944338340d2de7acd2ec2f22175466b0877ba1f3879bf974e83e4d21a1&s=eyJ3cCI6IjUuOC4yIiwid2YiOiI3LjUuNyIsIm1zIjpmYWxzZSwiaCI6Imh0dHBzOlwvXC9maXhhd3JlY2suY29tIiwic3NsdiI6MjY5NDg4MzM1LCJwdiI6IjcuMy4zMCIsInB0IjoiY2dpLWZjZ2kiLCJjdiI6IjcuNzkuMSIsImNzIjoiT3BlblNTTFwvMS4xLjFsIiwic3YiOiJBcGFjaGUiLCJkdiI6IjUuNy4yNi0yOS1sb2ciLCJsYW5nIjoiIn0&betaFeed=0&action=plugin_vulnerability_check
[Dec 16 19:12:06:1639681926.404779:10:info] SUM_START:Scanning for old themes, plugins and core files
[Dec 16 19:12:06:1639681926.391668:10:info] SUM_ENDOK:Scanning for weak passwords
[Dec 16 19:12:06:1639681926.387674:4:info] Completed checking password strength of user 'pwsbuilder'
[Dec 16 19:12:06:1639681926.157948:4:info] Checking password strength of user 'pwsbuilder' with ID 3 (Mem:16.0M)

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @insocialdev, thanks for your detailed message.

    You have absolutely done the right thing in changing the scan stages value to 20 as a first-step and will often have the desired result.

    If you have any caching plugins installed, or other tasks such as site backups scheduled to run in your cron jobs at the same time, this can slow things down also. If you know how your cached pages are stored, you can add these locations to Wordfence > All Options > Advanced Scan Options > Exclude files from scan that match these wildcard patterns (one per line).

    I can check the other settings regarding timeouts and max execution times if you send a diagnostic report to wftest @ wordfence . com. You can find the link to do so at the top of the Wordfence > Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

    NOTE: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email

    Thanks,

    Peter.

    Thread Starter insocialdev

    (@insocialdev)

    Hi Peter,

    I don’t think there was any other backup plugins that were running at the same time — I tried running the scan a few times at different times throughout the day and it was taking a long time for all runs and if it was a plugin that was running at the same time, it’s a little odd if it happened during all the times I was running the scan? Though I inherited the site so I’m not really sure which plugins would cause this. I can investigate the plugins further but I also just sent the Diagnostics report, kindly check as well for me so that if there’s anything you notice, you can let me know.

    Thank you.

    Thread Starter insocialdev

    (@insocialdev)

    Good day @wfpeter

    It’s been a month with no word from you or your team. I’ve already done and sent everything you asked for. Do you still need anything from our end? We’d really like to have this resolved.

    Thank you.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Wordfence Scan taking too long’ is closed to new replies.