Re: [users@httpd] 403 error upon upgrade

2018-09-30 Thread Frank Gingras
It worked before because you had other DirectoryIndex directives (mostly unaware of that fact). Now, you need DIrectoryIndex index.html index.php or just DirectoryIndex index.php On Sun, Sep 30, 2018 at 4:36 PM Jack M. Nilles wrote: > I don't have an index.html in that directory -- only index.p

Re: [users@httpd] Auto-indexing of directory

2018-09-30 Thread Frank Gingras
The exit signal 31 is a bit odd here. What mpm are you using? What modules are loaded (check with apachectl -M)? How large is that directory? Is it provided via NFS? On Wed, Sep 26, 2018 at 6:32 AM Hemant Chaudhary < hemantdude.chaudh...@gmail.com> wrote: > Hi All, > > I want to see the content o

Re: [users@httpd] 403 error upon upgrade

2018-09-30 Thread Jack M. Nilles
I don't have an index.html in that directory -- only index.php. I suppose I could put in an html file that immediately switches to the php page. That site has always worked before with no index.html file. Why not now? - To uns

Re: [users@httpd] Redirect vhost, with Wordpress

2018-09-30 Thread Frank Gingras
Your first step is to list the current vhosts with either httpd -S or apachectl -S. Edit accordingly. Also, avoid IP:PORT vhost, and use *:PORT when unsure. Pay attention to your logs, especially if you get a 302 or 301. On Sun, Sep 30, 2018 at 2:42 PM Labs Ocozzi wrote: > I did make somethings

Re: [users@httpd] 403 error upon upgrade

2018-09-30 Thread Frank Gingras
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 wrote: > Also, it was not clear as to what exactly was upgraded - the S

RE: [users@httpd] 403 error upon upgrade

2018-09-30 Thread Jerry Martinez
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

RE: [users@httpd] 403 error upon upgrade

2018-09-30 Thread Jerry Martinez
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 P

Re: [users@httpd] Redirect vhost, with Wordpress

2018-09-30 Thread Labs Ocozzi
I did make somethings tests, i think this problem is the enviroment.I did deploy a wordpress in other enviroment and restore database and that website work fine. But i did deploy other wordpress in this enviroment and the new project work fine too. But when i restore the database, my wordpress

Re: [users@httpd] 403 error upon upgrade

2018-09-30 Thread Richard
> Date: Sunday, September 30, 2018 10:44:28 -0700 > From: "Jack M. Nilles" > > 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

Re: [users@httpd] Re: Updating to php 7.0 and having apache still work?

2018-09-30 Thread Jonathon Koyle
Simply to avoid assumptions, did you update php-fpm to 7 as well? On Sun, Sep 30, 2018, 11:01 @lbutlr wrote: > On 29 Sep 2018, at 21:02, Frank Gingras wrote: > > As for the "filter_var" error, you're missing a php extension/module. > > No, I'm not. filter is built in to php and is properly list

Re: [users@httpd] 403 error upon upgrade

2018-09-30 Thread Jack M. Nilles
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 Op

[users@httpd] Re: Updating to php 7.0 and having apache still work?

2018-09-30 Thread @lbutlr
On 29 Sep 2018, at 21:02, Frank Gingras wrote: > As for the "filter_var" error, you're missing a php extension/module. No, I'm not. filter is built in to php and is properly listed in php -m On 30 Sep 2018, at 03:43, Carmel NY wrote: > Add the following to the "/etc/make.conf" file: > >

Re: [users@httpd] Redirect vhost, with Wordpress

2018-09-30 Thread Jonathon Koyle
If you access the server by ip httpd can't differentiate which vhost you are trying to access, so it returns the default. To access a something other than the default you need to include the server name, either as the URL, or maybe you could add it to the request with nginx - before you pass the r

Re: [users@httpd] Updating to php 7.0 and having apache still work?

2018-09-30 Thread Ruben Safir
On 9/30/18 5:43 AM, Carmel NY wrote: > I am running FreeBSD 11.2 p4 / amd64 with php72 install. I upgrade from php56 > as follows. > > First I got a list of all the php56 modules installed > > pkg info -r php56 > php56-modules.txt You can't be sure that scripts that work on PHP65 will work on P

Re: [users@httpd] Updating to php 7.0 and having apache still work?

2018-09-30 Thread Carmel NY
On Fri, 28 Sep 2018 16:12:03 -0600, @lbutlr stated: >Once again I have tried, and failed, to move from php 5.6 to php 7.0 (using >postmaster under FreeBSD 11.3-RELEASE). The results are largely the same, >php pages don’t load either "Primary script unknown” or complaints about >filter(0 (which is