wp-includes: no matching DirectoryIndex

dermotd

• December 13, 2019 16:56

In reviewing my /var/log/apache2/error_log file, I see daily error messages for: [Fri Dec 13 11:33:31.437413 2019] [autoindex:error] [pid 84601] [client x.x.x.x:42504] AH01276: Cannot serve directory /home/client/public_html/wp-includes/css/: No matching DirectoryIndex (index.php,index.php5,index.php4,index.php3,index.perl,index.pl,index.plx,index.ppl,index.cgi,index.jsp,index.jp,index.phtml,index.shtml,index.xhtml,index.html,index.htm,index.wml,Default.html,Default.htm,default.html,default.htm,home.html,home.htm,index.js) found, and server-generated directory index forbidden by Options directive
Following advice from another thread in this forum, I have been creating blank index.html files in the wp-includes/css/ directories, but with ~60 clients on the server I am wondering if there is not a more efficient way of doing this, and resolving this issue? Also, is there any impact to creating a blank (0 bytes) index.html file in the wp-includes/css and wp-content/themes/[active-theme-name]/ directories?

• 

  GOT

  • December 15, 2019 12:44

  The easier route to go would be to disable indexes in that apache config.

  0
• 

  GOT

  • December 15, 2019 12:46

  Actually, disregard, if you are getting that error you should already have indexes disabled. The error in the log is no big deal and can be ignored, I would not go to the trouble of creating blank index files.

  0
• 

  cPanelLauren

  • December 16, 2019 18:32

  The apache documentation may be useful: mod_dir - Apache HTTP Server Version 2.4 As far as generating indexes - there's little impact in doing it but also it may not be extremely useful - the skeleton directory might be useful for having something populated in newly created accounts - Skeleton Directory - Version 84 Documentation - cPanel Documentation

  0

Please sign in to leave a comment.