• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Restart instead reload?

Vladimir_HosterKZ

New Pleskian
Hi. We have CL + Plesk 12.5 with Apache + Nginx. After any changes on any account, like enable/disable nginx, enable php as fast cgi, etc, all clients see 502 bad gateway nginx.

We see this errors in journal:

http://joxi.ru/KAxz4l1h48Q0ym


This is wrong. Why one client may kill processes of all clients?

What we can do?
 
Interesting :)
Had similar issues recently and wasn't quite sure how to tackle it. Thanks for the link, Igor!
 
Back
Top