Wordfence attempts to post live‑traffic information to noc1.wordfence.com using wp_remote_post. The request ends with cURL error 52, which indicates an empty reply from the remote server. No HTTP headers or body are received, so Wordfence cannot record the traffic data.
The empty reply results from a broken TLS handshake, blocked outbound connection, or mis‑configured proxy. When the server cannot complete the HTTPS request, Wordfence reports the error and stops updating live traffic.