Apache index html error

Fix Apache Error: No matching DirectoryIndex easily

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:

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.

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:

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.

Источник

Apache не подхватывает index’ную страницу

Собрал Apache 1.3 из исходников под Slackware. По localhost’у пустая страница. Если введу http://localhost/index.html — всё нормально, тестовая страница установки Apache. Как заставить по умолчанию открывать index.html?

AddType application/x-httpd-php .php DirectoryIndex index.php index.html

С PHP-файлами такая же хрень.

Apache не подхватывает index’ную страницу

Apache не подхватывает index’ную страницу

Я пробовал и из IfModule вынимать и в .htaccess писал.

Apache не подхватывает index’ную страницу

А вывод что покажет?
$ apachectl -t -D DUMP_MODULES | grep dir

Apache не подхватывает index’ную страницу

bash-3.1# /usr/sbin/apachectl -t -D DUMP_MODULES | grep dir
bash-3.1#

Apache не подхватывает index’ную страницу

Значит модуль не загружен. Нужно его загрузить или при сборке включить.

Apache не подхватывает index’ную страницу

phpinfo в секции Apache вот что выдаёт:

Loaded Modules mod_bandwidth, mod_evasive, mod_perl, mod_php5, mod_setenvif, mod_so, mod_unique_id, mod_headers, mod_expires, mod_auth, mod_access, mod_rewrite, mod_alias, mod_userdir, mod_actions, mod_asis, mod_cgi, mod_dir, mod_autoindex, mod_include, mod_info, mod_status, mod_negotiation, mod_mime, mod_log_config, mod_env, mod_vhost_alias, http_core

Или это не факт, что все эти модули загружены?

Apache не подхватывает index’ную страницу

> Или это не факт, что все эти модули загружены?
А вот тут уже не знаю. А если так?
$ apachectl -l

Apache не подхватывает index’ную страницу

(205 строка httpd.conf) LoadModule dir_module /usr/lib/httpd/modules/mod_dir.so

# /usr/sbin/apachectl configtest
Syntax error on line 205 of /usr/local/apache/conf/httpd.conf:
module dir_module is built-in and can’t be loaded

Apache не подхватывает index’ную страницу

bash-3.1# /usr/sbin/apachectl -l
usage: /usr/sbin/apachectl (start|stop|restart|fullstatus|status|graceful|configtest|help)

start — start httpd
stop — stop httpd
restart — restart httpd if running by sending a SIGHUP or start if
not running
fullstatus — dump a full status screen; requires lynx and mod_status enabled
status — dump a short status screen; requires lynx and mod_status enabled
graceful — do a graceful restart by sending a SIGUSR1 or start if not running
configtest — do a configuration syntax test
help — this screen

Apache не подхватывает index’ную страницу

поставил конфиг с сервера, где всё нормально работает — те же помидоры.
чувствую, надо будет апачу пересобирать.

Apache не подхватывает index’ную страницу

> module dir_module is built-in and can’t be loaded
Походу модуль вкомпилен намертво, и должен работать. Не понятно что ему не хватает.

Apache не подхватывает index’ную страницу

Попробовал загрузить http://localhost/ links’ом, вот что пишет:

Error loading http://localhost/:
Error reading from socket

Apache не подхватывает index’ную страницу

Проблема решена. Мешался mod_perl. Как только собрал без него — всё заработало.

Apache не подхватывает index’ную страницу

Костыльное какое-то решение.. А сорцы с офсайта качал?

Apache не подхватывает index’ную страницу

Конечно. Вообще мне Perl не нужен был, а тестовый сервак нужно было поднять срочно, по этому не самый худший вариант. На досуге и с перлом разберусь, по крайней мере, ясно куда копать теперь.

Apache не подхватывает index’ную страницу

Я вот прям сейчас ставлю 13 слаку в виртуалку, тоже посмотрю.. Вообще странная фигня, скинь плиз опции —configure, с которыми ты собирал

Apache не подхватывает index’ную страницу

> Собрал Apache 1.3 из исходников под Slackware

Apache не подхватывает index’ную страницу

Сори, не приходят, почему-то, уведомления о новых ответах.

