Debian12 with nginx and php-fpm

Discussion:

(too old to reply)

Stefano Prina

2024-07-06 14:00:01 UTC

Hello All,

I am Stefano from Torino, Italy;Â I am just new to thisÂ list, nice to
virtually meet all of you : )

I am writing to you because I need support for a strange issue I' am facing.

I am trying to create a debian container to run some php app for a side
project, the idea is to use nginx and php-fpm,

the procedure I am using is :

[host] $ podman run -ti -p 8090:80 debian:12-slim

[container]$apt update && apt install vim nginx php-fpm

edit`/etc/nginx/sites-enabled/default` de-commenting the php part

Â Â Â Â Â Â # pass PHP scripts to FastCGI server
Â Â Â Â Â Â Â #
Â Â Â Â Â Â Â location ~ \.php$ {
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â include snippets/fastcgi-php.conf;

Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â # With php-fpm (or other unix sockets):
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â fastcgi_pass unix:/var/run/php/php8.2-fpm.sock;
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â # With php-cgi (or other tcp sockets):
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â #fastcgi_pass 127.0.0.1:9000;
Â Â Â Â Â Â Â }

[container]$/etc/init.d/nginx start
[container]$ /etc/init.d/php8.2-fpm start

edit`/var/www/html/info.php using the content:`

<?php
phpinfo();
?>

connectinghttp://localhost:8080 I get the default nginx page

connectinghttp://localhost:8080/info.php I got Access denied.

and the logs report :

[container]$ tail -n 2 /var/log/nginx/error.log
2024/07/06 13:19:45 [error] 7365#7365: *1 FastCGI sent in stderr: "PHP
message: PHP Warning: Â PHP Request Startup: Failed to open stream:
Permission denied in Unknown on line 0; Unable to open primary script:
/var/www/html/info.php (Permission denied)" while reading resp
onse header from upstream, client: 127.0.0.1, server: _, request: "GET
/info.php HTTP/1.1", upstream:
"fastcgi://unix:/var/run/php/php8.2-fpm.sock:", host: "localhost:8090"
2024/07/06 13:19:45 [error] 7365#7365: *1 FastCGI sent in stderr: "PHP
message: PHP Warning: Â PHP Request Startup: Failed to open stream:
Permission denied in Unknown on line 0; Unable to open primary script:
/var/www/html/info.php (Permission denied)" while reading resp
onse header from upstream, client: 127.0.0.1, server: _, request: "GET
/info.php HTTP/1.1", upstream:
"fastcgi://unix:/var/run/php/php8.2-fpm.sock:", host: "localhost:8090"

It is strange because I the file /var/www/html/info.php exists and have
to much open permission 0:)

[container]$ls -l /var/www/html/info.php
-rwxrwxrwx 1 root root 20 Jul Â 6 13:03 /var/www/html/info.php

the socket /var/run/php/php8.2-fpm.sock exist and it seems ok:

[container]$ls -l /var/run/php/php8.2-fpm.sock
srw-rw---- 1 www-data www-data 0 Jul Â 6 13:14 /var/run/php/php8.2-fpm.sock

all the workers seem running using the right user:

