Trusted WordPress tutorials, when you need them most.
Beginner’s Guide to WordPress
25 Million+
Websites using our plugins
Years of WordPress experience
WordPress tutorials
by experts

How to Password Protect Your WordPress Admin (wp-admin) Directory

Editorial Note: We earn a commission from partner links on WPBeginner. Commissions do not affect our editors' opinions or evaluations. Learn more about Editorial Process.

Do you want to learn how to password-protect your WordPress admin directory?

Adding another layer of password protection to your WordPress admin directory can be a great way to improve your WordPress security.

In this article, you will learn how you can password-protect your wp-admin directory easily.

How to Password Protect Your WordPress Admin (wp-admin) Directory

Why Password Protect Your WordPress Admin Directory?

By password-protecting your WordPress admin directory, you add an extra layer of security to the most important entry point to your WordPress website.

Your WordPress admin dashboard is the central hub of your site. It’s where you’ll publish posts and pages, customize your theme, install WordPress plugins, and more.

Often, when hackers try to get into your website, they’ll do it through the wp-admin screen using a brute force attack.

You can help protect your website against potential attacks by using security measures such as a strong password and limiting login attempts.

To be even more secure, you can also password-protect the wp-admin directory. Then, when someone attempts to access your admin area, they’ll need to enter a username and password before they ever make it to the WordPress login page.

With that said, let’s take a look at how you can password-protect your WordPress admin directory step by step.

The first method is recommended for most users, and you can use the quick links below to jump straight to the method you want to use:

Video Tutorial

Subscribe to WPBeginner

If you’d prefer written instructions, then just keep reading.

Method 1: Password-Protect wp-admin Using Directory Privacy (Recommended)

The easiest way to password-protect your WordPress admin directory is by using your WordPress hosting provider’s Directory Privacy app.

First, you need to log in to your hosting account dashboard and click on the ‘Directory Privacy’ option in the Files section of your website’s cPanel dashboard.

Click on the Directory Privacy option in the Files section

Note: Most web hosts using cPanel, like Bluehost, will have similar steps. However, your dashboard might be slightly different from our screenshots, depending on your hosting provider.

This brings you to a screen that lists all of the different directories on your server. You need to find the folder that contains your website files.

For most website owners, this can be found by clicking on the ‘public_html’ folder.

Click public_html

This brings up all of the website files you’ve installed on your server.

Next, you’ll need to click on the folder with your website’s domain name.

Click domain name folder

In that folder, you’ll see a wp-admin folder.

Instead of clicking the folder name, you’ll need to click the ‘Edit’ button next to that folder.

Click edit wp-admin folder

This brings you to a screen where you can turn on password protection.

Simply check the box that says ‘Password protect this directory’. If you like, you can also give your directory a name like ‘Admin Area’ to help you remember.

Check password protect directory box

Once you’ve done that, you’ll need to click the ‘Save’ button.

This will take you to a page where the confirmation message will appear.

Confirmation message click back button

Now, you’ll need to click the ‘Go Back’ button, and you’ll be taken to a screen where you can create a user that will be able to access this directory.

You will be asked to enter a username and password and then confirm the password. Make sure to note your username and password in a safe place, such as a password manager app.

Create a User

Make sure you click the ‘Save’ button when you’ve done that.

Now, when someone tries to access your wp-admin directory, they will be prompted to enter the username and password you created above.

Password protect WordPress admin example

Method 2: Password-Protect wp-admin Using Code

You can also password-protect your WordPress admin directory manually. To do this, you’ll need to create two files called .htpasswd and .htaccess.

Note: Adding any code to your WordPress site can be dangerous. Even a small mistake can cause major errors on your website. We only recommend this method for advanced users.

Creating the .htaccess File

First, open up your preferred text editor and name the new file .htaccess.

After that, you need to copy the following code snippet and add it to the file:

AuthName "Admins Only"
AuthUserFile /home/user/public_html/
AuthGroupFile /dev/null
AuthType basic
require user yourusername

Make sure you change the ‘AuthUserFile’ path to the location where you’ll upload the .htpasswd file and change ‘yourusername’ to the username you want to use to log in.

