« Preload flash .flv files into browser cache.htaccess mod_rewrite rewrite examples »
Update: AskApache Password Protect Plugin
Note: A lot of updates to this plugin are in the works, so this plugin should be considered BETA… than them.
Adding .htaccess based HTTP Basic Authentication to your WordPress blog is such a smart thing to do and I’m trying to help make it easier for you. Mainly because it stops alot of automated hacking attempts and exploits from ever being attempted, thus cutting down on the number of requests, connections, and mysql queries for all WordPress blogs on the Internet.
Upgrading Instructions
Just download and extract the new plugin file to wp-content/plugins/askapache-password-protect/ and activate it. It automatically deactivates and deletes previous versions.
Well, this is BETA for now, meaning it works but there are a lot of cool features I just didn’t have time to include in this release. A lot of people were experiencing problems with the older version.
Now hosted by WordPress.org
Current AskApache Password Protection: download | description
Install Problems
Known solutions to all the issues are in the works so prepare for the next release. In the meantime, the problem occurs because this version tries to save the encrypted htpasswd file ABOVE your document_root, obviously this isn’t working very well for most wordpress users.
« Preload flash .flv files into browser cache
.htaccess mod_rewrite rewrite examples »
The love of liberty is the love of others; the love of power is the love of ourselves.
-- William Hazlitt
Please consider donating to support active development of the free software and articles here.![]()
The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect. Tim Berners-Lee
I figured it out… you have to FTP in and make sure all your .htaccess files in your mail /public_html/wp-admin/ is CHMOD 755 and /public_html/.htpasswda1 file is also CHMOD 755
Works for me!
I added the askapache password plugin to my 2.5.2 wordpress blog hosted on Yahoo (never found any warnings in install documentation on Wordpress against this) and now I cannot access my dashboard to remove the plugin (or do anything else on my blog). There are not any .htaccess files or password files that I can see in Yahoo file manager or filezilla. After I installed it and gave user name and password, the first login, it refuses my username and password and I’m locked out of my own blog. How can I fix this, short of blowing everything away and reinstalling Wordpress and my backups?
I installed your password plugin, not cannot get into admin panel. Did all you suggested, but cannot bring up admin… what did I do wrong?
thanks
lauren
I get the error
Warning: Wrong parameter count for sha1() in /public_html/sitename/wp-content/plugins/askapache-password-protect.php on line 532
hi, great idea for a plugin. however, like a lot of the others i read in the comments, i also get a 404 page and can not access the wp-admin directory. nor does it prompt me for a username or password. any fix for this?
it would also be great if you could add something like this to the .htaccess file in the root of the blog directory (seperate from the other wordpress variables:
Options All -Indexes
RewriteEngine On
RewriteBase /
RewriteCond %{THE_REQUEST} /(wp-includes|wp-content)/.*\ HTTP/
RewriteCond %{HTTP_REFERER} !^http://(www\.)yourdomain\.com/.*$ [NC]
RewriteRule .* - [F]
this would exclude people for browsing or direct calling the plugins or template stuff except for the blog software itself. just a thought :)
Same error here Mike and:
Warning: Wrong parameter count for sha1() in /wp-content/plugins/askapache-password-protect/askapache-password-protect.php on line 532
Warning: touch() [function.touch]: Unable to create file /.htpasswdaa1 because Permission denied in /wp-content/plugins/askapache-password-protect/askapache-password-protect.php on line 413
Is it possible to use Windows Live Writer with your plugin?
I am using Wordpress 2.3.3, hosted on my site, which is hosted by hostgator. I am using PHP5. My server details are:
Apache/1.3.37 Server at site Port 80
Yet, when I go to activate this and set the config, it tells me that my server can’t handle the program. I get an error 500.
Can you advise?
I have uploaded the latest version with my updated wordpress install; my server is running php5, and tells me that it is apache, although when I do this:
/phpinfo.php
I get server api: CGI.
Anyway, This will not install, telling me my server’s not good enough… not much I can do about this, since I’m buying host time at hostgator…
I like the idea of this plugin and hope it can be made to work.
Oh, the error it gives me when I try to active is error 500.
Thx
Very nice plugin setup and configuration. It creates the files in the directories. I am using the latest version and WP 2.3.3 on a Linux/Apache hosted server.
However, I am having a similar problem as others on the old version’s comments… 404 Not Found errors when trying to access the wp-admin directory. The comments I read under the old version post didn’t have any answers – that I could find. So, what is the fix for this?
Thank you for your hard work and effort on this plugin.
Never mind – I found the htaccess it wrote in the admin folder, deleted that, and now I’m fine.
Ooookay, I installed this, and now I get a 404 page when I try to access any page in the admin panel. I deleted the plugin AND the test folder it made, and still the problem persists.
wordpress 2.3.3 on apache server.
I have been using version 2.0 of this plug in. I followed your upgrade instructions for 3.1 and have the following errors…
1. Upon activating the new version it did NOT deactivate and delete the previous version. I cleared cache and reloaded plugins page several times and checked via ftp.
2. At control panel of new version I get FATAL ERROR Please disable this plugin but dont delete, updates are on the horizon and a suggestion I use Apache on server (I am)
3. The error logs show the following problems…
PHP Warning: file_exists() [<a href='function.file-exists' rel="nofollow">function.file-exists</a>]: open_basedir restriction in effect. File(/.htpasswdaa1) is not within the allowed path(s): Will this be fixed in the near future? Or what can I do at my end to fix it? Thanks
It's very simple - you read the protocol and write the code. -Bill Joy
HTML | DCMI | GRDDL | XOXO | XDMP | XFN | DOM | XML | XHTML 1.1 Strict | CSS 2.1 | W3C | TLDP | WAI | DISA | ICSI | GIAC | SANS RR | GHOST | DEFCON | NIST | DHS CYBER | NIST | Phrack
↑ TOPExcept where otherwise noted, content on this site is licensed under a Creative Commons Attribution 3.0 License, just credit with a link.
This site is not supported or endorsed by The Apache Software Foundation (ASF). All software and documentation produced by The ASF is licensed. "Apache" is a trademark of The ASF. HTTPD based on NCSA HTTPd
@ Ivan. After having installed the plugin, I couldn’t use the Windows Live Writer any longer. All I got was a “403 forbidden” error. Then I played around with activating and deactivating the security modules in the plugin configuration. Now I know at least one thing for sure: The module “1022 BAD Content Type Denies any POST request with a content type other than application/x-www-form-urlencoded|multipart/form-data” blocks WLW. I deactivated it – now WLW has access to my blog again.