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
37 results found
-
Uploading purchased SSL/TLS certificate for domains aliases
Hello,
Please add functionality for uploading purchased certificates for securing domain aliases.
At the moment domain, aliases always use the certificate for the main domain. This is not suitable if different certificates are used for a domain and an alias.
Let's Encrypt certificates can be issued for aliases, but certificates uploading should also be possible.
14 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 -
Redirect to https and only after to www when HSTS and www prefered domain are enabled
Hello, it would be good if Plesk can redirect to https and only after to www when www prefered domain is enabled because when submitting your domain on https://hstspreload.org it gives me this error (I replaced my domain by a fake one obviously)
10 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 -
Add additional CA certificates to an existing certificate
It would be very helpful to be able to add additional CA certificates to existing certificates.
For example, in our case, on a domain with Let's Encrypt, it's required to add origin-pull-ca.pem from Cloudflare (https://support.cloudflare.com/hc/en-us/articles/204899617/) but trying to set sslclientcertificate (Nginx) or SSLCACertificateFile (Apache) as additional directives will trigger an error of duplicate syntax.
Therefore, it should be possible to go to Domains > example.com > SSL/TLS Certificates > Click on the certificate > Add more CA-certs
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 -
webmail subdomain is protected by Let's encrypt for domains but not for alias domains
If I have an ALIAS domain example.com, then
webmail.example.com is created, but there is no certificate for it2 votesThank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IG -
SSL It! Add HSTS preload options for the domain and allow the choice www or non-www domain name
For this extension to be truly useful in regards to adding HSTS to a domain it needs to provide the options necessary to implement it in a way that meets the requirements for preloading.
So it needs to:
1) have an option to add the preload directive.
2) allow for the choice www or non-www domain name by performing the proper redirects to meet the requirements for preloading. Even if it means instructing the client to manually set the "Preferred domain" to "None" as part of the process then having the client return to the extension and then the extension…23 votes -
Allow the use of LetsEncrypt for default certificates
I would like to be able to use the Let's Encrypt extension to add new certs to the "list of certificates in server pool" and make use of a Let's Encrypt (LE) cert as the "default certificate" for domains that have not added their own specific certificate.
I thought this was already possible, but was incorrect. I added a LE cert on the Tools/Settings > SSL/TLS Certificates page, and made it the default certificate.
However, I used a different certificate to secure the Panel and the mail server. It appears, in that case, the LE cert will never be renewed.
…
2 votes -
Add Let's Encrypt Support to Plesk *.domain addresses
The new wildcard SSL support for Let's Encrypt is awesome!
Except that it doesn't work the way a person would expect. For example, when I install a SSL from GoDaddy, I can click my "exampledomain.com" button, and add the SSL. Then I can click my " *.exampledomain.com" button, and add the SSL.
This currently does not work with Let's Encrypt. With LE, I can click into "exampledomain.com" and set up a "*.exampledomain.com " Let's Encrypt SSL. It will properly secure exampledomain.com .
BUT, when I go to the "*.exampledomain.com" in Plesk, and click "Hosting Settings", I cannot select the *.…
16 votes -
Add let's encrypt for webmail.alias
Currently, it is impossible to secure the webmail for the alias.
Please allow the possibility to issue Let's Encrypt SSL for the wbmail of the domain alias.7 votes -
Issue Let's Encrypt Wildcard (and others) certificate without main domain in SAN (use DNS-01 challenge only)
Currently the Let's Encrypt Wildcard requires that main domain would be hosted on the Plesk server, and pass the HTTP-01 challenge as well as DNS-01 for Let's Encrypt.
However for issue the Wildcard Let's encrypt require only DNS-01 challenge.
The HTTP-01 limits the causing the issue since not always the main domain is hosted on the same server as the subdomains.72 votes -
Take *.domain.com as the CN of Wildcard certificates in the LE extension
At the moment the CN of the wildcard certificate is still domain.com and not *.domain.com. The wildcard is just in the alternative domain names.
Please use the wildcard as the CN4 votesThank you for your input. We will consider this functionality in upcoming releases if it is 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.
9 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 -
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!
284 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 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.
25 votesThis is a valid request, for example when a provider does not want to offer free certificates to some customers. 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.
-- PD
-
I would like to be able to acquire SSL certificate of Let's Encrypt for subdomain of www.
I would like to be able to acquire SSL certificate of Let's Encrypt for subdomain of www.
For example
If example.com is another server, SSL certificate of www.example.com can not be acquired by Let's encrypt
I want you to be able to do it.2 votes -
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").9 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.
14 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 -
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)127 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
- Don't see your idea?