Don’t forget to save the file when you are finished.

Creating the .htpasswd File

Once you’ve done that, you need to create a .htpasswd file.

To do this, open up a text editor and create a file called .htpasswd. This file will list your username along with your password in an encrypted format.

The easiest way to generate the encrypted password is with a htpasswd generator.

Simply enter your username and password, select the encryption format, and click the ‘Create .htpasswd file’ button.

Create htpasswd file

The htpasswd generator will display a line of text that you need to paste into your .htpasswd file. Make sure you save the file once you’ve done that.

Uploading .htaccess and .htpasswd to the wp-admin Directory

The last step is to upload both of the files you created to your website’s wp-admin folder.

You will need to connect to your WordPress hosting account using an FTP client or the online file manager tool provided by your hosting provider. For more details, see our beginner’s guide on how to use FTP to upload files to WordPress.

For this tutorial, we will use FileZilla because it’s free and works on both Mac and Windows.

Once you have connected to your website, you will see the files on your computer in the left window and the files on your website on the right. On the left, you need to navigate to the location where you saved the .htaccess and .htpasswd files.

Then, on the right, you need to go to the wp-admin directory for the website you wish to protect. Most users will need to double-click the public_html folder, then the folder with their domain name, then the wp-admin folder.

Now, you can select the two files on the left and click ‘Upload’ from the right-click menu or simply drag the files onto the left window.

Uploading the Files to Your Website's wp-admin Directory

Now, your ‘wp-admin’ directory will be password protected.

Troubleshooting wp-admin Password Protection

Depending on how your server and website are set up, there’s a chance you might run into WordPress errors. These errors can be fixed by carefully adding code to your .htaccess file.

Note: This is the .htaccess file located in your main website folder, not the one you uploaded to the ‘wp-admin’ folder. If you are having trouble finding it, then see our guide on why you can’t find .htaccess and how to locate it.

Fixing the Ajax Not Working Error

One of the most common errors is that Ajax functionality may stop working on the front end of your site. If you have WordPress plugins that require Ajax, such as live Ajax search or Ajax contact forms, then you will notice that these plugins won’t work anymore.

To fix this, simply add the following code to the .htaccess file that’s located in your wp-admin folder:

<Files admin-ajax.php>
    Order allow,deny
    Allow from all
    Satisfy any 

Fixing the 404 Error and Too Many Redirects Error

Two other errors you might run into are the 404 error and the too many redirects error.

The simplest way to fix them is to open up your main .htaccess file located in your website directory and add the following line of code before the WordPress rules:

ErrorDocument 401 default

Bonus: Best WordPress Guides for wp-admin Security

Now that you know how to password-protect your wp-admin directory, you may like to see these guides on making your admin area more secure:

We hope this article helped you learn how to password-protect your WordPress admin (wp-admin) directory. You may also want to see our guide on how to get a free email domain and our expert picks of the best email marketing services for small businesses.

If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

Disclosure: Our content is reader-supported. This means if you click on some of our links, then we may earn a commission. See how WPBeginner is funded, why it matters, and how you can support us. Here's our editorial process.

Editorial Staff

Editorial Staff at WPBeginner is a team of WordPress experts led by Syed Balkhi with over 16 years of experience in WordPress, Web Hosting, eCommerce, SEO, and Marketing. Started in 2009, WPBeginner is now the largest free WordPress resource site in the industry and is often referred to as the Wikipedia for WordPress.

The Ultimate WordPress Toolkit

Get FREE access to our toolkit - a collection of WordPress related products and resources that every professional should have!

Reader Interactions

