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. Option to enable or disable automatic issue SSL certificate per domain (instead of per subscription)

    Currently in Plesk a subscription can contain multiple domains. But there is no option to manage which of those domains should be automatically secured with a SSL certificate. There is only the "Keep Websites secured with free SSL/TLS certificates" option for the subscription, which affects all domains inside the subscription.

    This is a suggestion to create an option to be able to manage the "Keep Websites secured with free SSL/TLS certificates" on a per domain basis.

    Use case example:
    When a subscription is used for hosting multiple domains, sometimes some of those domains aren't transferred yet. For example because the…

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Improve RapidSSL order and reissue for many domains

    Hello,

    Please implement a more efficient way to order and reissue RapidSSL certificates for many domains at one.

    It should be possible to order, reissue and install RapidSSL certificates for multiple domains at once without need to provide payment information over and over again.
    Payment information should be stored by Plesk on to automate payment process.

    Reissuing certificates should happen automatically and it should be possible to unsubscribe domains from future reissuing of the certificate.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  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

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
1 3 Next →
  • Don't see your idea?

Feedback and Knowledge Base