Server status error

Hi @lemdeals, thanks for getting in touch.

The IPv6 message shows for some customers as the check needs to be there, but not all hosts are supporting it yet. The message won’t affect operation or show to your users outside of that diagnostics page. You can also check our scan stages documentation for why the yellow triangle may appear under a certain heading.

The wp_remote_post() test will be the biggest blocker for you here. A cURL Error 7 happens at the site and suggests that it can’t connect outwardly to our servers at all. It’s possible that a firewall, service like Cloudflare, or other setting on your server is blocking the connection.

I would certainly still check our connection troubleshooting page in addition to the scan troubleshooting you mention already trying, just in case anything there helps:
https://www.wordfence.com/help/central/connect/#troubleshooting-connection-issues

If you have access to the shell on your server, sometimes running curl -v https://noc1.wordfence.com/ and sending us the output can help. It’s not a perfect check as it bypasses PHP but in many cases can point to the precise cause of the cURL error. Sometimes your host/admin is able to assist with this as they will have the ability to run that command.

Many thanks,
Peter.

Hi @lemdeals, thanks for doing that.

The test result shows a successful connection to https://noc1.wordfence.com/. The key line is HTTP/2 200, which means the server reached Wordfence successfully over HTTPS and received a normal response. Make sure to check:

• Whether the domain resolves correctly on the server
• If any firewall/WAF/ModSecurity/CSF/Imunify rule is blocking self-requests
• and if ports 80/443 are reachable locally from the server itself

This appears to be a loopback connection issue where your site cannot connect to itself, rather than a general outbound connectivity issue to Wordfence. Once your site can connect to itself, that error in diagnostics will clear and scans/extended protection should work as expected.

If you need to add a trusted proxy to correctly detect IPs, or need to allow Wordfence in Cloudflare we have documentation at the following pages:
https://www.wordfence.com/help/dashboard/options/#general-wordfence-options
https://www.wordfence.com/help/advanced/compatibility/#cloudflare-compatibility

Thanks again,
Peter.

Hi @lemdeals,

If IPv6 isn’t supported by your host, it’ll just fall back to IPv4. The error message on the Diagnostics page doesn’t result in any issue provided IPv4 is working.

Thanks again,
Peter.

Hi @lemdeals,

Thanks for your suggestion. I’ll mention it to the development team to see if the label wording, “Not required; this may not be an issue on some sites. Click here to learn whether this is an issue)” can be adjusted for clarity. The result text itself was originally in red, although was changed to orange to reduce its severity level.

Many thanks,
Peter.