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. Custom labels in WP Toolkit

    This idea was already mentioned on: https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/39722035-custom-labels-in-wp-toolkit-and-additional-filteri

    And to give some ideas of what custom labels could be added:
    - managed / unmanaged
    - notes about who manages the site
    - notes about special environments besides production / staging / ...

    It would be less work to not have to look up these informations for each site and be able to just add a short custom label. For us these labels do not need to be filtered, but it would be a nice-to-have to have this addition like described in the original thread.

    27 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

    17 comments  ·  WordPress Toolkit  ·  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)

    We are planning to add this functionality very soon, but there's one fundamental thing we need to clarify with you first:

    Current hardcoded labels in WordPress Toolkit are global/public. If server administrator sets a "demo" label on a customer's site, this label will be seen by customer as well, since it's just a property of a site in WPT. Moreover, the customer can change this label to a different one, for example, "staging", and server administrator will see the "staging" label instead.

    Adding custom labels means one of the following:

    1. Custom labels stay public -- in other words, everyone will see all labels added to a site, regardless of who've added them. So, server administrator could add a "pain in the ass" label to a client site, and the customer would see it and change the label to "no u

  2. Allow disabling of Let's Encrypt on a domain by domain basis

    Currently, when giving users the ability to access SSL to add their own certificates, they can also view Let's Encrypt and create free certificates. It would be useful to allow users access to add their own certificates without giving them access to use Let's Encrypt and there is currently no way to do this.

    Additionally, any users logging in to manage their domains can see Let's Encrypt (although cannot use it) and we keep getting asked about it, so it would be useful to hide this off for users unless they specifically need access.

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Customize which email address can receive the notifications from WordPress digest

    Provide an option via the interface to customize the notification for the WordPress digest, as an example:

    As default Plesk send the notification from all customer/reseller or additional administrator.

    Would be amazing to instead only select all customer/reseller or add administrator accounts, also be able to select which customer will receive the notification or remove specific customer from the list.

    12 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

    4 comments  ·  Plesk (general)  ·  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. Add ZeroSSL as an alternative to Let's Encrypt

    https://zerossl.com now offers 90 days ssl certificates that work with ACME.

    It would be nice to be able to choose it as a ssl certificates provider in Plesk.

    Probably not too complicated since it relies on same technologies.

    10 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

    10 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. Add IgnoreHosts options to Plesk`s DMARC implementation

    Currently it is possible to whitelist only domain with IgnoreMailFrom parameter. However there could be false-positive DMARC failures (in case sender's strict policy and mail going throughout relay) due to which it could be useful to have option to whitelist specific network. It would be nice having this option available

    10 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

    5 comments  ·  DNS  ·  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)

    During research, we have found that the request is about passing emails via intermediate mail gateway (which works as an anti-spam solution) and the idea of the request is do not check SPF for these emails on Plesk side.

    In Plesk, there is already exist a solution for that: need to use "SPF Local rules" setting to configure an SPF record which will be used by Plesk to validate emails (including emails from an intermediate anti-spam solution). See KB article for mode details (https://support.plesk.com/hc/en-us/articles/360022753174) and Plesk documentation.

    If it does not solve the issue on you Plesk environment and you still need the "IgnoreHost" option, let us know more details about you case for that in comments below.

    — AY

  6. LiteSpeed 1 Click On

    Please enable LiteSpeed ​​with one click, just like changing from apache to nginx. thanks!

    5 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  ·  Plesk (general)  ·  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. Version selection for Nextcloud Extension

    Often the new versions of Nextcloud are not compatible with some plugins, so an option to select the major version to be installed would be useful

    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

    more input required  ·  1 comment  ·  Extensions  ·  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)
  8. Restrict the installation of deprecated WP versions in WPTK

    An option to restrict the installation of a deprecated WordPress versions in WPTK would be a nice addition.

    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  ·  WordPress Toolkit  ·  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)
  9. 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Support newer versions of ISC Bind along with Slave DNS Manager extension

    Support newer versions of ISC Bind along with Slave DNS Manager extension

    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

    more input required  ·  0 comments  ·  DNS  ·  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)
  11. Exclude yarn .cache folder from backup by default.

    The .cache folder takes up a lot of (unnecessary) backup space.

    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  ·  Backup / Restore  ·  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)
  12. Plesk Advisory that write permissions (ntfs) are allowed as full contraol/modify/delete

    Plesk Advisory that write permissions (ntfs) are allowed as full contraol/modify/delete

    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  ·  Plesk (general)  ·  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)

    Adding the “Additional write/modify permissions” checkbox really gives the pool user Full access privileges to your site’s content. This should be described in our Plesk documentation.

    It is not completely clear what does not suit you:

    - what is this checkbox set by default?
    - that it doesn’t show up somewhere in the interface?
    - or the fact that there is no red warning that “you now have an unsafe option enabled, turn it off urgently”?


    IG

  13. Limiting access to Plesk panel by specifying the allowed dst addresses

    It is required to control the accessibility of the Plesk panel by having an option to permit access only by the specified server's IP's. For example:
    Let's say there are 172.16.1.10 & 172.16.1.11 IPs on the server both assigned with a domain name panel.example.com.
    Option "Specified domain" is set in Tools&Settings > Customize Plesk URL.
    Any other IP address on that should NOT serve the login procedure.

    However, when this server has a full subnet 172.16.1.32/27 added as the secondary IP addresses, it is possible to open any of them via the Web Browser, afterward press "Log in to Plesk"…

    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  ·  Plesk (general)  ·  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)
  • Don't see your idea?

Feedback and Knowledge Base