• 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.

Input Suggestion: Automatic optimization of MySQL/MariaDB settings

Sven Wappler

New Pleskian
Hello,
my experience is that most of the problems with inaccessible webs on a Plesk system are related to the MySQL server.
Especially on VPS or cloud servers that can be scaled, the MySQL server does not adapt to the requirements. It could use much more RAM, but it doesn't. I had to manually increase the innodb_buffer_pool_size. Also, depending on the grown size, systems can serve a higher number of max_connections. Not doing so results in slow sites and "502 bad gateway" timeouts.
It would be super helpful if Plesk would periodically scan the settings and match them with what is possible. I think this will lead to a much more reliable system for some people.
 
You can vote for this feature request:

 
Back
Top