brute force name change locks me out

  • Resolved bodywise

    (@bodywise)


    7 years, 8 months ago

    I know this has been asked in the past. I cannot find the answer

    I have used the brute force secret name to be invaluable. But when WP resides in a sub-directory it locks me out. It is not related to the htaccess file. It is not found in the database. Some other file is changed.

    In some instances I literally had to delete the entire plugin directory and start over again.

    How can I solve this problem. All queries point to the cookies not secret word implementation of brute force protection.

    Again, when implemented this is a huge security gate! Better than anything else.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi, which Brute Force feature are you currently using? Have you tried disabling all of your other plugins except this one and then carrying out a test?

    Thread Starter bodywise

    (@bodywise)

    Thank you but I find this question repeatedly asked without a true explanation.

    I mentioned that I am using secret word not cookie. All your explanations are directed to cookie based.

    I think the problem is related to WP in a subdirectory. What is the solution when locked out? All your soltiuons are simple fixes to repair the site not to solve the problem.

    So … if WP is located in a subdirectory will the brute force secret word work? I think not. It does not affect the htaccess file. There is another solution. I think one other file needs to be changed. Which one? index.php?

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi, yes the Brute Force rename login page works in a subdirectory. I am running 3 sites sub sites with this plugin without any issues.

    Check your .htaccess file and make that it is working correctly and also make sure that this plugin can writ to the .htaccess file.

    Regards

    Thread Starter bodywise

    (@bodywise)

    It is not the htaccess that causes this problem. When you say you are having no problems, fine. It does not solve the problem we have. There is a bug in this program that is not being solved.

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi, sorry to hear you are still having issue. I have submitted a message to the developers to further investigate your issue.

    Kind regards

    Thread Starter bodywise

    (@bodywise)

    Thank you so kindly for this response. It is a bug in the software. It does work on some sites. But the majority of my Amazon web services sites it fails uniformly. For this reason I haven’t given up on this plug-in. The rename login file when operative is bulletproof. I love this plug-in. Otherwise when it does not work it is not worth the effort. So have simply deleted the plug-in. It would be wonderful if we had an answer.

    Virtually all queries and resolutions are relevant to the cookie-based brute force login and not the renaming brute force login. I have also found the cookie-based brute force does not work very well either.

    Thank you very much again

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘brute force name change locks me out’ is closed to new replies.