Static IP Address Code Not Blocking Log-in Attempts

  • Resolved newvisionmedia

    (@newvisionmedia)


    10 years, 2 months ago

    Hi,

    Further to my previous post:
    https://ww.wp.xz.cn/support/topic/static-ip-address-code-not-blocking-log-in-attempts?replies=0#post-8217835

    We’ve received an email with the following information:

    A user with IP address 217.67.30.35 has been locked out from the signing in or using the password recovery form for the following reason: Used an invalid username ‘admin’ to try to sign in.
    User IP: 217.67.30.35
    User hostname: dw17.nameserver.sk
    User location: Slovakia

    We’ve since spoken to Wordfence, in which they recommended that we check our Logs, which shows as followed:

    [Tue Apr 05 00:20:05.290665 2016] [ssl:warn] [pid 5769] AH01909: www.appareltruth.org:443:0 server certificate does NOT include an ID which matches the server name
[Tue Apr 05 00:20:06.055976 2016] [ssl:warn] [pid 5771] AH01909: www.appareltruth.org:443:0 server certificate does NOT include an ID which matches the server name
[Tue Apr 05 01:23:54.436270 2016] [access_compat:error] [pid 5845] [client 130.185.155.74:62874] AH01797: client denied by server configuration: /appareltruth.org/public_html/wp-login.php
[Tue Apr 05 04:45:13.797523 2016] [core:error] [pid 14165] [client 159.203.66.34:57055] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace., referer: http://www.netcraft.com/survey/
[Tue Apr 05 04:45:13.802329 2016] [core:error] [pid 14165] [client 159.203.66.34:57055] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace., referer: http://www.netcraft.com/survey/
[Tue Apr 05 17:43:13.251702 2016] [:error] [pid 8312] [client 217.160.166.219:58958] File does not exist: /appareltruth.org/public_html/wp-admin/media-parse-new.php
[Tue Apr 05 17:45:04.850459 2016] [access_compat:error] [pid 8260] [client 195.206.253.146:52911] AH01797: client denied by server configuration: /appareltruth.org/public_html/wp-login.php

    We’re still unaware to why they’re able to access the wp-login page in the first place as we’ve now set up the static server. Are we just not understanding the email correctly?

    Thanks
    Jamie

    https://ww.wp.xz.cn/plugins/bulletproof-security/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author AITpro

    (@aitpro)

    10 years, 2 months ago

    Are you using BPS Login Security? Did the “admin” user account get locked by BPS Login Security? When you go to the BPS Login Security page do you see a locked account for user “admin”?

    If the answer is no for – do you see a locked account for user “admin” then BPS Login Security did not lock the “admin” user account, which means the login attempt for user account “admin” never reached your Login page. That would mean that wordfence is doing something else. What that is I would have no idea and you would have to ask wordfence what they are doing.

    Plugin Author AITpro

    (@aitpro)

    10 years, 2 months ago

    All you need to do to test if your Login page IP address blocking htaccess code that you used in this forum thread: https://ww.wp.xz.cn/support/topic/static-ip-address-code-not-blocking-log-in-attempts?replies=5#post-8219129 is working correctly is to use boomproxy.com Proxy and try to access your login page. You will see that you are not allowed to access your login page and will see a 403 Forbidden message. Whatever else wordfence is doing is something you would have to ask them about.

    Plugin Author AITpro

    (@aitpro)

    10 years, 2 months ago

    Oh I just noticed this in the wordfence email message that you posted: “…Used an invalid username ‘admin’ to try to sign in…”. BPS does not bother checking or locking invalid usernames since that would unnecessarily waste your website and server resources for nothing. If a username does not actually exist/is invalid then there is no point in wasting your website and server resources because only valid usernames can login to a website. So there is no point in doing something dumb like that.

    Thread Starter newvisionmedia

    (@newvisionmedia)

    10 years, 2 months ago

    Thanks for the response.

    I’ve check the Login Security. Login Security is turned on and there is no locked ‘Admin’ login. Therefore on the basis of what you are saying I’m confident BPS is working properly.

    Thanks for taking the time to reply and for such comprehensive support. I really am very grateful.

    In the meantime I will contact Wordfence to discuss and post a reply here for future record (so please don’t close this topic just yet)

    Plugin Author AITpro

    (@aitpro)

    10 years, 2 months ago

    Well resolving this thread would not prevent you from posting any additional information. Since this is a wordfence issue/problem then if you want to be helpful to someone else who uses both BPS and wordfence then you can post a link to the wordfence forum thread topic when wordfence responds to or fixes this problem/issue/bug in wordfence.

    So since this problem/issue/bug is not related to the BPS plugin then I have resolved this thread, but like I said you can post an update to resolved threads at any time.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Static IP Address Code Not Blocking Log-in Attempts’ is closed to new replies.