> Date: Tuesday, January 26, 2016 17:24:31 +0100
> From: Weare Borg <kernelfr...@gmail.com>
>
> On Tue, Jan 26, 2016 at 4:57 PM, Richard wrote:
>> 
>> > Date: Tuesday, January 26, 2016 16:51:01 +0100
>> > From: Weare Borg <kernelfr...@gmail.com>
>> > 
>> > On Tue, Jan 26, 2016 at 4:47 PM, Richard wrote:
>> > 
>> >> 
>> >> > Date: Tuesday, January 26, 2016 16:40:23 +0100
>> >> > From: Weare Borg <kernelfr...@gmail.com>
>> >> > 
>> >> > Hi Eric,
>> >> > 
>> >> > Error log :
>> >> > 
>> >> > [Tue Jan 26 16:25:04.015356 2016] [core:notice] [pid 30823]
>> >> > AH00094:
>> >> >> Command line: '/usr/sbin/apache2'
>> >> >> [Tue Jan 26 16:32:14.613618 2016] [autoindex:error] [pid
>> >> >> 30827] [client 127.0.0.1:47452] AH01276: Cannot serve
>> >> >> directory /var/www/html/: No matching DirectoryIndex
>> >> >> (index.html,index.cgi,index.pl,index.php,index.xhtml,index.
>> >> >> htm) found, and server-generated directory index forbidden
>> >> >> by Options directive, referer:
>> >> >> http://localhost/recovery/install/index.php/finish/ [Tue
>> >> >> Jan 26 16:38:02.326241 2016] [autoindex:error] [pid 30828]
>> >> >> [client 127.0.0.1:47716] AH01276: Cannot serve directory
>> >> >> /var/www/html/: No matching DirectoryIndex
>> >> >> (index.html,index.cgi,index.pl,index.php,index.xhtml,index.
>> >> >> htm) found, and server-generated directory index forbidden
>> >> >> by Options directive
>> >> >> 
>> >> > 
>> >> > These are the same name of files on remote-server where we
>> >> > have Apache 2.2, and it's working fine there.
>> >> > 
>> >> > 
>> >> > On Tue, Jan 26, 2016 at 4:21 PM, Eric Covener
>> >> > <cove...@gmail.com> wrote:
>> >> > 
>> >> >> On Tue, Jan 26, 2016 at 10:14 AM, Weare Borg
>> >> >> <kernelfr...@gmail.com> wrote:
>> >> >> > Kindly let me know what I can do to get rid of this
>> >> >> > forbidden message.
>> >> >> 
>> >> >> What does your error log say?
>> >> >> 
>> >> 
>> >> Do you have a file with the name of one of:
>> >> 
>> >>  index.html,index.cgi,index.pl,index.php,index.xhtml,index.htm
>> >> 
>> >> at "/var/www/html/", that is readable by the user that your
>> >> server is running as?
>> >> 
>> >> Note, filenames are case sensitive.
>> >> 
>> > 
>> > No, I don't have the any of the similar files you named. I don't
>> > think so that is needed as other configuration also doesn't have
>> > it, but it runs fine. Here are the files :
>> > 
>> >              bin            config.php       eula_en.txt
>> >              .htaccess media      shopware.php  themes
>> > var
>> > ..            composer.json  CONTRIBUTING.md  eula.txt
>> > license.txt       README.md  style.css      vendor
>> > autoload.php  composer.lock  engine           files
>> > maintenance.html  recovery   templates     UPGRADE.md    web
>> 
>> Read the error message in your log:
>> 
>>  > AH01276: Cannot serve directory
>>  > /var/www/html/: No matching DirectoryIndex
>>  > (index.html,index.cgi,index.pl,index.php,index.xhtml,index.htm)
>> 
>> It's looking for a file with one of those names.
>> 
>> I suspect that some aspect of the configurations of your two
>> systems differ.
>> 
>
> I don't think so, because it is not very complicated to setup, but
> I don't know why I keep getting this error. And as I had pasted
>

The cause of the error is fairly clear. You have a DirectoryIndex
directive that enumerates six "index" filename (extension) options.
If none of those exist, and you have "indexing" turned off, there's
nothing that the server is authorized to serve when you try to enter
a directory without otherwise specifying an existing file.

You might want to go through the same steps/links on both servers
and watch what shows up in the access and error logs. Specifically,
look at the access log on the server where the same action on the
other server gets the forbidden error. Note what the logs indicate
gets served -- that should help you pinpoint what's going on with
your setups.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Reply via email to