Minor quibble. "Your /wp-admin is protected by Apache using .htaccess"

Posted February 20, 2015 4.9k views

I’ve got a wordpress installation and when I log in at the command I get this useful message in the MOTD:

Your /wp-admin is protected by Apache using .htaccess credentials:
User: admin
Pass: <password>

Only, it’s not protected by .htaccess credentials. It’s protected in /etc/apache2/apache2.conf in a <DirectoryMatch ^.*/wp-admin/> directive.

All I’m saying is, there’s five minutes of my life I won’t get back puzzling over that mystery. Fix the message please?

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
3 answers

Thanks for mentioning this. I will pass this along to the person who maintains our Wordpress image so we can update it.

Good post, I guess you may save people 3 minutes when they stumble across this looking for an answer :)

People need to post more stuff like this after they come across odd issues.

I would say though that posting it to the wordpress website or on their bugzilla would be a good thing?

  • The problem isn’t with Wordpress, it’s with the particular way it’s set up on DO.

  • Fair enough :)

    Cant say ive used the DO images. Still. Seems like a potential issue with WP anyway by not giving the most useful of errors.

  • This issue is with our one-click image and not with Wordpress itself. Because we launch a preconfigured droplet that just needs you to set up your admin password and site name, without the password protection when the droplet is first launched it would be easy for anyone to hit this IP address and complete the setup. By adding the password protection to this process it prevents your new Wordpress site from being hijacked before you can complete it’s setup. It’s not an ideal method and we are certainly looking to improve it.

  • IMsupporting, you have misunderstood the problem, twice now. You’re not helping. It’s nothing to do with WordPress at all.

  • Since ryanpq posted, I now understand the issue.

    Sorry, It just sounded like a WP error based on your initial post and confused me ( as I had never used a DO image )

    My statement still stands though. Its handy to have you post this as I’m sure someone else may of come across this and thought.. What?