MySQL server settings (my.cnf) can only be updated via CLI, it would be faster if these changes could be made in Plesk Panel or PHPMyAdmin without the need to edit settings on server.

Provide the ability to modify sender's name when configuring an auto-reply on Plesk.

At this moment, whenever a WP site is synced, the appearance of an instance at the top of the list is expected in any sort. This was done in order to make it easier to find an instance in the list.

This means the "Sort by" URL mechanism is not being respected, this change is considered a point of improvement to not cause damage to people relying on the "sort by" mechanism to distinguish their instances.

Add the possibility to customize the WordPress Toolkit Set to install WP in a custom directory (e.g., “/wp”) instead of installing it in the root folder (httpdocs)

Reason: The automatic WP installation performed via a WordPress Toolkit Set through a Hosting Plan would work fine if the customer’s current site is not built on WP or another php-based platform, but will fail and mess up their current site if their domain already contains a WP or php-based installation at the root level.

automated logout happens in phpMyAdmin even if i am continuously checking sql commands in phpMyAdmin , the editted sql commands are lost and effort gone waste
logout should happen only in case of the phpMyAdmin console is idle for certain time say half an hour

Will you do support for clearlinux?

As for now, Fail2Ban parses error logs on a domain level. If there are more than 500 domains on the server and the "Piped logs" option is enabled in Apache configuration, it would be more efficient for Fail2Ban to automatically switch to a global Apache log.

Currently the way an IP is chosen from the ip pool allows IPs from alternate interfaces, dedicated IPs, or shared IPs. It would be nice if we had a way to force it to use shared ips for new subscriptions or, just give us a way to set an IP as the default IP for new subscriptions.

Plesk email notifications to the administrator's email address get into Spam folder at public email providers because they are not protected by SPF, DMARC or DKIM anti-spam methods.

It is required to enhance the Plesk notification system so that Plesk email notifications are treated as legitimate email messages by the Internet email system.

Add a possibility to specify Temporary directory for ASP applications outside of the subscription root.

Please develop a "Two-factor verification" option using email and google authentication app or mobile to log in to Plesk for additional security against cyber attacks.

In the UI, at Tools & Settings > Update Settings, it is possible to set a notification to be sent when updates are available or were installed.

In the UI, it is possible to set the notification to be sent either daily or weekly. However, the corresponding CLI option plesk bin notification --update -code adminpumupdates has no option to set the notification frequency. Please add an option to set it via CLI as well.

Help admins and customers to create a security.txt file when creating a site in Plesk Panel, see https://securitytxt.org/
No details yet.

At the moment it is not possible to use the Comodo ruleset with ModSecurity 3.0(Nginx).

Due to this xmlrpc.php brute force for WordPress is not protected, which is allowing Plesk server to be vulnerable to xmrlpc.php attacks

It is required to customize temporary domain names generated by Plesk from subdomain.203.0.113.2.plesk.page to subdomain.203.0.113.2.example.com to have own domain for branding reasons

Please add GUI buttons for common npm scripts in Node.js extension.
For example, implement the buttons to execute "npm start" and "npm build" - this will be helpful in case the application does not have a classic startup file and has to rely on npm scripts

Add the ability to manage the default WordPress Toolkit Security Measures before setting up the instance, e.g. via some options in panel.ini.

I only use Plesk for mail hosting and there is too much junk I do not need. I would love to see an email-focused Plesk version that provides all the necessary tools to have the best email hosting panel and appropriate licence. No WordPress or other server tools. Just focus on email security delivery and management with a special licence.

The problem we are facing is that Plesk's Node.js extension expects an entry point for the app (like app.js) but next.js doesn't work that way.
The expected workflow as explained here (Learn - Deploying a Next.js App | Next.js) is to run the app using npm via the command line using "npm start" after you have built the app and next.js handles the rest internally.