Hello.
Looking at the changelog I saw this:
"Version 1.30.28
released 11/20/2026
PHP-FPM Selector
Fixed the per-account PHP-FPM pools being lost when a PHP-FPM version is auto-updated to a newer build. On affected servers the PHP-FPM pool directory was left empty, so every site on that PHP version returned 503 (no PHP-FPM socket). The pools are now preserved across a PHP version update, and any server left with empty pools is repaired automatically on the next CWP update (rebuilt from another installed PHP-FPM version and the service restarted)."
Just tonight I had this problem.
Alma10 server with CWP Edge version, has had a php fpm auto update and I have obtained a 503 until I have configured a php fpm socket for that domain and it has been solved.
On another server, Alma10 with CWP LTS, this automatic update also occurred, but at that time, I didn't have any websites running, so I assume it would have also experienced the 503 error.
The difference: On the CWP LTS server, the PHP FPM version was automatically updated, but it retained the values ��I had defined in the php.ini file.
This didn't happen on CWP Edge. It also updated the PHP FPM version, but it didn't retain/update the values ��I had configured in the php.ini file; I had to reconfigure them manually.
Just in case this is helpful.