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
2068 results found
-
Allow hosting email directly on Google when using Google Workspace extension
Currently, Plesk sets DNS records for mail to mail.<domain> pointing to the Plesk server and creates accounts in Google Workspace as well as accounts locally which are then relayed to Google Workspace, so emails go through the Plesk server and become unavailable if Plesk is down even though they are hosted on Google
Please add possibility to set the mail records to point directly to Google
2 votes -
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 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 a way to remove entries from the Scheduled Backups List extension
The Scheduled Backups List extension has no option to remove entries. When there are many domains and customers enable and disable scheduled backup tasks, the extension eventually becomes unusable as it's necessary to manually navigate pages to find relevant disabled backup tasks.
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.
In the meantime, I believing sorting the tasks by Status, Name, Type, etc. can help you navigate a bit easier.
-- SH
-
Arch Linux support
It would be nice to have Arch Linux among supported systems due to security concerns and more frequent and accurate patches.
2 votesThank you for your input! We will consider introducing support for Arch Linux if it becomes popular and there's demand for it.
Everyone, please continue voting for this feature if you consider it important.
-- SH
-
Make Visual Studio Code projects deployment possible from non-root SSH
Visual Studio code deployment on Plesk for Linux doesn't work as intended if a non-root user with SSH enabled is used. Therefore, only root can be used to deploy projects.
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
-
Secure one way encrypted password storage (no mail_auth_view for gdpr, pci-dss, nis2)
Mail password are encrypted but not hashed.
Clear text password are available using the utility
/usr/local/psa/admin/bin/mailauthviewThis is just symmetric everyone not the good practice. See OWASP :
https://cheatsheetseries.owasp.org/cheatsheets/Password_Storage_Cheat_Sheet.htmlIt does not meet many regulations (often referring to good practices or OWASP) and it's an unnecessary security risk of password exposure.
Please add an option to have mail user password hashed one way.
Thanks.
1 voteThank you for your input. We are already working on storing only password hashes, rather than actual passwords. I cannot provide any ETA at this moment.
-- SH
-
Forward domain logs to an external server through syslog
Provide the functionality to forward the domain logs to an external server using syslog.
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 SMTP authentication with incoming mail disabled
Having the mail server enabled for a domain makes all mail go to it internally, even if the MX records of the domain point to another server.
The option to disable incoming mail resolves this, but doesn't allow Plesk to send mail over SMTP for that domain, only PHP mail.
This is not preferable because this mail can't be encrypted nor signed with DKIM. Therefore, for security, Plesk should have an option to disable incoming mail while still allowing SMTP delivery by using the public MX records.
4 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
-
IISNode
Install IISNode v. 16+
1 voteThank you for your suggestion. Could you please explain your request in more detail? Thank you in advance.
-- SH
-
Change ".NET CLR version" to "No Managed Code" via Plesk interface
It would be useful to change IIS application pool setting ".NET CLR version" to "No Managed Code" via Plesk interface
3 votesThank you for your input! Could you please provide more details on what the desired end goal is and how would that be beneficial for other Plesk users? Thank you in advance.
-- SH
-
Add "issuemail"-property tag for CAA-Records
When creating a CAA record, you can only choose between "issue", "issuewild" and "iodef". Certificate Providers like Sectigo have begun enforcing CAA-Lookups. (See https://www.sectigo.com/knowledge-base/detail/CAA-Record-Certification-Authority-Authorization-1527076091491/kA01N000000zFMO )
For a S/MIME certificate the propery tag needs to be "issuemail". Could you add this to the selection of CAA record property tags?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 Percona support
Support and shipping (installation) of Percona server
3 votesThank you for your input! We will consider introducing support for Percona in upcoming releases if there is considerable demand.
Everyone, please continue voting for this feature if you consider it important.
-- SH
-
manage root user event handlers **VIA THE UI** without blocking their existence entirely
ability to block access to create / manage root user event handlers VIA THE UI without blocking their existence entirely (i.e. so that CloudLinux installer would work, which I presume creates the event handlers via CLI, but the Plesk admin would not have access via UI to touch them or create event handlers of their own that would effectively give them root access to the underlying server).
2 votes -
Disable HTTP/2 support on Plesk Interface
Give to the administrator the ability to disable HTTP/2 using the Plesk GUI in Plesk Windows
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.
In the meantime, please following the instruction from our documentation on how to disable HTTP/2 through the command line.
-- SH
-
Exclude specific parameters from syncing with the Service Plan on unlocked subscriptions
The option to exclude certain parameters such as hard disk quota from syncing with the Service Plan on unlocked subscriptions can be provided in 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
-
Add option to hide DKIM management
We haven an external DNS cluster and an external customer panel in which customers can manage things like DNS records etc.
We have implemented a function through which we can let the customer enable DKIM through the external panel, which enables it on the Plesk server, retrieves the key, and adds the key to the zone on the DNS cluster
In order to avoid conflicts and confusion we would like to hide the DKIM settings in Plesk for the customer on the subscription level.
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
-
Queue emails over limit in a domain instead of defearring
If you have activated a limit and the limit is reached, all further mails are rejected. It would be good if for these emails to remain in the mail queue and be sent automatically after the set time for the limit has expired.
5 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
-
Add email list impot from plain-text file for white or black lists
When adding email to white or black list, Plesk only gives the option to write manualy one address, and you need to click link to add another one. If you made a decent mannagement of your dmarc responses, and extract spam emails or domains from received email, you have a list too large to write by hand. An option to import a plain text with an email address or domain or top level domain really is a must.
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.
In the meantime, assuming that you are referring to the Blacklist in Server-wide mail settings, as a workaround, you can use the following command to import the entries from txt files:
For Blacklist:
cat your_blacklist.txt | while read i; do plesk bin mailserver --add-to-black-list $i;done
Please make sure that you have each entry on a new line.
-- SH
-
Add customer number to frontend
There already is an API field for the customer number. Why can't I set this through the UI?
Would be critical for us to be able to automate billing.2 votesThank you for your suggestion. In order to get better understanding, could you please confirm what exactly are you referring to by "number", e.g. the customer ID, the guid, number of customers, phone number, or something else. Thank you in advance.
-- SH
-
Detect and notify of vulnerabilities in NPM packages within Node.js extension
Detect and notify of vulnerabilities in NPM packages within Node.js extension
4 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.
In the meantime, you may consider using npm audit, for example.
-- SH
- Don't see your idea?