Since the connection test worked, the error may have been from a temporary problem at your host, or a side-effect of changing settings. If you can try running a Wordfence scan, and it completes, then it should be ok.
Since you mentioned enabling CloudFlare, can you also check on the Live Traffic page that visitor IP addresses are coming in correctly? You can check if your own IP appears if you visit the site in a second browser where you aren’t currently logged in. It shouldn’t be related to the original issue above, but on some sites, when CloudFlare is active, you may need to change the “How does Wordfence get IPs” option.
If the IP addresses already come through correctly, then there is no need for a change.
-Matt R
Thanks, Matt. I think you’re right that it was just a side-effect of changing settings. About 12 hours after the change, Wordfence did its scheduled scan and the message disappeared, so it may have simply been a slow uptake of the change. Around the time of the scan, I did change the “How does Wordfence get IPs” option over to CloudFlare, which after reading your message may have actually been unnecessary, so I’m not sure if that had anything to do with the message suddenly disappearing or not.
Needless to say, all is working well now and the Wordfence/CloudFlare combo seems pretty great as my site is now super fast! Thanks again for your assistance.
Ok, great! You could try changing “How does Wordfence get IPs” back to the default, and check the Live Traffic page to see if your own IP still comes through when you visit from another browser.
If you use the CloudFlare plugin for WordPress or if your host has “mod_cloudflare” installed, then the default option is better, as long as the IP addresses are showing up properly on the Live Traffic page.
Thanks for following up!
-Matt R
Awesome. I just changed it back to the default setting and it’s working perfectly. Thanks, Matt!
