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 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.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

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

    6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  5. Automate DigiCert SSL with ACME API

    Let's Encrypt is a fantastic system. It has changed the landscape of SSL certs to the point that DigiCert now offers an ACME API endpoint1. This is currently a beta feature, but this would be invaluable to hosts and webmasters.

    Consider a world where the only major concern is, is there active funding for the cert? The rest will be handled by the ACME bot of choice. This removes the possibility of the cert not being added or unavailable to browsers.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  9. subdomain creation does not inherit main domain certificate

    When a new sub domain is created it does not inherit the Let's Encrypt certificate issued for the main domain. Domains > subdomain.example.com > Hosting Settings > Certificate shows as None selected.

    If the main domain has the option "Issue a wildcard SSL/TLS certificate" enabled, this certificate could be easily assigned to the new sub domain on creation instead of having to go to subdomain > Hosting settings and selecting it manually.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    14 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  11. Conceptional failures of your SSL It! extension

    Your SSL It! plugin has some conceptional failures:


    1. You provide Mozillas Cipher Suites to adjust the three levels of Mozilla. I'm unsure, if you always then set the additional settings like nginx ssl session caching, but however, Mozillas Suites are not the best. Better is the rating table of Qualys SSL Labs, as that's the grade finally looking for. E.g. Mozillas most secure level requires EC certs, as you don't provide a way to order or install such certs with your normal SSL certificate dialogue (if don't want to order via Let's Encrypt or Encryption Everywhere program), so it's somehow…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    12 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  16. update the Let's Encrypt extension to support DNS challenge, so Plesk users can choose the preferred challenge.

    The Plesk extension uses by default http-01 challenge, which doesn't work when the website is hosted on a private IP address.

    The must be an option to choose the dns-01 challenge as proffered one. This functionality is currently missing :|

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    22 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Web / SSL  ·  Flag idea as inappropriate…  ·  Admin →

    The 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.

← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base