Make sure that /home/data/site1/htdocs/index.html exists, first. If you want to allow directory listings, then use Options +Indexes (don't mix relative and absolution options).
On Sun, Sep 30, 2018 at 3:14 PM Jerry Martinez <je...@jmweb.net> wrote: > Also, it was not clear as to what exactly was upgraded - the SUSE OS, > Apache > or PHP? I assumed PHP since I experienced issues going from 5 to 7. mod_php > with PHP 5 and ZTS worked fine but everything broke with PHP 7. It turns > out > PHP7 ZTS is broken. Once I transitioned to PHP-FPM, everything worked > flawlessly. > > > Jerry Martinez > Owner & Lead Developer > > JM Web Services, Inc > 786.412.1660 | www.jmweb.net > > > -----Original Message----- > From: Jerry Martinez [mailto:je...@jmweb.net] > Sent: Sunday, September 30, 2018 2:47 PM > To: 'users@httpd.apache.org' > Subject: RE: [users@httpd] 403 error upon upgrade > > I am running PHP 7.2.10 on SUSE Linux Enterprise 12 SP2 via PHP-FPM. I have > a hunch your issues are PHP-FPM related. When PHP5 was working for you were > you running mod_php or PHP-FPM? If your PHP7 install is set to use PHP-FPM, > I do not see anywhere in your config that ties each Apache Vhost to a > PHP-FPM pool. This explains your path issues and PHP unable to parse your > PHP files. > > This is a good resource to follow: https://wiki.apache.org/httpd/PHP-FPM > > > Jerry Martinez > > > -----Original Message----- > From: Richard [mailto:lists-apa...@listmail.innovate.net] > Sent: Sunday, September 30, 2018 2:14 PM > To: users@httpd.apache.org > Subject: Re: [users@httpd] 403 error upon upgrade > > > > > Date: Sunday, September 30, 2018 10:44:28 -0700 > > From: "Jack M. Nilles" <jnil...@jala.com> > > > > Basically the same as before: > > > > [Sun Sep 30 10:29:05.708882 2018] [autoindex:error] [pid 3663] [client > > 220.181.51.119:50416] AH01276: Cannot serve directory > > /home/data/site1/htdocs/: No matching DirectoryIndex > > (index.html,index.html.var) found, and server-generated directory > > index forbidden by Options directive > > The "index.html.var" directoryindex option is part of the (default) global > setting. I would suggest searching your config file(s) for "DirectoryIndex" > to locate all the instance(s) of "index.html.var". > That will help you get a sense of context and what is and isn't being read > as you would expect. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > >
