Net core can run applications on windows and linux with a short configurations . Please add support to both OS

I want to upgrade Plesk 18 from Ubuntu 16.04 to Ubuntu 18.04 or 20.04.

As described here: https://support.plesk.com/hc/en-us/articles/360002913773-Ubuntu-18-04-support-in-Plesk

At this moment you can change favicon.ico by replacing /usr/local/psa/admin/htdocs/favicon.ico, however it will be replaced on Plesk update.

It is also not possible to make it permanent using custom theme from Plesk branding guide.

Please make a way to customize favicon.ico on permanent basis

Free version of Enterprise Litespeed, it would be nice to use lsphp+Openlitespeed+LSCache (free) within Plesk.

add the ability to manage auto-reply option Domains > example.com > Mail > Email Addresses > Auto-Reply > Send an automatic response to a unique email address no more than (times a day) via API.

Hello,

Please consider support of CloudLinux 8 on Centos 8 + Plesk.

CloudLinux 8 is ready for production use now:
https://blog.cloudlinux.com/cloudlinux-8-with-4.18-kernel-is-ready-for-production

add HTTP/3

The actual MailQueue status is useless, becaus the "status" of the email isnt viewed. This contains the important information for mails with problems.... Please expand it with the status, like it is done win Webim for example

When the DNS service is not hosted on Plesk, the Let's Encrypt wildcard certificate cannot be renewed automatically. Therefore, please provide us with a way to use our own DNS tools (API or script) to create the TXT record on our side and force the extension SSL It! to finish the issuing by itself.

It would be great to implement in Plesk a new feature.

When there are X failed attempts, in Plesk there should be the possibility to block automatically the access to the customer account (completely or for a certain period of time).

As per now, Plesk block the IP address via Fail2ban, but this is not the feature that we need. We just want to block the access completely or temporarily for the affected login.

It will be good if Plesk can implement automatically applied wildcard let's encrypt option by default.

It would be nice to have ability to prevent client from modifying the number of maxchildren . The permission "Hosting performance settings management " revokes this but it also prevents the user from changing PHP options like execution time and maxvars. But we would like to allow our clients to manage "Performance and security settings" parameters in Plesk.

Plesk Obsidian introduced the Dynamic List View Mode and some of our customers are having problems understanding the new GUI.

It would be very helpful to configure the View Mode at the Service Plan level:
- Disable the possibility to change the View Mode
- Configure a default View Mode

No suggestion, but a critical, urgent, overdue feature request, as described in many "suggestions" since years:
Secure
mail.customerdomain.tld
webmail.customerdomain.tld
with Let´s Encrypt certificate without having to set the DNS A Record for
customerdomain.tld
to the mailserver IP.
And withouth having WAF disabled (SSL It 1.20 is being blocked bei Comodo (free) and Atomic (free) rules, other not tested yet).

Currently Plesk doesn't support customization of MyLittleAdmin settings, and all myLittleAdmin files will be overwritten during package upgrade.
Please add the functionality to support customization of MyLittleAdmin

Hi,

I think the preview urls is a really useful feature, but they have a limitation in which they cannot be secured.

Being able to secure these urls with a wildcard certificate from Lets Encrypt would be hugely beneficial when developing.

An example would be when developing with certain APIs such as HTML5 Geolocation API.

Thanks

In Plesk Onyx, when subscription is created from a service plan, mail service is created in deactivated state.
But when such subscription is created in Plesk Obsidian, it is created without mail service, which makes creating mail addresses impossible without enabling mail service.
Creating mail addresses in this way is crucial for the client, so please add this functionality to Plesk.

Would be good to be able to manage SMTPUFT8 option over Plesk so that it is not reverted after Plesk Updates and also to remove the need to manage this option over the Postfix config directly.

More information:
https://talk.plesk.com/threads/smtputf8-is-required-but-was-not-offered-by-host.351377/
http://www.postfix.org/SMTPUTF8_README.html