> My question is what should the /var/run/php/php7.0-fpm.sock have as
> permission?
It should have rw (read/write) access for whatever user/group nginx is running
under (by default nobody).
Depending on which service (nginx or php-fpm) is running under correct user
either change the nginx conf
Ian thanks very much for your prompt response. I already have been through
the MySQL problems and I'll try your fix on php on Monday. Unfortunately I
had unexpected guests to deal with today hence I only 'just' saw your
message.
Will let you know how I got on.
Posted at Nginx Forum:
https://for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello!
I got confused and no hint(s) about map directive co-exist with
try_files directive. Is it right to think using map directive? Or any
alternative?
The goals is, I want to avoid many location like :
... snip ...
index index.php;
Hi Purvez,
I am going through a similar upgrade, here is what I found necessary (so
far).
1) Swap back from sockets to a normal port. As root, edit
/etc/php/7.0/fpm/pool.d/www.conf
# nano /etc/php/7.0/fpm/pool.d/www.conf
Find listen and change to
listen = 127.0.0.1:9000
listen.al
I had a fully functioning ubuntu 14.04 serving up via nginx a passenger/ror
site with 'some' php.
The passenger/ror bit works fine after the upgrade however any attempt at
accessing my php files gives a 404 Not Found error:
The error.log for nginx shows the following:
===
>From the docs:
yum install gcc-c++ flex bison yajl yajl-devel curl-devel curl GeoIP-devel
doxygen zlib-devel pcre-devel
git clone https://github.com/SpiderLabs/ModSecurity
cd ModSecurity
git checkout -b v3/master origin/v3/master
sh build.sh
git submodule init
git submodule update
On Sat, Apr 22
> It's worth to try libmodsecurity (aka ModSecurity 3.x) + nginx connector
> instead:
> https://github.com/SpiderLabs/ModSecurity/tree/v3/master
> https://github.com/SpiderLabs/ModSecurity-nginx
I'm trying to download/compile libmodsecurity and everything I read concerning
Ubuntu, it instructs
