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

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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!

    216 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    32 comments  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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)

    101 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    17 comments  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  3. Issue Let's Encrypt Wildcard certificate without main domain in SAN

    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.

    26 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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.

    26 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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.

    21 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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…

    17 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  7. Automatically apply wildcard Let's Encrypt SSL

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

    11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    open discussion  ·  1 comment  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  14. Use Lets Encrypt to secure preview urls

    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

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  15. Create CSR with multiple domains

    Currently, Plesk only provides the option to include a single domain on a Certificate Signing Request (CSR): https://support.plesk.com/hc/en-us/articles/213939845

    According to our business needs, we need to issue a CSR with alternative subject names, we need to include multiple domains on this CSR so we can issue a SAN certificate, but Plesk doesn't have such functionality.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add the option to remove certain domain names or its parts from Let's Encrypt certificates auto-renewal notifications

    Add the option to remove certain domain names from Let's Encrypt certificates auto-renewal failure (customer's digest) and Let's Encrypt certificates auto-renewal success (customer's digest).

    For example, I have domain example.com without "www" part (by design) that is secured with Let's Encrypt certificate for example.com (without "www" part). Plesk sends the notification that the www.example.com could not be secured. With the suggested option it will be possible to switch off such notification for "www" part only so that the regular notification for example.com will be active.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  17. Implement a general-purpose ACME client for certificate authorities other than Let's Encrypt

    Currently, it is only possible to automatically renew certificates issued by Let's Encrypt. Certificates from other CA's have to be updated manually even if they support ACME protocol, so it would be useful to have a module that could renew all certificates.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  18. Add ZeroSSL as an alternative to Let's Encrypt

    https://zerossl.com now offers 90 days ssl certificates that work with ACME.

    It would be nice to be able to choose it as a ssl certificates provider in Plesk.

    Probably not too complicated since it relies on same technologies.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  19. Reload Nginx serivice instead of restaring it when reissuing Let's Encrypt certificate

    When reissuing Let's Encrypt certificate for wildcard subdomain(*.example.com) Nginx is restarted, which causes downtime depending on the number of websites. For example, if the server hosts around 4000 domains this can cause 15 seconds downtime for each restart.

    The suggestion is to reload the Nginx service and not to restart it.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base