• Hi,

    I have read a number of threads in this forum about issues where the 127.0.0.1 IP address is incorrectly registered as the users IP and is locked out. I am using a Cloudflare / Cloudways setup, which uses an NGINX server.

    I have configured the plugin following the advice in this forum, with “HTTP_X_REAL_IP” set in the trusted IP origins box. My debug window shows the following:

    REMOTE_ADDR = IP0
    HTTP_CF_CONNECTING_IP = IP0
    HTTP_X_REAL_IP = IP0

    If I used the WordPress login page, it seems to capture the IP address correctly for a failed login attempt.

    However, if I use the Woocommerce login page, which is the default on my site as I use Woocommerce memberships, it is still capturing the 127.0.0.1 IP address instead.

    How do I resolve this?

    Thanks!

    Laurence

    • This topic was modified 4 years, 9 months ago by lozula.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author WPChef

    (@wpchefgadget)

    Hi,

    We’ve tested the plugin with Woocommerce and it works as expected. Most likely the problem is with the Woocommerce membership plugin, but since it is paid, we can’t test it.

    However, your debug information looks weird. All your IPs have the same value which means your server is set up correctly and you don’t even have to use the HTTP_X_REAL_IP header in the plugin’s settings. Is it possible that your REMOTE_ADDR and HTTP_X_REAL_IP are 127.0.0.1? Can you check that?

    Thread Starter lozula

    (@lozula)

    Thanks for the response ?? How would I go about checking that? My public IP is definitely not 127.0.0.1, as that’s just a local address.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Locking out 127.0.0.1 on Woocommerce Login Page Only’ is closed to new replies.