No matching directoryindex ошибка

The “Apache Error: No matching DirectoryIndex easily” error triggers due to missing of the particular index file from DirectoryIndex section in httpd.conf file.

As a part of our Server Management Services, we help our Customers to fix webserver related errors regularly.

Let us today discuss the possible causes and fixes for this error.

What is Apache Error: No matching DirectoryIndex?

The “No matching DirectoryIndex” error occur while accessing applications that have index files other than index.html or other specified ‘directory index’.

For example, phpMyAdmin includes an index.php file upon installation, but not an index.html file.

By default Apache is configured with the following:

DirectoryIndex index.html

Thus Apache will only look for directory index files that has name as index.html. As a result, when attempting to access phpMyAdmin, Apache throws the following error:

[autoindex:error] [pid 20115] [client 10.30.6.80:50800] AH01276: Cannot serve directory /usr/share/phpMyAdmin/: No matching DirectoryIndex (index.html) found, and server-generated directory index forbidden by Options directive

How to fix Apache Error: No matching DirectoryIndex?

The most common reason for this error is the missing of the particular index file from DirectoryIndex section in httpd.conf file. This can be easily fixed by editing the file. For instance, if it is to add index.php to add phpMyAdmin, it can be performed with the setof steps given below:

First step is to open the httpd.conf file with any of the available editors.

vim /etc/httpd/conf/httpd.conf

Now we need to identify the following set of lines in the configuration file.

DirectoryIndex index.html

Next task is to change it to the following format.

DirectoryIndex index.html index.php

Then save and exit the file. Finally, make sure to restart Apache with:

systemctl restart httpd

At times, this error can trigger when the PHP-FPM hits a limit of max allowed processes. We coulld fit it with an increase the value of max allowed processes. For example, in DirectAdmin servers, this can be set to 30 using the commands given below:

/usr/local/directadmin/directadmin set php_fpm_max_children_default 30
cd /usr/local/directadmin/custombuild/
./build rewrite_confs

In plesk environments, after a dist-upgrade, at time a 403 Forbidden is shown on all websites. The apache log shows the “No matching DirectoryIndex” in the apache error log.

To fix the error, enable the dir Apache module going to Tools & Settings > Apache Web Server > Select dir module > Click OK to apply changes

Note to include “IncludeOptional mods-enabled/*.conf” to the /etc/apache2/apache2.conf:

# grep "IncludeOptional mods-enabled/\*\.conf" /etc/apache2/apache2.conf
IncludeOptional mods-enabled/*.conf

[Need any further assistance in fixing Apache errors? – We’re available 24*7]

Conclusion

In short, The “No matching DirectoryIndex” error occur while accessing applications that have index files other than index.html or other specified ‘directory index’. Today, we saw how our Support Engineers fix this error.

It’s the first time I’m trying to deploy my Laravel App on my shared hosting account.

The folder structure is as follows:

|--laravel
  |--app
     |--GoPublic.php // use to point to new location 
  |--bootstrap
  |--config
  |--database
  // more folders 
|--public_html
  |--app // my subdomain document root
     |--assets
     |--index.php // GoPublic.php point to this file

When I go to my subdomain url, I get this:

I’ve checked my error.log file and I get the following 403 forbidden error:

[autoindex:error] [pid 910782] [] AH01276: Cannot serve directory /home/user/public_html/app/: No matching DirectoryIndex (index.php,Index.html,Index.htm,index.html.var,index.htm,index.html,index.shtml,index.xhtml,index.wml,index.perl,index.pl,index.plx,index.ppl,index.cgi,index.jsp,index.js,index.jp,index.php4,index.php3,index.phtml,default.htm,default.html,home.htm,index.php5,Default.html,Default.htm,home.html) found, and server-generated directory index forbidden by Options directive

Hope anyone can help me. Thanks!

How to Resolve the Apache Error: No matching DirectoryIndex?

You might face this error while attempting to access applications that have an index.php file (or other index file), but not an index.html or other specified ‘directory index’ file.

For example, phpMyAdmin comprises of index.php file after installation, but not an index.html file.

Apache is by default configured with the below command:

DirectoryIndex index.html

It means that Apache will only check for the directory files that are named index.html.

While trying to access phpMyAdmin, Apache gives the below error:

[autoindex:error] [pid 20115] [client 10.30.6.80:50800] AH01276: Cannot serve directory /usr/share/phpMyAdmin/: No matching DirectoryIndex (index.html) found, and server-generated directory index forbidden by Options directive

In this case, add index.php to the DirectoryIndex directive.

vim /etc/httpd/conf/httpd.conf

Change the below line:

DirectoryIndex index.html

to:

DirectoryIndex index.html index.php

Now exit and save the file using the command :wq .

Ensure to restart Apache:

systemctl restart httpd

Congratulations! You have now learned to solve the Apache Error: No matching DirectoryIndex.

Also Read
Steps to Modify Apache Directory Listing Style
Learn to Restart Apache on Dedicated Server