205 CommentsLeave a Reply

  1. Syed Balkhi says

    Hey WPBeginner readers,
    Did you know you can win exciting prizes by commenting on WPBeginner?
    Every month, our top blog commenters will win HUGE rewards, including premium WordPress plugin licenses and cash prizes.
    You can get more details about the contest from here.
    Start sharing your thoughts below to stand a chance to win!

    • demonkoryu says

      Edit: I see that your problem isn’t with Disqus comments (facepalm), but it might be applicable in your case anyway.

      This happened to me too.
      a) Clear all cookies (for Disqus and the site where you’re trying to use it)
      b) Try another browser than the one you’re currently using

  2. Thomas says

    This isn’t working for me in WordPress 3.9.1. I get a 500 (internal server) error for any admin pages, and the wp-login.php page loads but doesn’t display correctly.

    I’ve added the code for the 404 error to the main .htaccess file, and have added the ajax code to the wp-admin/.htaccess file. No change.

    What might be causing this? Is my server or WordPress install misconfigured somehow?

  3. Abinash Mohanty says

    Hi Syed, Thanks for the tips! I tried with Cpanel method and then added the following .htaccess scripts. The modal pop up window was not working previously and I realized that there was another usename, which was assigned for the same purpose in the past. So what I did was removed all previously assigned usernames and added a new one followed by the new password. The modal popup started working like a charm :) Thanks a lot.

  4. Guest says

    I added the admin-ajax code to my /wp-admin .htaccess file, but that didn’t fix the issue. The All-In-One-Event-Calendar plugin is still not able to access the admin-ajax on the front end.

    Please advise.

    Thank you!

  5. bamajr says

    Wouldn’t adding 2-Step Authentication to the WordPress Admin, login process, resolve this? Say, by using Authy (and their associated plugin)!

  6. Chris Christoff says

    Hi guys,
    Quick note, admin-ajax.php isn’t the only thing that plugins need access to. You also need to allow non-password protected access to async-upload.php and media-upload.php

    These are used by plugins to allow files to be uploaded on the frontend (like uploading a file during a checkout).


  7. Abinash Mohanty says

    Hi Syed Balkhi,
    You made my day! I was getting regular attempts to hack by unknown sources. Thanks for the process, I have fixed mine. It’s better and way easier than wordpress codex :)

  8. Kushal Jayswal says

    Hi I am confused!

    If I lock wp-admin directory then registered authors can access “” in the browser? Or they also need username and password?

    See on my blog anyone can login directly with Facebook, so in such a case if password and username is mandatory for all users. It will be little complex to handle…

    Any comment?

  9. Phil Alcock says

    Thanks for the ajax fix. Added those few lines and it fixed my problem with a plugin. Much easier than the suggestion in the WordPress Codex.

  10. Inayu Mustikayu says

    i follow the manual tutorial and and with 500 error, after trial and error get this work with :
    AuthUserFile /home/yourdirectory/.htpasswds/public_html/wp-admin/passwd
    changed to just
    AuthUserFile /home/yourdirectory/.htpasswds
    in my small tiny ubuntu apache vps :)

  11. aryan says


    i use this password method ,
    please help , because this popup windows not open in UCBrowser !!

    so tell me may i make a page ,html page or any kind of page for login ?? i don’t want to show popup ,i want to show a login in page , and other function as same

  12. Arthur says

    Wow! at last! The “ErrorDocument 401 default” did the trick. I was loosing my patience with the redirect problem….

    Thank you so much for share that.

  13. James says

    Seems to work great except it asks for authentication on our home page not just when accessing wp-admin. Is this possibly another plugin calling a file other than admin-ajax.php?

  14. Jeffro says

    Just wanted to let you know that when I went to manage my subscriptions here on the site via email link, I received the username password prompt. Clicking Cancel allowed me to manage my subscriptions. After selecting and option and clicking save, got the prompt again which clicking cancel also allowed the action to be performed. Just letting you guys know in case you did’nt want that to happen to other people.

  15. Muhammad Ahsan says

    shoud I copy the “ErrorDocument 401 default” line in .htaccess file in /wp-admin/.htaccess file ? or any other .htaccess file ?

  16. pankaj says

    Hi ,
    As you told i i did but when i open wp-admin directory then i got error like “The page isn’t redirecting properly

    Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

    This problem can sometimes be caused by disabling or refusing to accept

    Even in google chrome it doesn’t given popup.Can you tell me how to resolve this issue.

    Thanks in Advance.

  17. Ed Emery says


    This problem has been going since day one last week when I first installed WP. I just did the step by step How to Password Protect Your WordPress Admin (wp-admin) Directory but same problem! Here is a screen shot of what / who / hacker is going on.

    First this:
    The server at WPBeginner Admins Only requires a username and password.

    Warning: This server is requesting that your username and password be sent in an insecure manner (basic authentication without a secure connection).

    Then this after trying to login:

    The server at WordPress attack protection CAPTCHA. Enter username: e7en4d Password: The result of math 16+4 requires a username and password.

    Warning: This server is requesting that your username and password be sent in an insecure manner (basic authentication without a secure connection).

    So how do I stop this as I have tried everything since last Thursday 07-18-2013



  18. David McMahon says

    Many thanks for this helpful hint – I’d been wondering why I kept getting the dreaded “request will never complete” message from Firefox, but now I don’t!

  19. Akash Deep Satpathi says

    Hi! I followed your tutorial with cPanel but after it I was not able to view my Dashboard. It was saying “This webpage has a redirect loop” on Google Chrome. So, what I am missing?

  20. Meher says


    Thank You very much for your article.

    I was trying to add an additional login layer to wp-admin folder and was redirecting to – Too many redirects error -.

    I searched a lot in Google and came across your article. This really helped me solve this issue.

    Thank you once again.

  21. arman says

    it works well

    but there is one problem .

    when normal users Login and wants to go to dashboard and change some info like picture profile they must answer this user password too !!

    is there any chance to set this protected folder for only admin or ignore it for normal users dashboard ?

      • ARMAN says

        So , If i use this for All users , it means all users must have my USer, password for Protected Folder !!

        so anyone can register and Anyone must have this user , password then any hacker can register as User in my site and get this user & pass !!

        So Protecting Wp-admin is useful for only sites with one Admin or with some Special Users to share this user password …

  22. Nishant says

    Thanks for the tips. I have implemented password protection of Wp-Admin directory and also have added double authentication using Google Authenticator. It seems to work fine.

    I recently migrated to a new host (Bluehost) and set up my WordPress site.

    I have installed Wordfence security plugin. The configuration of the plugin is such that every time somebody logs in(including myself), I get an email alert. And also, if somebody attempts a login with an invalid username, then it locks out that IP Address for 10 minutes and sends an email notifying me that there has been a failed attempt to login.

    Considering that I have password protected my Wp-admin directory, unless someone knows the user and and password for it, they cannot reach wp-admin or wp-login to attempt a login to my wordpress.

    But last night I got few emails from Wordfence citing that there have been lock out of few IP Addresses for having made failed attempts to logon to WordPress using invalid usernames (like admin, Admin or nishant). Is it possible to bypass server side password protection of wp-admin directory and make an attempt to logon to WordPress?


    • Nishant says

      Also, I just noticed that…

      When I use the URL directly to wp-login, i am shown the window of server side password for wp-admin directory. But when I click cancel on that password window(2 to 3 times), it displays the wp-login page!

      But when the url is wp-admin, then when clickign cancel it displays “401 Authorization Required
      Invalid login credentials!”

      And the log files showed the invalid attmepts to login were tryign to access wp-login.php directly.

      • Editorial Staff says

        Yes wp-login.php is still accessible. But even if they get the right password, they won’t be able to see it. You can also use the same technique and password protect your wp-login.php file individually.


        • Jeffro says

          Just what exactly would that code be? I didn’t see an easy way to password specific files in Cpanel.

  23. Bart says

    Dear author,

    I am convinced I followed all of your directives, yet still I get the Firefox “endless loop” notification. This is what I did so far:
    – I made a .htpasswds file in /.htpasswds/public_html/wp-admin/passwd (CHMOD 664)
    – I made a .htaccess file with a generated hash / username and put it in /public_html/wp-admin
    – I inserted the line ErrorDocument 401 default before all code into my main .htaccess file in /public_html

    Could you please guide me to solving this problem. My main questions are:

    – you say “make a file called ‘.htpasswds’ “. Is this in fact the correct filename ? I mean, with the s at the end included?
    – exactly what path do I need to specify in my .htaccess file in my /public_html/wp-admin folder? Currently it says “AuthUserFile /.htpasswds/public_html/wp-admin/passwd” I’m not sure I’m doing this part right…

    I’m looking forward to some clarification here…I have been wrestling with this a couple of hours now and I figure it shouldn’t be THAT hard? :-)

    Thank you very much in advance…if you require any more info I’m more than happy to provide it. Kind regards,


    • Editorial Staff says

      What type of hosting are you on? Do you have a cPanel web host? Can you try using the cPanel method to generate the htpswd file?

      It’s really hard to tell what is going wrong because we wrote down the exact same thing that we did on our site.


  24. zimbrul says

    I’d like to ask you guys a question: did it ever happen to you to have admin folder password protected and to be asked for authentication for EVERY post you read on your blog? It does happen with one of my blogs. I was wondering if it’s not better to protect the admin login with Google Authenticator or something similar instead…

    • Editorial Staff says

      If you are being asked to authenticate every single time, then one of the two is happening:

      1. You pasted the .htaccess info in your main .htaccess file and not in the .htaccess file in the /wp-admin/ folder.

      2. admin-ajax.php file is being loaded on the front-end. You need to add the rule to prevent that from being password protected. We have mentioned the fix for that.

      Lastly, yes we have 3 layers of protection for our admin. IP match (if that doesn’t match, then the .htaccess password), and then there is Google Authenticator. We also have limit login attempts activated as well.

      Sucuri also does a pretty good job at blocking other attacks.


  25. Anish K.S says

    i tried this method, but getting an error ” Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects. ”

    How to fix this ???

  26. Mathieu Slaedts says

    Hi there.

    I try to implement this protection. I tried the two solutions (manual and form the admin panel of my host). In both case, the .htacess is in the wp-admin folder, but the pop-up appears on every page.

    Any idea where does that come from ?


    • Editorial Staff says

      That is an unlikely behavior. Without looking at the specific situation, we can’t tell you why it is doing that. We do know that by following this tutorial as it is written, you should be able to make it work. We have it running on WPBeginner.


      • Ollie says

        I just had the same problem with the pop-up appearing on almost every page on my wordpress website.

        It turns out that on the pages where it was showing up, a wp-admin resource, in this case something from a plugin, was being pulled in and that seems to have triggered the pop up. I’ve since disabled the plugin and the password pop up no longer shows up on those pages.

        So, I’d open the source and search for wp-admin to see what’s causing the pop up to appear.

        • Editorial Staff says

          The most common file that is loaded is admin-ajax.php, and we already covered that. If a plugin is loading another file, then yes you have to account for that.

  27. aditya says

    I followed up as you said.
    I protected my wp-admin directory and It’s working for login but the same popup is always coming out while navigating through site ????

    • Editorial Staff says

      This means that you have the code in the wrong .htaccess file. You need to create a brand new .htaccess file in your /wp-admin/ folder. It sounds like that you pasted the code in your main .htaccess file.


  28. 20Music says

    I followed the suggestion found on your site. I created password from cpanel on the wp-admin folder and it done ok for admin login page but on every link that I click in the website, a popup will appear asking for identification. Everything is alright when I clicked cancel.
    Do you know what is the issue with it?

    I used the ErrorDocument 401 default on main .htaccees too.


  29. Ariel says

    I edited my .htaccess root file (to put the errordocument rule), and the pop-up worked well, but all my post links gives me a 404 error. I think that is a rewrite rule problem :( Thanks

  30. Tomy says

    Really helpful info thanks, I just had a breach apparently, 3 files we added to my WordPress install. 1into wp-admin, 1 to wp-admin/images and 1 to wp-includes.
    All were php files. One of them had base 64 encoded crap in it.

    Will setup the htaccess in wp-admin, and limit login attempts plugin seems to provide done nice info.

    Oh I was able to notice the files that were added to my install because WordPress file monitor plugin alerted me.

  31. Mao Shan says


    I followed the suggestion found on the internet on how to secure wp-admin folder. I created a .htacess to password protect the folder. However after implementing it, on every link that I click in the website, a popup will appear asking for identification. Everything is alright when I clicked cancel. Do you know what is the issue with it? I want to secure my wp-admin folder but I don’t want the popup on all pages/links. Currently using Mayashop theme and woocommerce plugin only.


    Below is my sample of .htacess

    Order allow,deny
    Allow from all
    Satisfy any

    Order allow,deny
    Allow from all
    Satisfy any

    Order allow,deny
    Allow from all
    Satisfy any

    AuthType Basic
    AuthName “Admin Only”
    AuthUserFile “(myurl)/.htpasswds/public_html/wp-admin/passwd”
    require valid-user

      • Mao Shan says

        Well the .htaccess file is in wp-admin folder. I changed the theme back to twentyeleven and everything works fine. Only on the other theme, the authorisation required pops out on all pages/links.

        I added below line and everything seems alright but when I got to url/wp-admin, it shows Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects. What is the reason?

        Files ~ “\.(php)$”
        Order allow,deny
        Allow from all
        Satisfy any

        • Mao Shan says

          Hi, I manage to solve it after a clean wordpress install. problem is I am now unable to create contact form as it will direct me to error 404 and when i activate xcloner plugin, it also redirect me to error 404.

          Any help?

  32. Sudeep Acharya says

    I have password protected wp-admin. But inspite of this someone is able to bruteforce on my blog. What may be the possible reason for this?

    • Editorial Staff says

      How do you know that they brute-forced and logged-in to your wp-admin? This sounds really suspicious. Often when this happens, the user has a backdoor in place.


  33. Sudeep Acharya says

    I had got too many redirects loop and just adding this code
    ErrorDocument 401 default

    in .httaccess fixed the problem.

  34. John RIker says

    I use Cpanel and went through how it was to be set up and did that, also the user and passwor.

    However, what I found out after hours of frustration is that the main .htaccess must have this added: ErrorDocument 401 default

    If you add that only to the main .htaccess file it all works. at top before the begin wordpress your world will be much more relaxed. Thats after you set protect directory in cpanel

    Thanks, used you page with a little twiking and its works great.

  35. damian says

    I’m getting so discouraged. My site hacked after only 2 days of being up! The amount of steps needed to take to protect the site is overwhelming, and then they still can get in…

    And every “authority” seems to have a different opinion or approach or favorite plugins… my head is spinning…can you please give a basic numbered run down of steps to take to keep from getting hacked…including cpanel, backend wp, and any other things you might think helpful…and hopefully steps that don’t require an A+ cert….thanks man!

    • Editorial Staff says

      We really apologize for the experience you have had so far. Speaking from this moment, there are no known security issues in the WordPress core. So if you are using the most up to date version of WordPress, then that is good. Often the security issues are with poorly coded plugin and themes. Before you can secure your site, you have to clean it up. Sometimes, changing your passwords and adding all these measures are not enough. Because the hackers can leave backdoor access files which gives them shell access to your server. We highly recommend that you start using Sucuri and have regular backups.

      Make sure to keep your plugins and core files updated at all times. Don’t use plugin/themes from untrusted sources. WordPress has become the Windows of our time. Because there are so many sites using it, hackers have the motivation to find the exploits in plugins, themes etc.

      We will work on creating a comprehensive tutorial on security.


  36. bob says

    I password protected my wp-admin on my sites but I was still getting lockout notices from lilmit login plugin. How could that be?
    I then noticed if I type in /wp-login.php? instead and then cancel I can get to the login page. Uggggh. Makes me wonder what other workarounds there are that I don’t know of.

  37. Peter says

    It appears that a security plugin had added a rewrite to the .htaccess file within wp-admin/ for your account. This was causing the site to redirect to itself causing a redirect loop.

    I have corrected the issue with .htaccess file and your wp-admin login page is loading correctly at this time.

    If you have any other questions or concerns please let us know.

    Preston M.
    Linux Systems Administrator LLC

  38. Peter says

    Had a host gator technician working half an hour on the 404 error issue. He could not resolve it.
    He even removed all rewrite rules in the public_html/.htaccess

  39. Peter says

    Still having “Too many redirects” error
    The page isn’t redirecting properly

    Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

    This problem can sometimes be caused by disabling or refusing to accept

    BUT I added:

    “Redirect 301 /tag/tax/
    Redirect 301 /tag/interest-rate/

    Redirect 301 /tag/chf-flows-floor-ubs/
    Redirect 301 /tag/boom/

    RewriteEngine on
    ErrorDocument 401 default”
    to my .htaccess in the public_html directory.
    (tried also to put “ErrorDocument 401 default” at the start)

  40. Ankur says

    Its a great way to protect wp-admin directory. I was using it for long time but when I installed commentluv, I had to uninstall it as it was not able to work properly.
    Do you happen to know any workaround ?

  41. mindctrl says

    FYI, I’ve seen this break plugins that use ajax on the front end by calling the wp-admin/admin-ajax.php.

    • Editorial Staff says

      Well, you can add a htpasswd. But you would also have to create a .htaccess rule in wp-admin directory to specify that you are locking the directory. Then specify the user or usergroup that is allowed etc. This basically helps us simplify the process.


    • zimbrul says

      The above tutorial is in fact adding security with .htpassword and .htaccess via a user friendly interface in cPanel. After you’ve done the above you’ll notice a .httpassword file has been generated outside your server root (for security reasons) and within the file you’ll find the info you’ve enered as per this tutorial.

  42. Howard says

    On every WP site I have, on my very first login after setup, I create another admin account with a name for which I use a formula to construct — and a very strong, computer-generated password. I then long out, and then login to the alternate admin account, and reduce the standard admin username to “no role for this site” and set a computer-generated password that is at least 35 characters long. I don’t bother to save that password anywhere. It’s now only a honeypot.

    Then I install the “limit login attempts” plugin. Any time that gets tripped, I add the offending IP address to my deny list in .htaccess to make sure that IP can’t reach my site.

    I trap 3 or 4 attempts to break into admin every week.

    • Editorial Staff says

      Yes we had that too. There comes a point when attacks are bouncing IPs. Banning a huge range of IPs is not a sufficient option. We also had login restricted by IP as well, but that didn’t seem to be doing the job either.


      • Howard says

        The “limit login attempts” plugin is pretty good. I have it set to shut off for 100 hours after 4 failed attempts, with the 4th lockout set for 4000 hours. So, even if the perp can dynamically switch IPs, he has to do so every four tries. And with a really long random password, that should take a couple of centuries, and more IP addresses than he is likely to be able to access.

        In the highly unlikely case they crack my “admin” it won’t do them any good anyway. Any time I notice that the scumbag has actually figured out what my real admin name is (only happened once so far), I immediately create a new one, and set the old one to “no role for this site” with a really long randomly-generated password. There are a few other details (e.g., first, I have to change the email address before it will let me create the new admin account with my email), but that pretty much did the trick on that one.

        I really don’t know if this is bulletproof, but I’m hoping the scumbags decide it’s too much work and go pick on a weaker site.

        • zimbrul says

          ” Any time I notice that the scumbag has actually figured out what my real admin name is…” can I ask you how did you figure that?

        • Howard says

          @zimbrul Sure.

          The limit login attempts plugin tells me which user name is under attack. Usually, it’s “admin” but there was one occasion where I saw my real admin account’s name. So I created a new admin account, and left the old one there, but gutted of any access, and with a ridiculously long password.

          I’m not sure how the perp found the admin account since I assigned it an unrelated “nickname” that appears on postings. I’m guessing there is some file on the server that can be at least partially read by a hacker, and I probably need to research that.

        • Editorial Staff says

          Its fairly easy to find the login name. All the person has to do is look at your author URL to know your username. For example this:

          The username would be “wpbeginner”. For most sites that is the case unless ofcourse they have changed the username like shown in this technique:

          If you do it like that, then your username will change, but your author URL would not.

    • zimbrul says

      Howard, that’s an interesting point; I’ll try to implement that.
      Also I had problems with 404 errors or too many redirects and I didn’t know the fix, thanks for that!
      For some reason, banning the IP address in .htaccess in wp-admin folder is not working for my site ! I’ve tried to access my site from my mobile phone on 3G and I could get through even the only allowed IP was the home IP.

Leave a Reply to Ahsan Ali Cancel reply

Thanks for choosing to leave a comment. Please keep in mind that all comments are moderated according to our comment policy, and your email address will NOT be published. Please Do NOT use keywords in the name field. Let's have a personal and meaningful conversation.