• Resolved andrewmili

    (@andrewmili)


    I get the following error message:
    Scan failed: There was an error connecting to the the Wordfence scanning servers: cURL error 28:

    I turned off the “Enable SSL Verification” option at the bottom of the diagnostics page and no luck.

    The connectivity is also good.

    Connecting to Wordfence servers (http) ?OK
    Connecting to Wordfence servers (https) ?OK

Viewing 14 replies - 1 through 14 (of 14 total)
  • Hi @andrewmili,

    This specific cURL error (28) indicates an operation timeout.

    As you’ve already disabled SSL Verification and checked that the connectivity to Wordfence servers is OK, the problem could’ve been caused by a temporary connection issue.

    However, should the problem persist could you please check the error log files which you can download from:

    • Wordfence Tools page
    • Diagnostics tab
    • Log Files (Error messages from WordPress core, plugins, and themes) section

    Can you see any errors related to connectivity or timeout there?

    Thread Starter andrewmili

    (@andrewmili)

    I accessed the Diagnostics tab, scrolled to the bottom of the page, and reviewed the LOG Files (Error messages from WordPress core, plugins, and themes) section. It displays the following message:

    No log files found.

    I trust you can help solve this mystery.

    Hi @andrewmili,

    Sorry about the delayed response.

    Have you been able to run a scan successfully? Has the cURL timeout error occurred again?

    If you have access to them I suggest you check the web server logs directly on the host. (The files location will depend on your environment. Your hosting provider can help you locate them)

    Hi @andrewmili,

    Since I haven’t heard back from you I am assuming that you’ve managed to identify the cause of the issue so I am marking this topic as resolved.

    If however, for whatever reason, you are still experiencing this issue and it is not resolved please respond to the post, which will move it back up the queue, and mark this topic as “not resolved”.

    Thank you.

    Thread Starter andrewmili

    (@andrewmili)

    Hello wfyann.

    I am sorry to say the issue is unresolved. As per your instructions I contacted my hosting provided (Godaddy). I was not able to get any information with respect to server logs.

    I use Godaddys Managed WordPress service and have several websites with them. All my websites use Wordfence and only one of them is having an issue with Wordfence.

    I feel I am at a dead-end unless you have any other suggests that might help me resolve the issue I am having.

    Best Regards

    • This reply was modified 7 years, 10 months ago by andrewmili.
    • This reply was modified 7 years, 10 months ago by andrewmili.

    Hi @andrewmili,

    Thank you for getting back to me… Let’s keep investigating, then!

    Could you please:

    • Go to the Wordfence Tools page
    • Click the Diagnostics tab
    • Scroll down to the Send Report by Email section
    • Send the report to yann[at]wordfence[dot]com
    Thread Starter andrewmili

    (@andrewmili)

    Hello wfyann.
    The I sent the email report.
    Thanks for all you assistance.
    Best Regards

    Hello @andrewmili,

    It seems that the max_execution_timeMaster Value (30)” (from php.ini) is being overridden by the “Local Value(800)” which could be set in httpd.conf, .htaccess or other Apache configuration elements with php_value directive.

    Do you have the same settings on the other sites you mentioned?

    Would it be possible for you to send me a Diagnostics report for one of the sites where Wordfence works fine?

    Thread Starter andrewmili

    (@andrewmili)

    Hello wfyann

    I believe the local value of 800, that you mentioned in the thread above, is set in the user.ini file.

    I just sent you another Diagnostic report, for another website, where Wordfence is working.

    Best Regards

    Hi @andrewmili,

    Sorry about the slow reply.

    I looked into both reports you sent but couldn’t find anything in them that would explain the difference in behavior.

    However, a reverse IP domain check showed that the site where Wordfence works is on a shared hosting as opposed to the one where Wordfence doesn’t work which seems to be the only site hosted on another server (I’m avoiding specifying the site’s URLs here for confidentiality purposes).

    The issue could be caused by limitations based on resources PHP scripts use, as explained in this post. Such limitations could’ve been implemented for one host but not for the other.

    Also, in order to provide us with more information on the sequence of events, could you please enable the Debugging Mode and paste here the last 20 lines or so of the activity log as described here?

    Thank you.

    Thread Starter andrewmili

    (@andrewmili)

    Hello Wfyann.

    Thank you for the information w.r.t. to the limitation based on PHP resources.
    I reset the Wordfence memory limit from 256 MB to 128 MB and performed another scan and encountered the same error.

    I have emailed the activity log to your attention. I did so because the activity log file appears to have what I would consider confidential information that I did not want to post here. I trust you can keep an eye out for the email.

    Thank you.

    Hi @andrewmili,

    Sorry about the delayed response.

    Have you tried tuning the “Maximum execution time for each scan stage” setting?

    It seems to have worked for this user who was having a similar issue.

    Thread Starter andrewmili

    (@andrewmili)

    Hello wfyann.
    I am happy to report the issue is resolved.
    I recently updated to the recent version of Wordfence and at the same time changed the maximum execution time for each stage.

    Thanks for the support!

    Hi @andrewmili,

    Thanks for the feedback.

    I’m glad your Wordfence scans are now running to completion!

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Scan Failed’ is closed to new replies.