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. 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 →
  2. List SSL expiry in domains list

    List of SSL Expiry date in domains list, and make it sortable so we can target domains with close expiry.

    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

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

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

    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 →
  7. Install Let's Encrypt certificate on domain with forwarding type on Plesk for Windows

    Now when it is possible to install Let's Encrypt on domain It should be possible to install Let's Encrypt certificate on domain with forwarding type on Plesk for Windows too

    3 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 →
  8. SSL It! wildcard + alias issue

    When generating a new Lets Encrypt Certificate with SSL it! , if we check the Wildcard option and also protect an alias, only the alias itself is included in the certificate, but not a wildcard of it.
    For example, we make wildcard of domain.com and also protect alias.com
    The ssl Certificate includes * .domain.com and alias.com. It would be recommended that you protect * .domain.com and * .alias.com

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

    3 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 →
  10. 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.

    3 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. LetsEncrypt confirmation form is very badly designed

    The LetsEncrypt enabling confirmation form is terrible.

    First off, it requires that the user wait for something before they hit Continue, while the Continue button is readly enabled and very prominent. The instruction to wait on DNS change, is described in a tiny final sentence on the form. This is as bad UX as it gets.

    Also, it doesn't describe how the user should check whether the change (adding the TXT record) was completed.

    There's also two Cancel buttons for some reason.

    2 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 →
  12. add posibility to secure webmail with Let's Encrypt certificate for the subdomain with 'No web hosting' type

    The issued certificate should be also available for selecting in Domains > subdomain.name > Mail Settings > SSL/TLS certificate for mail

    2 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 →
  13. 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.

    2 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 →
  14. 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

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

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

    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. Count what certificates are installed on a server

    Add the feature (e.g. CLI utility) to count the certificates that are currently installed on the server with displaying their types and secured components (e.g. wildcard, webmail etc.)

    1 vote

    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. Allow configuring of double redirect

    When in Hosting Settings setting the Preferred Domain to anything but "None" and enabling "Permanent SEO-safe 301 redirect from HTTP to HTTPS" Plesk will redirect every request in one go.

    For example, I configure my domain to redirect HTTP to HTTPS and to prefer the absence of "www". When I now request "http://www.example.com/" it will be redirected to "https://example.com/" in one single redirect. According to the Dutch Web application guidelines the server should first redirect to HTTPS and only then redirect to either include or exclude the www subdomain. (see attachment, taken from https://en.internet.nl/)

    1 vote

    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 →
  19. Enable setting the default (and a custom) max-age value for HSTS in the SSL-IT! plugin

    The Dutch web application guidelines (https://www.ncsc.nl/documenten/publicaties/2019/mei/01/ict-beveiligingsrichtlijnen-voor-webapplicaties) prescribe a minimun max-age of one year (max-age=31536000). The default in the SSL-IT! plugin is 6 months. There is no option for one year, but there is an option for two years.

    I would like to be able to set the default value and add custom values to choose from. I would also very much appreciate to be able to set those through the CLI.

    1 vote

    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 →
  20. Implement the ability to remove the default certificate from newly created domains.

    When creating a default server certificate within "Tools & Settings > SSL/TLS Certificates" it appears for all domains created, even those domains which doesn't match with the server certificate name.

    Implementing a feature at "SSL/TLS Certificates" to avoid displaying the default server certificate for customers within "Domain > example.com > Hosting Settings > Security" can avoid having a customer use a certificate which doesn't match with their domain.

    1 vote

    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 →
  • Don't see your idea?

Feedback and Knowledge Base