Scan terminated with error: since last update

  • Resolved themps

    (@themps)


    7 years, 12 months ago

    I’ve been getting this ever since the last plugin update.

    “Scan terminated with error: There was an error connecting to the the Wordfence scanning servers: cURL error 28: connect() timed out!”

    Everything was fine before the last update.

    Anyone else having problems like this? Any possible fix?

    No known patterns. It stops at different points within scans.

    Thanks

    • This topic was modified 7 years, 12 months ago by themps.
Viewing 7 replies - 1 through 7 (of 7 total)

  • Hi themps,
    Please check (Wordfence > Diagnostics => Connectivity) and let me know what you have there, while you are on the same page, please check the value for “Checking for cURL support”.

    You may also try turning off “Enable SSL Verification” option down at the bottom of the diagnostics page then try re-saving the Wordfence Options page again.

    Let me know how it goes,
    Thanks.

    Thread Starter themps

    (@themps)

    Thanks, green check mark and “7.24.0” for cURL

    I’ll let you know how the ssl change goes.

    Thread Starter themps

    (@themps)

    I disabled and re-enabled SSL. First scan worked. It had worked fine for a year or more previously. I’ll update here if it abends again.

    Thread Starter themps

    (@themps)

    Ok, so this time I receievd the cURL issue error out trying to get to your servers but also this…
    Notice: Undefined index: HTTP_REFERER in /home2/**basepathformyste****/public_html/wp-content/plugins/w3-total-cache/DbCache_WpdbInjection_QueryCaching.php on line 366 Notice: Undefined index: HTTP_REFERER in /home2/

    I’m turning off the ssl in diagnostics now to see how it goes.

    There is a known issue related to “W3 total cache” plugin while initiating scans with “Database caching” option turned on, so I suggest turning it off for now while scanning, also you should know that this plugin has some incompatibility issues with the latest version of WordPress (version 4.7).

    Regarding the cURL issue, if you are still running into this one, I recommend shooting an email to your web host asking for more details about this “connect() timed out” error.

    Thanks.

    Thread Starter themps

    (@themps)

    Ok thanks. Yeah disabling the SSL option fixed thr cURL issue. I am on BlueHost. Is that a big deal security wise to disable that?

    Also thanks for the W3 info.

    • This reply was modified 7 years, 11 months ago by themps.

    No, you can keep it like that, however, I still recommend trying to resolve this issue regarding the “connect() timed out” with your web host.

    Thanks.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Scan terminated with error: since last update’ is closed to new replies.