• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question Error 503 after changing to "FPM application served by..."

tanasis

Regular Pleskian
Server operating system version
AlmaLinux 8.10
Plesk version and microupdate number
Version 18.0.61 Update #5
Hello,
on my webserver I had high traffic websites with PHP as "Dedicated FPM application served by Apache / nginx" and I had high CPU.
I changed 4 of them to "FPM application served by Apache / nginx" (no Dedicated) and then some sites start showing Error 503.
I think to change the PHP-FPM settings globally, I'll have to increase the values.

Where can I find the globally settings in Plesk?

1717615794753.png
 
The only way to raise PHP-FPM children is from Service Plans? How many pm.maxchildren/request apache can he handle?
 
Back
Top