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

4 results found

  1. DNS Authorisation for Let's Encrypt

    Described in https://tools.ietf.org/html/draft-ietf-acme-acme-06#section-8.4

    The problems with mail/webmail/lists subdomains could be obsolete, because a acmechallenge.lists.domain.tld txt record could be challenged.
    So no problems with webroots etc.

    24 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  ·  Extensions  ·  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. The ability to clone WordPress multisite

    WordPress Toolkit Clone feature also available for in supports WordPress multisite.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    In WP Multisite installations you have one single WP controlling many different websites and domains. "Cloning" a multisite installation seems to be a challenge, because when you clone a site, you need to mention a target where to clone the site to (a new URL, a new subdomain). As a multisite installation has many URLs, it seems impossible to clone these to one single domain. It will be unclear which domain is actually cloned or how to map source to target.

    But as always, we're open for ideas and would love to hear more details from you how you imagine the workflow. Please describe in your comments what you expect to happen when you clone a multisite installation, e.g. how you'd want to map source to target(s). Would you for example want to see a dialog where you can enter new domains and subdomains for each existing URL in the…

  3. Protect mail domain name option

    It would be very desirable for Plesk to have an option, besides the "include www.domain.name" and "Secure webmail.domain.name" options to "Include mail.domain.name" on issuing a Let's Encrypt SSL certificate. If the DNS service is hosted on a 3rd-party service, the mail.domain.name is not secured and the wildcard certificate will not be automatically 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  ·  Extensions  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Is this feature request the same?

    https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/36137434-issue-let-s-encrypt-wildcard-certificate-without-m

    We understand that an option to include mail.domain.tld shall be added when issueing LE certificates. However, a domain-validated certificate requires that the domain that such a DV cert protects is on the host that the DV cert protects. When your mail.domain.tld is hosted elsewhere, it cannot be included in a cert. Instead, a matching cert needs to be created and installed on the external host where mail.domain.tld is operated.

    As you mention a "wildcard" certificate: It is not possible (by LE) to exclude some subdomains from a wildcard cert. A wildcard always protects all.

    For that reason we are having difficulties understanding this feature request correctly. Please rephrase the request or provide more details what exactly is requested and why you believe that this makes sense?

    -- PD

  4. Improve support for third-party app extensions (particularly WordPress)

    At the moment, many third-party app extensions for apps in Plesk like WordPress are not supported without a significant amount of server dependencies being installed. At present, this is not possible to do from within Plesk and requires direct access to server shell and a significant amount of technical skill. It would be great if Plesk incorporated the ability to install server dependencies without needing to use the server shell.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hi Paul,

    with the built-in Plesk WP Toolkit installing, maintaining and using Wordpress works like a charm. Have you already tried it? 

    Plesk Obsidian 18.0.49 and newer also feature a PECL installer where you can add PHP extensions from within the graphical user interface, saving the hassle to edit configurations on the system level.

    Please describe in more detail what is still missing so that your idea gets the required attention.

  • Don't see your idea?

Feedback and Knowledge Base