Hi @davemspan, thanks for sending that over.
The immediate thing that stuck out to me was the failure Wordfence sees when trying to connect back to your site is a default server 403 Forbidden response:
wp_remote_post() test back to this server failed! Response was:
403 Forbidden
This additional info may help you diagnose the issue. The response headers we received were:
Additional Detail
HTTP/1.1 403
date: Thu, 04 Jan 2024 11:23:53 GMT
server: Apache
content-length: 199
content-type: text/html; charset=iso-8859-1
x-via: LHR4
connection: close
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>403 Forbidden</title>
</head><body>
<h1>Forbidden</h1>
<p>You don't have permission to access this resource.</p>
</body></html>
Cloudflare state:
If you encounter a 403 error without the Cloudflare branding, this means that the error is being returned directly by the origin web server, not Cloudflare.
https://developers.cloudflare.com/support/troubleshooting/http-status-codes/4xx-client-error/error-403/
I would first take a look at any server firewalls or .htaccess rules etc. that may be preventing services from connecting back into your site. It may be appropriate to speak with your host/admin in case they already know the reason.
Many thanks,
Peter.
Hello. We’ve turned on the option “Use only IPv4 to start scans” and this seems to have fixed it.
Thank-you
Hi @davemspan,
After changing that setting, are you able to confirm whether Wordfence > Tools > Diagnostics > Connecting back to this site is also returning a green “OK” response rather than the server 403 error too?
Thanks again,
Peter.
Hello Peter. We still have the warning, but this warning is for IPV6 and our server does not support IPV6.
Even with “Use only IPv4 to start scans” switched on, I guess no way to hide this?
Thanks
Hi @davemspan,
No, that will show for all customers as that page is largely just for problem-solving and checking settings. With IPv6 becoming more common, the check needs to be there even if many hosts aren’t supporting it fully yet. The message won’t affect operation or show to your users outside of that diagnostics page.
I’m pleased the IPv4 change worked for you, and thanks for keeping me updated.
Thanks,
Peter.
