Title: cURL error7
Last modified: August 27, 2023

---

# cURL error7

 *  [clementdouillet](https://wordpress.org/support/users/clementdouillet/)
 * (@clementdouillet)
 * [2 years, 9 months ago](https://wordpress.org/support/topic/curl-error7/)
 * Dear Support,
 * I already have oppened a thread but it remains unanswered.
   Here : [https://wordpress.org/support/topic/sitemap-error-by-wordfence-unable-to-run-scan-curl-error-7-cloudflare](https://wordpress.org/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](https://wordpress.org/support/users/wfpeter/)
 * (@wfpeter)
 * [2 years, 9 months ago](https://wordpress.org/support/topic/curl-error7/#post-17009454)
 * Hi [@clementdouillet](https://wordpress.org/support/users/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](https://wordpress.org/support/users/clementdouillet/)
 * (@clementdouillet)
 * [2 years, 9 months ago](https://wordpress.org/support/topic/curl-error7/#post-17010477)
 * 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](https://wordpress.org/support/users/clementdouillet/)
 * (@clementdouillet)
 * [2 years, 9 months ago](https://wordpress.org/support/topic/curl-error7/#post-17025067)
 * 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.

 * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865)
 * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordfence/)
 * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/)

## Tags

 * [forking](https://wordpress.org/support/topic-tag/forking/)
 * [ipv6](https://wordpress.org/support/topic-tag/ipv6/)

 * 3 replies
 * 2 participants
 * Last reply from: [clementdouillet](https://wordpress.org/support/users/clementdouillet/)
 * Last activity: [2 years, 9 months ago](https://wordpress.org/support/topic/curl-error7/#post-17025067)
 * Status: not resolved