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

1639 results found

  1. Autoresponder "From" Email Addresses

    It is commonplace nowadays to see something like this when we receive email.

    "Accounts From My Organisation" accounts@myorganisation.com .

    It looks far more professional and more aesthetically pleasing than the utilitarian "accounts@myorganisation.com" which is the only option currently available in the Plesk Obsidian autoresponder functionality.

    It would be a nice feature - and fairly simple, I imagine - to add a field to the autoresponder functionality to allow us to enter a "pretty" name which would be what the email recipient would see in their inbox. Alternatively, of course, the existing field could be amended to allow for…

    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  ·  Mail  ·  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. Add the Flutter support to Plesk

    Please add the the Flutter support to Plesk

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. URL-based branding logos

    I suggest enabling Plesk to allow different branding logos in the login screen and the top left corner of the session, depending on the full-qualified hostname used to reach the server. For example, if a server can be reached through 2 different names, the idea would be to be able to set a default branding logo and have alternative ones depending on the URL used to connect to the server. Here's an example:

    plesk.domain1.com -> main logo (default)
    plesk.domain2.net -> alternative logo 1
    hosting.domain3.co -> alternative logo 2
    any other aliases/URLs -> main logo (default)

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Allow specifying of ports to open in firewall during certificate generation process to open and close again automatically

    allow for specific ports to be opened when securing/ressecuring Let's Encrypt SSL certs.

    For example, Lets Encrypt needs several ports open in order to reissue SSL so have a field to enter the ports to open when re issuing the SSL.

    tcp:80, 443
    udp:443

    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

    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)
  5. Usage of "Quick Preview" DNS should be made more clear.

    The fact that Plesk must be the DNS server for the "Quick Preview on a domain in Plesk" option should be underlined and more prominent in the interface. The necessity of a Wildcard SSL cert should be clearer too. That would help your clients and avoid some tickets to Plesk support.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Introduce other MFA methods besides the phone app

    As for now, MFA extension is limited only to a phone app. It would be useful to introduce other authorization methods (e.g. mail) for this extension.

    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  ·  Security  ·  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. Block new extensions to be installed during Plesk Upgrades

    Add the possibility of switching off any new default extension to be installed automatically during the Plesk Upgrade process without the need of blacklist this explicitly one by one but to block all new extensions installations entirely.

    19 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Remove All Files / Packages From The Previous Plesk Obsidian Release(s) As Part Of Plesk's Upgrade Process

    As per the title. When any Plesk Obsidian release is upgraded to the next release, many files and/or packages are simply left in place and not removed as part of the Plesk installation process. Without patient and time-consuming manual "clean-up" exercises, all of these now unused and non-functional files and/or packages, simply accumulate and (just like garden weeds do in the real world) take up useful and valuable server real estate, but for no purpose. It's a little surprising that this is still happening, when nearly all software packages provide this as a default action.

    7 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Custom color wheel for private branding

    Currently, Plesk provides only two options for branding customization, which can be limiting for users managing multiple internal companies with distinct branding needs. I propose the addition of a custom color wheel for private branding in Plesk.

    This feature would allow administrators to choose from a broader range of colors, offering more flexibility in aligning the Plesk interface with specific company branding. For users handling multiple companies, this customization option would be a significant improvement, making it easier to differentiate between brands.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. CAS Trust Level Setting in Service Plan Level

    Add the capability of setting the CAS Trust level on the Service Plan level under the Permissions tab.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Add SMIMEA Record in DNS

    Add the SMIMEA record in the DNS-system.
    This is required for encrypted email communication.

    There is no need to set up an automatic system, just the option to create an individual record.

    The 63-character restriction must be removed, otherwise the hash of the address is too long and will be rejected.

    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  ·  DNS  ·  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. Update GUID during process migration

    Update GUID during process migration. Plesk migration tool needs to be updated to do this. This will avoid any issues with GUID conflicts.

    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

    1 comment  ·  Migrations  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Please add PostgreSQL 16 support to Plesk

    According to official documentation from https://docs.plesk.com/release-notes/obsidian/software-requirements/#s4, Plesk currently supports PostgreSQL from 8.4 to 15 version

    Please add PostgreSQL 16 support to Plesk as well

    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

    3 comments  ·  Databases  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Bypass MFA when using session token to login

    Currently, when session tokens are used for logging into Plesk and MFA is enabled, the MFA code is still required.

    It would be useful to have an option to bypass MFA when using session tokens to log into Plesk.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Great fight against spam: Make possible to add settings in '.cf' for spamassassin like adding an helping DNSBL and/or modifying scores

    The possibility to add DNSBL's is not bad, but not good as without knowing several emails are blocked and in these blocked emails sometimes is a or several hams/emails as false positives. Much better would be being able to put in an '.cf'-configurations-file for spamassassin 'DNSBL's, which do not block but move emails identified as spam to the spam folder. Later on the customer can watch from time to time if hams/femails as alse positives have been sorted out wrongly and put them back to the inbox or a sucfolder which is not for spams.

    A rule can even learn…

    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

    2 comments  ·  Mail  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Cloudflare records exclusions

    A very cool feature would be to exclude individual records in the zone from sync / export to Cloudflare and the choice by auto-update to only update / create records without removing whole Cloudflare zone.

    In my particular scenario I am serving mts-sts. via Cloudflare worker. Everytime Plesk update DNS zone on Cloudflare the particular mta-sts. record is deleted. This record can not be created in Plesk, because it is a worker trigger.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Add to Plesk possibility of installing certificates from ACME-compliant services other than Let's Encrypt

    In Plesk, there is a Let's Encrypt which is an ACME-compliant vendor of certificates. It would be good to have another one or the possibility to implement other ACME-compliant certificates via Plesk tools. For example JPRS: https://jprs.jp/pubcert/about/ACME/index.html

    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)
  18. Make Composer advisories configurable to only notify for production vulnerabilities

    Add a setting to change the Composer warning advisories to only trigger on production vulnerabilities, so that non installed dev dependencies don't trigger warnings

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. include panel.ini in server backups

    The idea behind this feature is to have the panel.ini configuration file included in server backups, allowing it to be restored if it's accidentally modified or an issue occurs. Saving time and if the changes are not remembered fully.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. add time-expiring fail2ban whitelist entries

    Please add the ability to add IP addresses to a temporary whitelist with an expiration option. Occasionally, customers may need to troubleshoot issues (e.g., verifying their mail account credentials) after being banned by Fail2Ban. To prevent them from being immediately banned again, we whitelist them temporarily. However, over time, if you forget to remove them, the whitelist grows indefinitely. It would be beneficial if these entries could automatically expire and remove themselves after a set period.

    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  ·  Security  ·  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