problem is still coming up intermittently
[Sep 08 20:35:22] Wordfence can't get the IP of clients and therefore can't operate. We received IP: 255.95.96.164. X-Forwarded-For was: 255.95.96.164 REMOTE_ADDR was: 255.95.96.164 Headers that may contain the client IP: HTTP_X_FORWARDED_FOR => 255.95.96.164 HTTP_CF_CONNECTING_IP => 255.95.96.164 HTTP_CF_PSEUDO_IPV4 => 255.95.96.164 SERVER_ADDR => 208.113.145.155 REMOTE_ADDR => 255.95.96.164
[Sep 08 20:35:23] Wordfence can't get the IP of clients and therefore can't operate. We received IP: 255.95.96.164. X-Forwarded-For was: 255.95.96.164 REMOTE_ADDR was: 255.95.96.164 Headers that may contain the client IP: HTTP_X_FORWARDED_FOR => 255.95.96.164 HTTP_CF_CONNECTING_IP => 255.95.96.164 HTTP_CF_PSEUDO_IPV4 => 255.95.96.164 SERVER_ADDR => 208.113.145.155 REMOTE_ADDR => 255.95.96.164
[Sep 08 20:35:23] Wordfence can't get the IP of clients and therefore can't operate. We received IP: 255.95.96.164. X-Forwarded-For was: 255.95.96.164 REMOTE_ADDR was: 255.95.96.164 Headers that may contain the client IP: HTTP_X_FORWARDED_FOR => 255.95.96.164 HTTP_CF_CONNECTING_IP => 255.95.96.164 HTTP_CF_PSEUDO_IPV4 => 255.95.96.164 SERVER_ADDR => 208.113.145.155 REMOTE_ADDR => 255.95.96.164
[Sep 08 20:35:25] Wordfence is receiving IP addresses, but we received an internal IP of 250.97.200.69 so your config may still be incorrect.
[Sep 08 23:10:26] Wordfence can't get the IP of clients and therefore can't operate. We received IP: 255.46.34.232. X-Forwarded-For was: 255.46.34.232 REMOTE_ADDR was: 255.46.34.232 Headers that may contain the client IP: HTTP_X_FORWARDED_FOR => 255.46.34.232 HTTP_CF_CONNECTING_IP => 255.46.34.232 HTTP_CF_PSEUDO_IPV4 => 255.46.34.232 SERVER_ADDR => 208.113.145.155 REMOTE_ADDR => 255.46.34.232
[Sep 08 23:10:27] Wordfence can't get the IP of clients and therefore can't operate. We received IP: 255.46.34.232. X-Forwarded-For was: 255.46.34.232 REMOTE_ADDR was: 255.46.34.232 Headers that may contain the client IP: HTTP_X_FORWARDED_FOR => 255.46.34.232 HTTP_CF_CONNECTING_IP => 255.46.34.232 HTTP_CF_PSEUDO_IPV4 => 255.46.34.232 SERVER_ADDR => 208.113.145.155 REMOTE_ADDR => 255.46.34.232
[Sep 08 23:10:27] Wordfence can't get the IP of clients and therefore can't operate. We received IP: 255.46.34.232. X-Forwarded-For was: 255.46.34.232 REMOTE_ADDR was: 255.46.34.232 Headers that may contain the client IP: HTTP_X_FORWARDED_FOR => 255.46.34.232 HTTP_CF_CONNECTING_IP => 255.46.34.232 HTTP_CF_PSEUDO_IPV4 => 255.46.34.232 SERVER_ADDR => 208.113.145.155 REMOTE_ADDR => 255.46.34.232
[Sep 08 23:10:30] Wordfence is receiving IP addresses, but we received an internal IP of 249.110.56.161 so your config may still be incorrect.
