Hi @stefanp44, thanks for getting in touch.
If the second error is regarding the IPv6 connectivity, you don’t need to be concerned about that as it occurs when the software on your server (often seen with Cloudflare) assigns an IPv6 address to your site, but your host doesn’t actually give you an IPv6 address.
However, it looks like the first “Connecting back to this site” is also failing so this implies your site can’t connect to our servers and back again. This may be causing problems with rules updates and scans as this connectivity is required.
If you don’t have Cloudflare, it is possible that another firewall associated with your server could be blocking the communication between your site and our servers. Make sure to ask your host if you’re not sure whether that’s the case. If you do have one in place that you’re able to configure, you may need to allow our IPs: https://www.wordfence.com/help/advanced/#servers-and-ip-range
If you do have Cloudflare, you will most likely select “Use the Cloudflare “CF-Connecting-IP” HTTP header to get a visitor IP. Only use if you’re using Cloudflare.” in Wordfence > All Options > General Wordfence Options > How does Wordfence get IPs.
You may also need to update your Cloudflare settings to allow your site to connect back to itself. You should be able to do this by going to your Cloudflare control panel. It’s worth checking all IPs associated with your server first (Find them at Wordfence > Tools > Diagnostics > IP(s) used by this server)
- Login to Cloudflare
- Go to “Firewall”
- Click the “Firewall Rules” tab
- Click “Create a Firewall rule”
- Name the rule under “Rule Name”
- Set the “Field” under “When incoming requests match…” to “IP Source Address”
- Enter your site’s IP address(es) under “Value”
- At the bottom, under “Then…Choose an action” change “Block” to “Allow”
- Click “Deploy
If it seems that you also need to allow our IPs, repeat the same process for the list of IPs given in the link above.
Thanks,
Peter.