.htaccess can't find passwd file -- have tried multiple paths

I am trying to setup a secure area on our commercially hosted web site via .htaccess.  The ISP says this is supposed to work, but I have not had success. The .htaccess file is being read because I am being prompted for user name and password.  However, I cannot get into the directory. Error logs say "No such file or directory: Could not open password file: /www/.htpasswd"

As an ISP customer, I do not have access (read or write) to httpd.conf.  When I connect via ftp, my current directory is /www.  In that directory, I have a .htpasswd file. I have a subdirectory 'secureaccess' in www (/www/secureaccess).   In /www/secureacess/ , I have a .htaccess file.

My .htpasswd file is:
joe:encryptedyaddayadda
bob:encryptedwhatever

My .htaccess file is:
AuthType Basic
AuthName "Password Required -- "               
AuthUserFile /www/.htpasswd
require valid-user

I have wide-opened the permissions on .htaccess and .htpasswd and the directory /secureaccess/.

The ISP tech support says that /www is the root that I should use.  (From /www, however, I can cd.. all the way back to:
/usr/local/ft_apache/www ).

I've tried every path I can think of, but am apparently still not seeing the .htpasswd file.

Any suggestions/comments are appreciated

Chuck
jesterepsilonAsked:
Who is Participating?
 
rjdownConnect With a Mentor Commented:
Ho hum...

I'm suprised u can CD all the way back there... it's a bit of a security risk on the part of your ISP :O

But anyway, just to make sure of your location, try this:

Create a file called test.php containing this line of code:

<?php echo $_SERVER['DOCUMENT_ROOT'];?>

And put it in the same directory as your .htpasswd file.

Browse to this file, take the output and stick "/.htpasswd" on the end. That is where it should map to.

Also, make sure there are no blank lines in your .htpasswd file (take extra care at the end of the file) as this screws things up too.

Hope it works out for ya :D
0
 
ahoffmannCommented:
does your AllowOverride contain AuthConfig in httpd.conf?
0
 
jesterepsilonAuthor Commented:
I don't have access to the httpd.conf (the ISP configures this).  The ISP does say that the .htaccess method works, so I assume that means that AllowOverride contains AuthConfig in the httpd.conf.
0
Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

 
ahoffmannCommented:
ok, we assume AuthConfig is set
are you shure that the owner of the httpd can read your files?
is the path to the files correct?
0
 
samriCommented:
hi Chuck,

Try to use

AuthUserFile .htpasswd

and check the error message.  By right by not using absolute path (one with / prefix), the file will be treated as coming from ServerRoot (http://httpd.apache.org/docs-2.0/mod/mod_auth.html#authuserfile).  From there we can figure out how the filesystem layout is made of.

another approach would be asking the ISP on the actual path (since they might be running apache and even ftp in chrooted env - where the path you see is not the path that the OS/apps is seeing.).

Have you tried AuthUSerFile /usr/local/ft_apache/www/.httpasswd ?

Check the permission on www itself.  Makesure it is readable by apache.




0
 
jesterepsilonAuthor Commented:
I know the .htaccess file is being read because it forces a password to get to that directory.  

I've got  /www/.htpasswd for the path which I believe is correct, however it does not work.  I've tried several different paths, but to no avail.
0
 
samriCommented:
hi jesterepsilon,

Based on the error: Error logs say "No such file or directory: Could not open password file: /www/.htpasswd"

it may be possible that apache could not find the file.  try to rename the file to something else (.oldhtpasswd maybe), and check the error. I would think that it would still be the same.

How about the permission on /www?  is it readable by others ?
0
 
jesterepsilonAuthor Commented:
AuthUserFile .htpasswd  returns --    
/usr/local/fp_apache/.htpasswd    
in the error log


AuthUserFile /usr/local/ft_apache/www/.htpasswd returns --
/usr/local/ft_apache/www/.htpasswd
in the error log


AuthUserFile /www/.htpasswd returns --
/www/.htpasswd
in the error log    

Changing the file name  and the reference to it in AuthUserFile returns the same error msg (except with the new file name)
0
 
ahoffmannCommented:
> .. which I believe is correct,
this is not enough.
You need to know it for shure. 100% shure!
Please ask you ISP where and how to write the correct path.
Anything else is guessing ...
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.