Password Protect Directories make mediawiki with 500 error ?

[meeti]

hello,


i install mediawiki on my server,

and i ope the "Password Protect Directories" from cpanel for my public_html.

now,i browser my website and type the name and password for the pop window,

but after that,it shows "internal server error 500".


if i close the "Password Protect Directories" for it,

it will work well,


can anyone teach me how can i colve the problem ?



thanks

[JawadArshad]

hello,


i install mediawiki on my server,

and i ope the "Password Protect Directories" from cpanel for my public_html.

now,i browser my website and type the name and password for the pop window,

but after that,it shows "internal server error 500".


if i close the "Password Protect Directories" for it,

it will work well,


can anyone teach me how can i colve the problem ?



thanks

Check apache logs. Open the URL and enter the login credentials. Don't press enter. Login to your server via SSH and tail the apache error log by using the command below.

tail -f /usr/local/apache/logs/error_log

Then press enter in the browser where you are getting the error. Check logs instantly, they should give you an idea of why you are getting the error. Then you can fix it.

[meeti]

hi,

it shows

[Sun Nov 02 20:25:29 2008] [error] [client *.*.*.*] (13)Permission denied: Could not open password file: /home/tiidii/public_html/_vti_pvt/service.pwd

how can i fix it?


thanks

[JawadArshad]

hi,

it shows


how can i fix it?


thanks

Check the ownership and permissions of the service.pwd file and all the directories before that, service.pwd should be 600 and owned by user.user where user is the cPanel user.

[shacker23]

I've got a similar problem, but have not been able to solve it with any amount of permission inspection / tweaking. This is an .htaccess/htpasswd set up completely by cPanel, not by me... so cPanel seems to be creating htpasswd files that it can't itself read.

My error logs say:
(13)Permission denied: Could not open password file: /path/to/file

[shacker23]

For future generations:

We were able to fix this problem by setting the group ownership of the .htpasswd directory to nobody.