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.
For technical assistance, contact Plesk support
For questions, bug reports, discussions and free assistance, check our Forum and Facebook page
For additional information, see Documentation, Knowledge Base and Blog
Follow us on Twitter for more news on Plesk development
Off-topic posts will be removed from here
-
Add Mailman support to Let's Encrypt
Please add Mailman support to Let's Encrypt.
Ideally, one could issue either a certificate directly for lists.domain.com or a wildcard certificate for *.domain.com.
Furthermore, a secure connection should be enforceable.
Thanks!
158 votesThank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.— rk
-
Let's Encrypt: separate cert for webmail (without main domain in SAN)
We have a setup where webmail.example.com and example.com point to another server than our Plesk instance. Because of this we can't enable Let's Encrypt on Webmail since the CSR contains webmail.example.com and example.com.
So I hope you consider adding an option to only create webmail.example.com (without SAN example.com)44 votesThank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.— rk
-
Allow both HTTP and HTTPS version of websites to be forwarded. It's 2018, this is vital.
This is all about security, it's simply not a fully developed product without this facility and I am hugely shocked and surprised it doesn't already exist.
19 votesThank you for the update! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
IG -
Allow disabling of Let's Encrypt on a domain by domain basis
Currently, when giving users the ability to access SSL to add their own certificates, they can also view Let's Encrypt and create free certificates. It would be useful to allow users access to add their own certificates without giving them access to use Let's Encrypt and there is currently no way to do this.
Additionally, any users logging in to manage their domains can see Let's Encrypt (although cannot use it) and we keep getting asked about it, so it would be useful to hide this off for users unless they specifically need access.
16 votesThank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
IG -
SSL Certificate changes should be reflected in Action Log
SSL Certificate changes are currently not logged in Action Log in any way. Such changes should be logged as they are part of hosting settings.
Yet, they should reflect the certificate details (e.g. "Certificate A was changed to certificate B").5 votesThank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
IG -
Allow certificate upload as .pfx container
If you have a .pfx file containing Certificate, Private Key and CA certificate, allow to upload that container with one step.
This way, a customer doesnt have to use tools like openssl to extract and convert the certificate themselves.
.pfx is the preferred format on windows plattforms ,e.g. when you export a certificate from another IIS-based server.
5 votesThank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
IG -
Option to disable SNI for a domain in SSL Settings
If a domain has SNI disabled from IIS > Site > example.com > Bindings, Plesk reverts it back to Enabled when it pushes changes to IIS.
It would be nice to have an option in the domain's SSL settings to turn ON/OFF SNI and lock it.
4 votesThank you for your input! We will consider this functionality in upcoming releases, if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
IG -
Auto-renew Let's Encrypt certificate when domain is reactivated
When a disabled domain with a Let's Encrypt certificate is re-activated in one of those situations, Plesk should be able to:
Situation A: Domain is reactivated before reaching certificate's expiration date => Do nothing, and renew the certificate aproaching the set date in the cert itself
Situation B: Domain is reactivated after reaching certificate's expiration date => Plesk should re-order or renew the expired certificate
2 votesThank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.—
IG -
Remove 'Secure with an SSL/TLS Certificate' from 'Add a Subdomain'
When adding a subdomain, it takes (at least at my webhoster) 15 min before the changes take effect. If one checked 'Secure the domain with Let's Encrypt' on the page 'Add a Subdomain', an error is thrown because the newly created subdomain is not available in time.
Therefore, I suggest taking this 'feature' off the 'Add a Subdomain' page.
1 voteThe time required for subdomain to become available depends on a many factors. In your particular case it takes a long time, in lot of other cases it works fast. Hoster can configure the server to wait longer, so, the feature can works even in your case.
That’s why we have no plans to remove this.
But anyway, everyone, please continue voting for this feature if you consider it important. If we’ll see a lot of votes for this request, we’ll reconsider it.
-
Option to not select alias domains in Let's Encrypt by default
By default, the Let's Encrypt extension pre-selects all alias domains of a domain to be included in the Let's Encrypt certificate. This can lead to some unwanted results, for example when one of the alias domains is removed from the DNS at a later stage (because it was only used for testing) which would result in Let's Encrypt being unable to renew the certificate.
It would be nice if there was an option that allows us to configure that alias domains should not be selected by default in the Let's Encrypt extension.
1 voteThank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
IG
- Don't see your idea?