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
2103 results found
-
Allow importing external DNSSEC keys (KSK/ZSK) into Plesk DNSSEC interface
Allow importing external DNSSEC keys (KSK/ZSK) into Plesk DNSSEC interface
Currently, Plesk’s “Use Existing Keys” DNSSEC feature only works if keys were previously generated by Plesk itself and are already present in its internal database.
There is no way to import an externally generated KSK/ZSK key pair into Plesk’s DNSSEC interface, which makes DNSSEC domain migrations difficult. Users are forced to either rotate the keys and notify the parent zone (risking downtime) or perform manual workarounds outside the GUI.
It would be valuable to add a supported method in Plesk to import legacy DNSSEC keys, allowing seamless migration of already-signed…
2 votes -
Plesk Migrator should be able to use a sudo user's key and su to root to perform the migration
Plesk Migrator should be able to use a sudo user's key and su to root to perform the migration. This is to be done inline with VPS provider security recomendations.
2 votes -
2 votes
-
GDPR Compliance – Add Impressum & Privacy Policy Links to Plesk Login Page
To fully comply with GDPR requirements, it would be beneficial to have an option in Plesk that allows adding links to the Impress and Privacy Policy directly on the login page. This ensures that users have transparent access to privacy-related information before logging in.
Requested Features:
Ability to specify Impressum and Privacy Policy URLs via the Plesk UI or a configuration file.
Display of these links at the bottom of the login page (e.g., as a footer or a separate section).
Optional: Customizable link text (e.g., "Impressum" and "Privacy Policy").Benefits:
Ensures GDPR compliance by making legal information easily accessible.…
2 votes -
Add means to control which Master IP address (Private or Public) will be referenced on slave DNS servers
Currently, If Public IP address is added on the Master DNS server under Tools & Settings > IP addresses, all new zones created afterwards will have Public IP address in .nzd/nzf file on the slave DNS server. In case of Google Cloud/AWS this might not be the desired behavior since they recommend to keep the DNS traffic on the private network. Some means of controlling which Master IP address is being referenced on the slave configuration is required.
2 votes -
Allow possibility to set Let's Encrypt certificate for forwarding domain when the server is using LiteSpeed.
LiteSpeed is a supported web server on Plesk (e.g. unlike Lighttpd or OpenLiteSpeed), so all Plesk functionality should work with it.
It's important that this option is available to the customers via the GUI2 votes -
Add a warning and way to switch SOGo webmail to/from regular and nightly repos
SOGo webmail has two repositories, regular and nightly releases. There should be a way to switch between them from Plesk, without having to reinstall the software manually.
Additionally, reinstalling the software removes all configurations. Plesk should have a warning for this, or make it so that they're not lost.
2 votes -
Add possibility to configure /var/log/mysql/audit.log via Plesk
Please add the possibility to configure the MariaDB /var/log/mysql/audit.log via Plesk
2 votes -
Add the ability to limit swap under Cgroups Control Manager
When cgroups v2 is engaged under Cgroups Control Manager in Plesk, it's able to only control MemoryMax variable on the user slice which happens to be RAM memory. Add a feature of limiting the amount of swap usage as well which happens to be a MemorySwapMax variable in order to prevent subscriptions from occupying all swap when the limit on RAM was reached.
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
-
Automatically issued certificates (Let's Encrypt) are not properly migrated using Plesk Migrator
Currently, Plesk Migrator does not properly transfer automatically issued certificates (Let's Encrypt).
This request is to improve the migration process and ensure that automatically issued certificates (Let's Encrypt) are fully functional after migration.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
-
Add ability to Plesk Email Security extension manage per-mailbox spam settings via CLI
At the moment when Plesk Email Security extension is installed, it is possible to manage via CLI only the global spam settings.
Please add the ability to manage per-mailbox spam settings via CLI when the Plesk Email Security extension is installed.
2 votesThis 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
-
Set a permitted time period to the customers to schedule their backups
Add the ability to restrict customers to schedule their backups only during a specific time.
2 votes -
Disable specific repos when upgrading MariaDB via Plesk Upgrade Tool
Be able to explicitly tell the Database Server Upgrade Tool to ignore specific repositories during the upgrade.
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
-
Get the list of the mailboxes of particular domain via REST API.
Need to implement the feature of getting the list of the mailboxes of particular domain via REST API.
Currently the mail function provide the list of all mailboxes on the server2 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 Customers to create scheduled website database dumps on their own
At the moment, Customer accounts in Plesk can create database dumps manually, however they do not have the necessary access to schedule the specific creation of such website database dumps.
That task is also not possible via a cron job, because the mysqldump command requires root access, which the Customer account does not possess.
Website database dumps can be created only manually via the Plesk GUI while using the steps in the https://support.plesk.com/hc/en-us/articles/12388279759255-How-to-export-a-website-database-in-Plesk article.
It would e very helpful to include the ability to create scheduled website database dumps while logged in as a Customer.
2 votes -
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 -
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
-
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.
2 votesThank 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
-
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 -
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.
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?