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

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

    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)

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

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

    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. 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 →
  8. 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 →
  9. 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
    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. 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
    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. 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 →
  12. 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.

2 Next →
  • Don't see your idea?

Feedback and Knowledge Base