Feature Suggestions
Please provide here your suggestion for new functionality for Plesk. We encourage you to review and vote for suggestions of others. The top-ranked suggestions are likely to be included in the next versions of Plesk.
Please write in English so that voters from all over the world can read and support your request.
Off-topic posts will be removed from here
3 results found
-
Support for HTTP/2 on apache (without using nginx as proxy)
Hi,
It seems some Plesk users would like to have support for HTTP/2 on apache directly (without using nginx as a proxy).
We do not clearly understand cases when it is required. Why using nginx as a proxy in front of the Apache is not an option? Could you please let us know how this feature should work in terms of workflow, in your opinion? We welcome any feedback and would be happy to receive examples to investigate the question in more detail.4 votesThank you for your idea. Could you tell us which scenarios you want to enable with this functionality?
— AY
-
Adding Let's Encrypt autorenew for ServerAlias in the subdomains (Example: servername.it alias with cert for subdomain.servicename.it)
Need to adding the certificates with Let's Encrypt for the domain names added as serveralias in the apache directives on subdomains, with autorenew system.
3 votesWe are not sure what is meant. At the moment you can set a certificate for the hostname and you can set a certificate for a subdomain. It is also possible to create a subscription that has the same domain name like the hostname, and that subscription can have subdomains all protected by a certificate. It is also possible to have a wildcard certificate for the subscription domain.
Could you please describe in detail what you would like to equip with an SSL certificate and how this is linked to encrypted mail connections as stated in the one existing comment?
-- PD
-
Nginx-only hostings (without Apache component installed on Plesk)
Hi,
It seems some Plesk users would like to have the ability to install Plesk without the Apache component (apache-free, nginx-only setup).
We do not clearly understand cases when it is required. Why using "Nginx-Only Hosting" (https://docs.plesk.com/en-US/obsidian/customer-guide/72320/#nginx-only-hosting) on a per-website base is not an option (which also provides more flexibility)? Could you please let us know how this feature should work in terms of workflow, in your opinion? We welcome any feedback and would be happy to receive examples to investigate the question in more detail.2 votesThank you for your idea. Could you tell us which scenarios you want to enable with this functionality?
— AY
- Don't see your idea?