Include memcache and settings for ram etc as standard.

Support varnish cache.
www.varnish-cache.org

I'll like to create a hosting that only use Nginx as webserver. Also I'll like to do this with Node.js, but I think it will not be approved.

For example, Odin uses a system where all the website information is stored inside a NoSQL database, and apache just reads this data with a special module:

http://www.odin.com/products/automation/services-and-applications/shared-hosting-next-generation/

As far as now in Plesk 17.8.9 Beta there are just limited options to configurate Nginx Mircocache.

There is no option to Cache every time.
Even if you de-select all of the "Bypass cache when" Rules your file looks like that.

/var/www/vhosts/system/domain.tld/conf/nginx.conf

[...]
proxy_no_cache $no_cache;
proxy_cache_bypass $no_cache;
[...]

But I want Microcache to Cache even if nocache is set.
Also these values are not configurable:

For Microcache

proxy_cache_valid
proxy_cache_background_update
proxy_cache_ignore_headers
proxy_cache_buffer_size
proxy_cache_buffers
proxy_cache_busy_buffers_size
proxy_cache_temp_file_write_size
proxy_cache_read_timeout
proxy_cache_lock
proxy_cache_methods
proxy_cache_revalidate
proxy_cache_min_uses
proxy_http_version
proxy_set_header

I would love to have some more options to fully configurate Microcache.

Thanks in advance and best regards,
Martin

Currently, Plesk for Linux filters out IPv6 addresses that were assigned dynamically by use of Stateless Address Autoconfiguration, or other means: https://plesk.zendesk.com/hc/en-us/articles/115000239114

This greatly limits IPv6 functionality in Plesk due to the fact that all hyperscalers (Amazon, Google, Azure, Vultr, etc.) provide IPv6 addresses using the autoconfiguration method.

At the moment it is not possible to change or choose the vhost path for a domain. Every Domain is installed in the standard vhost path, at example /var/www/vhosts
If someone has a Server with attached fast and slow storage or big and small storage, it should be possible for the administrator to choose between them when installing a new Domain. It could be possible to give a customer service packages with faster storage for mission critical domains or giving him a lot of space for another domain located on disk drives mounted to another location.

Currently only the Administrators can manage site-aliases with the API.
Why is it not possible for customers to manage site-aliases of their own sites, while they can manage their sites and subscriptions ?
Now I have to use administrator access in the API on a single website, which is a security issue. This website can now manage everything. I would prefer to use the credentials of the customer to manage it.

add HTTP/3

Currently it is not possible to make domain-forwarding for every Domain in an Abonnement. You have to select website-Hosting for the first domain to enable Forwarding for other Domains.

Plesk seems to add up the request response size,
including those of its own extenal IP address.
We would like to disable this behaviour or filter out this info, because
this is not the actual traffic.

We have customers that have a lot of internal requests because of some
caching module where about 50% of the total traffic is from its own IP.

A feature that would allow to install, manage and remove ASP modules such as FileUp in Plesk.

An Nginx restart interval should be helpful for situations when users use API calls to modify domain's PHP settings. This results in multiple nginx reloads:

/var/log/plesk/rc_actions:

INFO: [Tue Feb 26 15:26:00 CET 2019]: Service: nginx, Action: try-reload
INFO: [Tue Feb 26 15:26:44 CET 2019]: Service: nginx, Action: try-reload
INFO: [Tue Feb 26 15:26:59 CET 2019]: Service: nginx, Action: try-reload
INFO: [Tue Feb 26 15:28:06 CET 2019]: Service: nginx, Action: try-reload
INFO: [Tue Feb 26 15:29:11 CET 2019]: Service: nginx, Action: try-reload

A similar functionality exists for apache in Tools & Settings > Apache web server > Restart interval.

For now it is possible to manage specific TLS version and cipher suite only on server level, meaning that particular TLS versopm will be applicable for all domains at once. It would be nice if Plesk introduces the ability to manage TLS version per domain basis, which would add more flexibility for Plesk administrators.

Redirect http://hostname:8443 to https://hostname:8443 on Windows.

Currently only Plesk on Linux can do this.

or provide a way to use nginx-full.

I'd like to make PHP, NGINX, Apache - compiled with maximum support for all extensions
Очень хочется чтоб PHP, NGINX, Apache - были скомпилированы с максимальной поддержкой всех расширений

IIS has CPU management based on Application pools.
It would be great if memory was also controllable.

it would be nice, if you can put little Question Marks between the important words, so that you don´t have to read the whole book with tips.
Over these Question Marks you can hover and than there is a short information about several steps.
Sry for the bad english i am from Germany.