Thuan

Thuan
Under review

Hi,

I need to update process_control_timeout from 0 (Off) to 5 seconds.

This is helpful because the PHP FPM reloads every deployment, and running processes will be killed and returned HTTP status 502 Bad gateway immediately.

Allowing the PHP FPM processes to wait at least 5 seconds to complete all running processes before reloading will prevent the error.

I suggest Ploi either:

  • Changes the default process_control_timeout to 5 seconds.
  • Allows editing PHP FPM configuration files at the server Manage tab.
Dennis
Dennis ·
Reply ·

Hey!

But you already can edit the FPM configuration files. Head over to the PHP tab, then per PHP version there's an edit button. You can edit every aspect for PHP configurations there. 💙

Thuan
Thuan Item author · · Edited
Reply ·

Hi,

You allow editing /etc/php/8.3/fpm/php.ini and /etc/php/8.3/cli/php.ini, while process_control_timeout was in /etc/php/8.3/fpm/php-fpm.conf.

Currently, it's still not possible to edit php-fpm.conf in the dashboard.

Glenn
Glenn
Glenn · · Edited
Reply ·

I can confirm this is an issue—I get 502s for a few seconds on every deploy. I think a 5s default would make sense (plus ability to edit).

Thuan
Thuan
Thuan Item author ·
Reply ·

Any updates on this? I upgraded to PHP 8.4 and I have to manually edit the file /etc/php/8.4/fpm/php-fpm.conf for each server.

Log in to comment

502 Bad gateway every deployment: change process_control_timeout in PHP FPM configuration file

2 total votes
Glenn Thuan
Markdown
ChatGPT Claude Perplexity Mistral

  • Dennis moved item to board Under review

    2 years ago

  • Thuan moved item to project Server Level Requests

    2 years ago

  • Thuan created the item

    2 years ago
Quick Actions
Activity
View recent activity and updates
Use arrow keys to navigate