The plugin uses a custom method named get_remote_addr to retrieve the IP address from the global server variables, two conditions are involved in the code, the first one checks if the site is being the Sucuri CloudProxy WAF network, and the second condition fixes the loopback address to make it more standard to the format used through the rest of the interface.
If the website is not protected by “CloudProxy” then the plugin uses the address available in _SERVER.REMOTE_ADDR. In the other hand, if the website is behind “CloudProxy” then the plugin takes the address from a custom HTTP header set by the firewall and goes through a list of eight other headers (in other of importance) in case that the previous variable is not available.
You can check which HTTP header is being used to detect your IP address from the “Site Info” page, as well as the IP address of your connection. If you see an inconsistency there then you must ask the support team of your hosting company which HTTP header should be used or which one has more priority, then you can come back to this ticket and I will continue the investigation in case that I need to change something in the code of the plugin to make it work on your site.
OP is unresponsive after two weeks, and this issue may probably be related with this other ticket about “No support for reverse-proxy” [1]. I currently only support the reversion through our firewall, but will add support for other generic proxies in the next version of the plugin.
[1] https://ww.wp.xz.cn/support/topic/no-support-for-reverse-proxy
