• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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