• John

    (@garrettlongest)


    I can’t figure out what is going on. I have a new IP address and figured that out after I tried to log in and was locked out. I went into MyPHPAdmin and removed the instances with my new IP from the “_itsec_” tables (lockout, 404, etc.). I also added my new IP to the whitelist row and to the .htaccess file, so all should be good to go… I can access the custom login screen but every time I try to login it says I’ve been logged out after too many attempts, then I redo the whole process mentioned above again and again can access the login page but cannot log in.
    The only way I can log in is to disable iThemes and log in the default way.
    Does anyone have any clue what’s happening?

    BTW: This is on a multisite network and this issue is across all sites. Never had any problems until my IP changed.

Viewing 2 replies - 1 through 2 (of 2 total)
  • … but every time I try to login it says I’ve been logged out after too many attempts,…

    You probably mean to say:

    … but every time I try to login it says I’ve been locked out after too many bad login attempts,…

    It’s hard enough as it is to resolve these type of issues, no need to make it even more difficult with partial/incorrect info ??

    Thread Starter John

    (@garrettlongest)

    It said “You have been locked out due to too many invalid login attempts.” My apologies for not being perfectly clear… (My post was like 4 or 5AM, zzzzzz)

    I did manage to resolve the issue!
    In case anyone else has the same problem, here is what I did:
    – I did everything mentioned above (MyPHPAdmin and .htaccess),
    – disable iThemes by changing the folder name on the server (like remove a hyphen in the name so that it reads “better-wpsecurity”),
    – log in the default way (/wp-login),
    – noticed iThemes had an update available on the plugin page and updated then activated it,
    – made sure all the security settings were the same as before then added my new IP to the whitelist (also made sure that the folder on the server was renamed back to “better-wp-security”,
    – released my username from the lockouts
    – logged out and logged back in using the hidden backend login as before and everything is good to go!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Need to disable iThemes to log in’ is closed to new replies.