I have a customer who is trying to install my php-based script on his dedicated RaQ server. After uploading all the files, when he tries to run setup.php, he gets an Internal Server Error.

According to his error log, the problem is:
DirectoryIndex not alowed here

In the htaccess file, the first line reads:
DirectoryIndex index.php index.html

I have had many many customers successfully install this script without any problems. So I'm certain this is an issue related to this customer's server configuration rather than the script itself.

Can anyone suggest the next step in solving this problem?

Thanks for your help.

Vito

In the virtual host section relating to this client's domain, what is the "Options" setting?

I.e.

# - S O M E D O M A I N . C O M --------------------------------
<VirtualHost *>
ServerAdmin hostmaster@somedomain.com DocumentRoot /usr/home/somedomain/public_html
ServerName www.somedomain.com
ServerAlias *.somedomain.com somedomain.com
CustomLog /usr/home/somedomain/log/httpd-access.log combined
<Directory /usr/home/somedomain/public_html>
Options Indexes
AllowOverride All
</Directory>
</VirtualHost>

If Options doesn't include Indexes for the directory, then AllowOverride will need to be set appropriately (All is not always the right answer!) or they will get an error 500, and in http-error.log you'll see feedback from Apache indicating that they weren't allowed to set that option.

Just check the Apache docs. All very simple.

Make sure AllowOveride is on "ALL" for the server itself.

By default .htaccess usage is switched off on the raq server.

Fron Cobalt Knowledge base:
There is an issue of htaccess files not being recognized on the RaQ4. This is due to the default configuration of the access.conf file and the AllowOverride parameter. The default configuration of the .htaccess files do allow for password protecting directories. The AllowOverride directive is not set to "All" by default because this is a security risk. To change the directive edit the /etc/httpd/conf/access.conf file and replace AllowOverride AuthConfig Indexes Limit to AllowOverride All.

Wow. Talking about quick replies. You guys are pretty cool.

I have emailed my customer directing him to this thread. I am pretty confident he will be able to solve the problem with the information in your replies.

Thanks very much for your help. :)

Vito

My server is a RaQ and the file system is a little different. In the httpd.conf file, there isn't anything that looks like that, well, nothing with <directory> ... </directory>

I'm thinking it may have something to do with the access.conf file?

Cool, I just set AllowOverrid to All and it works :), though I'm afraid this could be a security issue...

You definitely do not need to set it to "All"

In fact, for a performance increase, if a web site has no need for .htaccess config files, turn it to None.

Check out
http://httpd.apache.org/docs/mod/core.html#allowoverride

To permit directory indexes:

AllowOverride Indexes

... is all you need.