Loginizer not showing correct IP to blacklist.

  • When IPs come in via cdn, the user IPs don’t show. Only the cdn ip. We have paid for your upgraded version for awhile now and it is becoming a liability. I see the post below me where everyone is locked out. Yes that happens randomly but regularly. Most annoying. But currently the issue is that we use Sitelock for our master security now. They run everything on their cdn and when ips come to us, for example, on Simple History or other IP logging plugins, as two ips. One the cdn IP and the other the user IP. Sometimes they even show 3 IPs by including the VPN. However your app just seems to pick up the cdn IPs that the access attempts come from. So we have it set to auto block IPs that request certain user names. The user IP attempting access does not show, and the cdn IP gets auto blocked and that causes more problems down the line. Especially during a brute force. Hundreds or more of the cdn IPs get blocked and not a single rogue user IP is blocked. Your help is appreciated. Thank you

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor loginizer

    (@loginizer)

    Hi,

    Sorry for the delay in response.

    You can go to Loginizer -> Dashboard under the System Information section check the “Your IP Address” line at the right corner you can use a custom method when using CloudFlare or similar dns provider and choose HTTP_X_FORAWRDED_FOR

    This should resolve your issue.

    Do let us know if you still face the issue.

    Wade

    (@wadedeveloper)

    I am using ‘HTTP_X_FORAWRDED_FOR’, and it is logging the CloudFlare IPs.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Loginizer not showing correct IP to blacklist.’ is closed to new replies.

Tags