Hi wfphil — I’m happy to report the problem has been resolved. Apparently one of our developer’s custom-made cookie plugin was blocking outbound traffic related to privacy policy. Noting to do with the Wordfence plugin or Wordfence Central.
I really appreciate you/your team stepping up to help me solve the problem. I will mark this topic resolved.
Hi wfphil!
Happy to get your response. I have sent the diagnostic report with my username here (russmcclay) and it shows successfully sent. Key point is that only this domain, proqc.com, has the problem. All other sites such as proqc.fr, which are on the same AWS Linux server, are able to connect to Wordfence Central. Also I opened an account on Central and could successfully add proqc.fr, but not proqc.com for the same reason of connectivity between the site and Wordfence.