cURL error7

  • Dear Support,

    I already have oppened a thread but it remains unanswered.
    Here : https://www.ads-software.com/support/topic/sitemap-error-by-wordfence-unable-to-run-scan-curl-error-7-cloudflare

    I have already completed all the steps indicated here – as I am on CDN CloudFlare, the error looks the same.

    But, after a month with what seems a correct configuration, every Wordfence scan ends forking.

    What could be the solution ?

    The error show in Diagnostics>Connectivity says :

    Connecting back to this site via IPv6 (not required; failure to connect may not be an issue on some sites)

    Response was: cURL error 7: Failed to connect to [website] port 443

    I am sending a repport now by mail.
    Any help would be appreciated.
    Thanks.
    Clément

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

    (@wfpeter)

    Hi @clementdouillet, thanks for sending that over, my apologies for missing that. I have closed the other topic and we’ll continue here.

    The IPv6 connectivity error in your diagnostic occurs when Cloudflare assigns an IPv6 address to your site, but your host doesn’t actually give you an IPv6 address. As your site seems to work with IPv4, the IPv6 error shouldn’t be affecting the site.

    On some hosts, when the scan “forks”, it sometimes tries to use?Cloudflare’s IPv6 address for the site, but the host may not allow outbound IPv6 connections. We added an option,?Use only IPv4 to start scans which could help in that case. You can find it in Wordfence > All Options > Advanced Scan Options.

    Let me know how you get on!
    Peter.

    Thread Starter clementdouillet

    (@clementdouillet)

    Hi Peter,
    Thanks for answering.

    The suggested option was already ticked on, so the problem might not come from here.

    What other options could I check ?

    Thanks,
    Clément

    Thread Starter clementdouillet

    (@clementdouillet)

    Hi Again Peter,
    The scan still is fokring, even after all setting specified.

    I had a possible lead:
    Is it possible that the forking comes from the fact that my domain is not a “primary” domain – i.e. linked to a way or another to a “main” domain?

    Maybe that could explain the forking?

    Thanks,
    Clément

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘cURL error7’ is closed to new replies.