👀 Views: 1457 💬 Answers: 1 📅 Created: 2025-06-24

php nginx php-fpm PHP

I'm writing unit tests and I've encountered a strange issue with I'm relatively new to this, so bear with me... I'm working with a frustrating scenario with my PHP 8.2 application running on Nginx and PHP-FPM. When I try to execute a long-running script, it intermittently returns a 502 Bad Gateway behavior. I've checked the Nginx behavior logs, and I see entries like `connect() failed (111: Connection refused) while connecting to upstream`. I've confirmed that PHP-FPM is running and accessible at the configured socket. Here's a snippet of my Nginx configuration for the site: ```nginx server { listen 80; server_name myapp.local; root /var/www/myapp/public; index index.php index.html index.htm; location / { try_files $uri $uri/ /index.php?$query_string; } location ~ \.php$ { include snippets/fastcgi-php.conf; fastcgi_pass unix:/var/run/php/php8.2-fpm.sock; } } ``` I've also set the `max_execution_time` and `memory_limit` in my `php.ini` to higher values to accommodate longer processes: ```ini max_execution_time = 300 memory_limit = 512M ``` Despite these changes, the script still times out. I've tried increasing the `request_terminate_timeout` in the FPM pool configuration: ```ini ; /etc/php/8.2/fpm/pool.d/www.conf request_terminate_timeout = 300s ``` But I still experience the same behavior. I suspect it might be related to Nginx not waiting long enough for the PHP-FPM response, but I've scoured the documentation and need to find the right directive to increase the timeout in Nginx. Any insights on how to resolve this scenario? What settings should I be checking or adjusting to ensure that long-running PHP scripts execute successfully without hitting the 502 behavior? This is my first time working with Php 3.11. Any pointers in the right direction? My team is using Php for this CLI tool. Any pointers in the right direction? For reference, this is a production service. I'm open to any suggestions.