./configure —disable-pdo —enable-bcmath —enable-calendar —enable-exif —enable-ftp —enable-gd-native-ttf —enable-libxml —enable-magic-quotes —enable-mbstring=ru —enable-safe-mode —enable-soap —enable-sockets —enable-wddx —prefix=/usr/local —with-bz2 —with-freetype-dir=/usr/local —with-gd —with-gettext —with-jpeg-dir=/usr/local —with-libexpat-dir=/usr —with-mcrypt=/opt/libmcrypt/ —with-mhash=/opt/mhash/ —with-mime-magic —with-mm=/opt/mm/ —with-mysql=/usr/local/mysql —with-mysql-sock=/tmp/mysql.sock —with-mysqli=/usr/local/mysql/bin/mysql_config —with-png-dir=/usr/local —with-pspell=/opt/aspell —with-ttf —with-xmlrpc —with-xpm-dir=/usr/local —with-zlib —with-zlib-dir=/usr —with-config-file-path=/usr/local/apache/conf —disable-debug —enable-safe-mode —enable-inline-optimization —with-gnu-ld —enable-dba=shared —enable-shmop —enable-sysvsem —enable-sysvshm —enable-sysvmsg

./configure —prefix=/usr/local/apache —bindir=/usr/bin —sbindir=/usr/sbin —sysconfdir=/usr/local/apache/conf —logfiledir=/var/log/apache —datadir=/usr/local/apache/data —localstatedir=/var —runtimedir=/var/run —disable-module=imap —server-uid=www —server-gid=www —activate-module=src/modules/standard/mod_rewrite.c —activate-module=src/modules/standard/mod_vhost_alias.c —enable-module=so —enable-module=rewrite —enable-module=alias —activate-module=src/modules/standard/mod_so.c —activate-module=src/modules/extra/mod_evasive.c —enable-module=evasive —activate-module=src/modules/extra/mod_security.c —enable-module=security —activate-module=src/modules/extra/mod_bandwidth.c —enable-module=bandwidth —activate-module=src/modules/standard/mod_setenvif.c —enable-module=setenvif —activate-module=src/modules/standard/mod_unique_id.c —enable-module=unique_id —activate-module=src/modules/standard/mod_headers.c —enable-module=headers —activate-module=src/modules/standard/mod_expires.c —enable-module=expires —activate-module=src/modules/standard/mod_auth.c —enable-module=auth —activate-module=src/modules/standard/mod_access.c —enable-module=access —activate-module=src/modules/standard/mod_alias.c —enable-module=alias —activate-module=src/modules/standard/mod_userdir.c —enable-module=userdir —activate-module=src/modules/standard/mod_actions.c —enable-module=actions —activate-module=src/modules/standard/mod_asis.c —enable-module=asis —activate-module=src/modules/standard/mod_cgi.c —enable-module=cgi —activate-module=src/modules/standard/mod_dir.c —enable-module=dir —activate-module=src/modules/standard/mod_autoindex.c —enable-module=autoindex —activate-module=src/modules/standard/mod_include.c —enable-module=include —activate-module=src/modules/standard/mod_info.c —enable-module=info —activate-module=src/modules/standard/mod_status.c —enable-module=status —activate-module=src/modules/standard/mod_negotiation.c —enable-module=negotiation —activate-module=src/modules/standard/mod_mime.c —enable-module=mime —activate-module=src/modules/standard/mod_log_config.c —enable-module=log_config —activate-module=src/modules/standard/mod_env.c —enable-module=env —activate-module=src/modules/php5/libphp5.a

Источник

[SOLVED] Apache Error: No matching DirectoryIndex

An Apache error is a message generated by the Apache Web Server software and is usually a result of a coding issue or server misconfiguration. Apache errors may include Internal Server Error or 403 Forbidden messages. They can range from minor, easily fixed errors to more serious ones that may require support from a system administrator. Therefore, understanding the causes of Apache errors helps take the necessary steps to resolve the issue.

This article walks through solving the error: No matching DirectoryIndex (index.html) on CentOS 6 and 7 servers, logged in as root.

General Reason for Apache Error

This error may occur when attempting to access applications that have an index.php file (or another index file), but not an index.html or other specified directory index file. For example, phpMyAdmin includes an index.php file upon installation, but not an index.html file.

Default Apache Configuration

By default, Apache is configured with the following.

This configuration means that Apache will only look for directory index files that are named index.html. So, 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

In this case, we want to add index.php to the DirectoryIndex directive. To do this, access the file from the text editor of your choice. This tutorial uses Vim.

vim /etc/httpd/conf/httpd.conf

DirectoryIndex File Changes

Locate the following configuration information within the configuration file.

Make the following change to the file to add index.php to the directive.

 DirectoryIndex index.html index.php 

Save and Exit the File

Save and exit the file once the appropriate changes are made. For Vim, exit and save the file with the :wq command.

Restart Apache

Restart Apache to implement the changes.

Wrapping Up

Solving the No matching DirectoryIndex Apache error is straightforward with the proper knowledge and understanding of the error’s underlying cause. Following this tutorial ensures the error is rectified easily.

Liquid Web offers managed hosting options to fit small to medium-sized businesses and enterprise workloads. Contact our sales team for a consultation on what best suits your business.

Related Articles:

Источник