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.
Off-topic posts will be removed from here
2086 results found
-
Add the Flutter support to Plesk
Please add the the Flutter support to Plesk
3 votesThank you for your input! We will consider this functionality in upcoming releases if it becomes popular.
Everyone, please continue voting for this feature if you consider it important.
-- SH
-
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 votesThank you for your input! We will consider this functionality in upcoming releases if it becomes popular.
Everyone, please continue voting for this feature if you consider it important.
-- SH
-
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:4433 votesThank you for your input! We will consider this functionality in upcoming releases if it becomes popular.
Everyone, please continue voting for this feature if you consider it important.
-- SH
-
Create a BIND-independent SSL It! mode
As of now SSL It! requires an active BIND (DNS) service to function, as it relies on DNS validation to issue and renew certificates. This dependency is hardcoded into the extension’s logic to ensure compatibility with certificate providers like Let’s Encrypt and to maintain secure, automated certificate management.
The idea is to allow for this feature to be able to disable this hardcoded logic, which requires active BIND service to update the DNS in certificates.
1 voteThis is a valid request, so we'll look into it. There is no ETA at the moment, but we would really appreciate you voting for this request so that we can accurately assess its popularity relative to other features. Thanks in advance!
-- SH
-
restart cookie expiration time of 2FA (Google Authenticator) after a successful login
It is already possible to have the cookie of the 2FA login expire after n days. But for admins who work on many servers, this still causes unnecessary extra work once that time frame expires. Because then they will be prompted to enter the 2FA code again, and this happens on all the servers they operate. It adds up to a lot of wasted work time.
Instead, the cookie expiration could be reset to n days after each successful login. Example: A user sets the expiration to 90 days, but on day 81 the user logs in without having to…
1 voteThis is a valid request, so we'll look into it. There is no ETA at the moment, but we would really appreciate you voting for this request so that we can accurately assess its popularity relative to other features. Thanks in advance!
-- SH
-
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 votesThank you for your input! We will consider this functionality in upcoming releases if it becomes popular.
Everyone, please continue voting for this feature if you consider it important.
-- SH
-
Support for HTTP/2 on apache (without using nginx as proxy)
Hi,
It seems some Plesk users would like to have support for HTTP/2 on apache directly (without using nginx as a proxy).
We do not clearly understand cases when it is required. Why using nginx as a proxy in front of the Apache is not an option? Could you please let us know how this feature should work in terms of workflow, in your opinion? We welcome any feedback and would be happy to receive examples to investigate the question in more detail.5 votesThank you for your idea. Could you tell us which scenarios you want to enable with this functionality?
— AY
-
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 votesThank you for your suggestion. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
-- KvD
-
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 -
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 votesThank you for your suggestion. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
-- KvD
-
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 votesThank you for your input! We will consider this functionality in upcoming releases if it becomes popular.
Everyone, please continue voting for this feature if you consider it important.
-- SH
-
Dark Mode across channels
Having a consistent viewing experience across channels would be appreciated, going from dark to white is not easy on the eyes. Unifying preferences to automatically adapt across channels(feature requests, support, updates...) would improve overall experience.
1 voteThank you for your input! Dark Mode will be integrated into Plesk Installer/Update Manager in one of the feature releases.
-- SH
-
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 voteThank you for your input! We will consider this functionality in upcoming releases if it becomes popular.
Everyone, please continue voting for this feature if you consider it important.
-- SH
-
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 votesThank you for your input! We will consider this functionality in upcoming releases if it becomes popular.
Everyone, please continue voting for this feature if you consider it important.
-- SH
-
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 votesThank you for your input! We will consider this functionality in upcoming releases if it becomes popular.
Everyone, please continue voting for this feature if you consider it important.
-- SH
-
Support for Wordpress Redis Object Cache plugin in cloning operations
Cloning/Site copy features present errors like wrong URLs when the Wordpress Redis Object Cache plugin is enabled.
9 votesThank you for your suggestion. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
-- KvD
-
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 votesThank you for your suggestion. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
-- KvD
-
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 votesThank you for your input! We will consider this functionality in upcoming releases if it becomes popular.
Everyone, please continue voting for this feature if you consider it important.
-- SH
-
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 votesThank you for your update and additional details! We will consider this functionality in upcoming releases if it becomes popular.
Everyone, please continue voting for this feature if you consider it important.
-- SH
-
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 votesThank you for your input! We will consider this functionality in upcoming releases if it becomes popular.
Everyone, please continue voting for this feature if you consider it important.
-- SH
- Don't see your idea?