Sometimes Plesk is not accessible with error:
DB query failed: "SET sql_mode = ''" Error: SQLSTATE[08004] [1040] Too many connections

It is possible to inrease the number of connections but it will also be good to have some monitoring of the current number of simultaneous connections to the MySQL, for example in Advanced Monitoring extension.

It will help to prevent Plesk downtime and set the reasonabl limit for max_connections

It is required to import databases created externaly with dbo database schema.

When such database imported in Plesk it is assigned to schema of the database user created in Plesk. When user created in Plesk, new schema is created for database user. For example, user test1 created in Plesk will have database schema "test1"

This results to the non-functional Database due to wrong schema (reuqired dbo, while database imported with schema test1).

The suggestion is to add functionality to select schema when creating database users in Plesk

It would be interesting to be able to have multiple S3-compatible storages configured at a time, so that multiple backup destinations can be used.

More complex random system usernames suggested in the subscription creation process like efsew331 or jk32hlkrj2 for security purposes.

Rounded uis more appealing for eye.

As above.

Currently, it just fails as it tries to create the mail account on the receiving server which already exists on the mail server.

At the least, you could allow migrations to exclude the entire mail domain and then make an account import tool to bring them into the receiving server.

Currently, it is only possible to do via psa database query and subsequent 'plesk bin server_pref --update-web-app-firewall'.

When restoring a Backup of the domain it would be beneficial if you could restore it to a different domain.
There sometimes is the case that data has to be extracted from an old backup, but the current domain state can't be overwritten.

Protect databse from accidental removal, so the database behaves in the same way as the following wordpress_e: greyed out so it cannot be deleted.

Migrator should take into account the database server type (remote or local) and change user permissions accordingly. Currently, users that was set on the source with permissions to connect locally to a local database are migrated to the target with the same permissions, despite the fact, that on the target database server is set as a remote. That leads to inability to connect to remote database for that user on the source after migration and migrator change the permission accordingly.

When setting hard disk quota for domains or subscriptions, allow the user to set limits for drives other than that stored in HTTPDVHOSTSD (e.g.: /dev/sda) such as /dev/sdb, /dev/sda2, etc.

add sprut.io web file manager

solution idea 1. rename the index.php per default to index_.php after mirgration is done rename to index.php

solution idea 2.suspend the domain, i think than its not possibile to access it.

the cron could cause putting stuff in the database while the mirgrations of very large databases is running.

The possibility to set the PostgreSQL Charset from ASC_II to UTF8 during a database creation.

Hello,

There should be an option to read and modify the value of the "Expiration Date" variable on the Plesk subscriptions in the API. That would help a lot.

When any changes are applied to the DNS Settings and when the Slave DNS Manager extension is installed, it would be helpful to add some notifications from the Slave DNS manager in case any issue with syncing zones occur. For example, if changes can not be applied to the Slave server, provide a warning that the service is not working as expected

Same sort of thing as the Route53 extension just with Linode Cloud DNS

Add an ability to access password protected directories from the specific IP addresses without authentication and have authentication for others.