Helll team. I have the lasted Admin Tools Pro installed, and my site uses CloudFlare.
First, a little bug I discovered in Admin Tools.
Under the configuration, option "Use IP workarounds", the system suggests me to "YES" use it. So I switch it to "YES", save, and then it suggests me to set it to "NO" :-) So I set it to "NO" and the story repeats forever. :) So I think there is something wrong.
Now, on to the point. I believe that the correct setup should be "YES", if I use CloudFlare, am I correct ? I believe that this setting is use to make use of the X-Forwarded-For header used by CloudFlare. Can you please confirm ?
Assuming this is right, then I would need to know what is the correct configuration to be set into Admin Tool's
"WAF" -> "WAF Configuration" -> "Exceptions" -> "Never Block these IPs".
Before setting the "IP Workarounds" to "YES", I had put into that line, the list of IPs belonging to CloudFlare. This is because I knew that all of the IPs that the server would have received (from CloudFlare to Apache to Admin Tools) would have been CloudFlare's IPs. And I didn't want any CloudFlare IP to be blocked.
Now, with the Workarounds set to "YES", my (correct?) understanding is that Admin Tools receives the remote IP, not the CloudFlare. But the config field that I mentioned: "Never Block these IPs" is matched internally to the CloudFlare IPs, or to the remote IPs. In other words, it takes effect AFTER Admin Tools has converted the IPs into Remote ones ?
If the answer is YES, then I think I should take out from that line all of the CloudFlare IPs (because Admin Tool will never consider the CloudFlare IP) and put there the IPs of the remote visitors, like if CloudFlare didn't exist. Am I correct ?
Thanks!
Regards Andrea.
First, a little bug I discovered in Admin Tools.
Under the configuration, option "Use IP workarounds", the system suggests me to "YES" use it. So I switch it to "YES", save, and then it suggests me to set it to "NO" :-) So I set it to "NO" and the story repeats forever. :) So I think there is something wrong.
Now, on to the point. I believe that the correct setup should be "YES", if I use CloudFlare, am I correct ? I believe that this setting is use to make use of the X-Forwarded-For header used by CloudFlare. Can you please confirm ?
Assuming this is right, then I would need to know what is the correct configuration to be set into Admin Tool's
"WAF" -> "WAF Configuration" -> "Exceptions" -> "Never Block these IPs".
Before setting the "IP Workarounds" to "YES", I had put into that line, the list of IPs belonging to CloudFlare. This is because I knew that all of the IPs that the server would have received (from CloudFlare to Apache to Admin Tools) would have been CloudFlare's IPs. And I didn't want any CloudFlare IP to be blocked.
Now, with the Workarounds set to "YES", my (correct?) understanding is that Admin Tools receives the remote IP, not the CloudFlare. But the config field that I mentioned: "Never Block these IPs" is matched internally to the CloudFlare IPs, or to the remote IPs. In other words, it takes effect AFTER Admin Tools has converted the IPs into Remote ones ?
If the answer is YES, then I think I should take out from that line all of the CloudFlare IPs (because Admin Tool will never consider the CloudFlare IP) and put there the IPs of the remote visitors, like if CloudFlare didn't exist. Am I correct ?
Thanks!
Regards Andrea.
https://www.elementotango.it