[container]$ps -aux
USER Â Â Â Â Â Â PID %CPU %MEM Â Â Â VSZ Â Â RSS TTY Â Â Â Â Â STAT START Â Â TIME COMMAND
root Â Â Â Â Â Â Â Â 1 Â 0.0 Â 0.0 Â Â 4188 Â 3216 pts/0 Â Â Â Ss Â Â 12:58 Â Â 0:00 bash
root Â Â Â Â Â 7255 Â 0.0 Â 0.0 201548 Â 8448 ? Â Â Â Â Â Â Â Ss Â Â 13:14 Â Â 0:00
php-fpm: master process (/etc/php/8.2/fpm/php-fpm.conf)
www-data Â 7256 Â 0.0 Â 0.0 201548 10792 ? Â Â Â Â Â Â Â S Â Â Â 13:14 Â Â 0:00
php-fpm: pool www
www-data Â 7257 Â 0.0 Â 0.0 201548 10664 ? Â Â Â Â Â Â Â S Â Â Â 13:14 Â Â 0:00
php-fpm: pool www
root Â Â Â Â Â 7364 Â 0.0 Â 0.0 Â 10336 Â 1512 ? Â Â Â Â Â Â Â Ss Â Â 13:19 Â Â 0:00 nginx:
master process /usr/sbin/nginx
www-data Â 7365 Â 0.0 Â 0.0 Â 10960 Â 4104 ? Â Â Â Â Â Â Â S Â Â Â 13:19 Â Â 0:00 nginx:
worker process
www-data Â 7366 Â 0.0 Â 0.0 Â 10960 Â 4244 ? Â Â Â Â Â Â Â S Â Â Â 13:19 Â Â 0:00 nginx:
worker process
www-data Â 7367 Â 0.0 Â 0.0 Â 10688 Â 2684 ? Â Â Â Â Â Â Â S Â Â Â 13:19 Â Â 0:00 nginx:
worker process
www-data Â 7368 Â 0.0 Â 0.0 Â 10688 Â 2684 ? Â Â Â Â Â Â Â S Â Â Â 13:19 Â Â 0:00 nginx:
worker process
www-data Â 7369 Â 0.0 Â 0.0 Â 10688 Â 2684 ? Â Â Â Â Â Â Â S Â Â Â 13:19 Â Â 0:00 nginx:
worker process
www-data Â 7370 Â 0.0 Â 0.0 Â 10688 Â 2684 ? Â Â Â Â Â Â Â S Â Â Â 13:19 Â Â 0:00 nginx:
worker process
www-data Â 7371 Â 0.0 Â 0.0 Â 10688 Â 2684 ? Â Â Â Â Â Â Â S Â Â Â 13:19 Â Â 0:00 nginx:
worker process
www-data Â 7372 Â 0.0 Â 0.0 Â 10688 Â 2684 ? Â Â Â Â Â Â Â S Â Â Â 13:19 Â Â 0:00 nginx:
worker process
www-data Â 7373 Â 0.0 Â 0.0 Â 10688 Â 2684 ? Â Â Â Â Â Â Â S Â Â Â 13:19 Â Â 0:00 nginx:
worker process
www-data Â 7374 Â 0.0 Â 0.0 Â 10688 Â 2684 ? Â Â Â Â Â Â Â S Â Â Â 13:19 Â Â 0:00 nginx:
worker process
www-data Â 7375 Â 0.0 Â 0.0 Â 10688 Â 2684 ? Â Â Â Â Â Â Â S Â Â Â 13:19 Â Â 0:00 nginx:
worker process
www-data Â 7376 Â 0.0 Â 0.0 Â 10688 Â 2684 ? Â Â Â Â Â Â Â S Â Â Â 13:19 Â Â 0:00 nginx:
worker process
root Â Â Â Â Â 7386 Â 0.0 Â 0.0 Â Â 8060 Â 4248 pts/0 Â Â Â R+ Â Â 13:51 Â Â 0:00 ps -aux

So I have the feeling I am missing something stupid... but what ??

Can you help me ?

Thanks in advance

Stefano

Michael Kjörling

2024-07-06 14:50:01 UTC

Permalink

Post by Stefano Prina
[container]$ tail -n 2 /var/log/nginx/error.log
2024/07/06 13:19:45 [error] 7365#7365: *1 FastCGI sent in stderr: "PHP
/var/www/html/info.php (Permission denied)" while reading resp
onse header from upstream, client: 127.0.0.1, server: _, request: "GET
"fastcgi://unix:/var/run/php/php8.2-fpm.sock:", host: "localhost:8090"
2024/07/06 13:19:45 [error] 7365#7365: *1 FastCGI sent in stderr: "PHP
/var/www/html/info.php (Permission denied)" while reading resp
onse header from upstream, client: 127.0.0.1, server: _, request: "GET
"fastcgi://unix:/var/run/php/php8.2-fpm.sock:", host: "localhost:8090"
It is strange because I the file /var/www/html/info.php exists and have to
much open permission 0:)

I am unable to replicate your results against a VM running a fairly
bare-bones Debian 12 installation. I did however have to do an extra
`systemctl restart nginx.service` within the VM guest for the nginx
web server to recognize info.php as a PHP script that should be
executed, instead of a plain file that should be returned as-is to the
client; simply the old-style /etc/init.d "start" that you show in your
post did not suffice.

I do note that you seem to have a mix of TCP ports here; both 80, 8080
(in the requested URL) and 8090 (in the podman invocation). I would
therefore suggest to double-check your podman invocation to make sure
it is correct for the intended results, and then double-check that you
are requesting the correct URL (primarily host and port) given the
conditions from where you are requesting it. For example, you could
make a change to the default page and check that this change is
reflected in the web browser.

--
Michael Kjörling 🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

Stefano Prina

2024-07-11 10:50:01 UTC

Permalink

Ciao Michael,

Post by Michael KjÃ¶rling
simply the old-style /etc/init.d "start" that you show in your
post did not suffice.
I do note that you seem to have a mix of TCP ports here; both 80, 8080
(in the requested URL) and 8090 (in the podman invocation).

After your email, I double checked and I reported wrongly the port on
the browser url.. of course there were no others containers running a
the host

Anyway I tested the procedure using

* a vm as you did, and I confirm it is working... starting the services
using systemd simply works.

* a vm, stopping the services using the systemd and restarting them
using init.d and it works.

* docker running on a debian host, starting the services using init.d
and it works.

* podman running on a debian host, starting the services using init.d
and it works.

So case close... because the first try was running on a different
distribution, confining all the check to debian do not reproduce the issue.

Thanks for your feedback

Stefano