Skip to content

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

26 results found

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

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    open discussion  ·  IgorG responded

    Thank 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

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

    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  ·  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. Became CA to issue SSL certificates without 3rd party integrations

    You need to make CA like cPanel who own their SSL, less error and not community service.

    It would be nice if Plesk became certificate authority to issue free certificates without 3rd party integrations

    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  ·  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. Separate error log for Let's Encrypt and SSLIt!

    Separate error log for Let's Encrypt and SSLIt! would facilitate panel.log analysis a lot. Now panel.log is flooded with LE and SSLIt errors.

    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  ·  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. 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  ·  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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    open discussion  ·  IgorG responded

    Thank 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

2 Next →
  • Don't see your idea?

Feedback and Knowledge Base