👀 Views: 85 💬 Answers: 1 📅 Created: 2025-06-19

nginx php ubuntu php-fpm 502-bad-gateway PHP

I'm stuck trying to I'm reviewing some code and I'm working with a persistent 502 Bad Gateway behavior while trying to serve a PHP application using Nginx and PHP-FPM on Ubuntu 22.04... The configuration appears to be correct, as I've verified the paths and permissions for both Nginx and PHP-FPM. Here’s what I have in my Nginx configuration file: ```nginx server { listen 80; server_name example.com; root /var/www/html; index index.php index.html index.htm; location / { try_files $uri $uri/ =404; } location ~ \.php$ { include snippets/fastcgi-php.conf; fastcgi_pass unix:/var/run/php/php8.1-fpm.sock; } } ``` I double-checked that the PHP-FPM service is running and listening on the correct socket: ```bash systemctl status php8.1-fpm ``` However, when I make a request to my site, the logs show this behavior: ``` 2023/10/20 14:25:23 [behavior] 12345#12345: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.100, server: example.com, request: "GET /index.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php/php8.1-fpm.sock:" ``` The socket `/var/run/php/php8.1-fpm.sock` does exist, and I confirmed that the user running the Nginx process has permission to access it. Additionally, I restarted both the Nginx and PHP-FPM services after making configuration changes. ```bash sudo systemctl restart nginx sudo systemctl restart php8.1-fpm ``` I've also checked for any other processes that might be interfering with the socket: ```bash lsof | grep php8.1-fpm.sock ``` This returned nothing unusual. I've tried increasing the `listen.backlog` directive in the PHP-FPM pool configuration, but the scenario continues. Does anyone have insights or suggestions on how to resolve this 502 behavior? Any feedback is welcome! I'm working with Php in a Docker container on Ubuntu 22.04. Thanks, I really appreciate it!