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
290 results found
-
dist-upgrade with automated scripts like for Ubuntu 18
As you write in the instructions, a dist-upgrade can be a difficult and risky undertaking.
Unfortunately, it's not always possible to simply rent an additional server and transfer the data from A to B.
In the meantime, a lot has been changed on the server and, moreover, it's also a matter of cost.
Therefore, it would be great if, like for Ubuntu 18 to Ubuntu 20, there were automated scripts for the dist-upgrade of other operating systems as well.
1 voteThank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
-
consistency between PhpSettingsCustom and dom_param tables.
It would be great that plesk repair db checks the consistency between PhpSettingsCustom and dom_param tables.
This can be reproduced by adding some additional php directives via Plesk UI for example.com domain and then removing them from table PhpSettingsCustom via plesk db command.
1 voteThank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
-
An option to change 'from' field in Plesk email notifications when using MSMTP
Currently, it's possible to change the 'from' field in Plesk email notifications only when Postfix or Qmail is installed. The change cannot be applied when using MSMTP.
Please implement an option in Plesk to change the 'from' field in email notifications when using MSMTP.
1 voteThank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
-
Add a feature wizard / feature showcase for feature on updates
TL;DR: This is a feature request for adding a feature wizard/showcase (for lack of a better name) to Plesk. Something that simply let's administrators choose whether they want to enable the new features that have become available when a Plesk update has been installed.
Detailed use case:
Currently, often new features are enabled by default when a Plesk update gets installed on existing Plesk installations. This is not always desirable and can cause confusion with Plesk server administrators. For example administrators might not want to enable new features directly as they become available because they want to familiarize themself with the feature first. Which…6 votesThank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
-
Create the option "Maximum number of incremental backups to store" on Plesk
Currently, it is possible to limit the "Maximum number of full backups to store" which is valid for Full backups only, it would be good to have a similar option to limit the "Maximum number of incremental backups to store".
It may be useful in cases when it's required to store the incremental backups e.g. last month and have full backups from the previous months also.
4 votesThank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
-
SMTP Connection in SiteJet Builder
Store SMTP connections in Sitejet Builder. phpsendmail is not a quality solution.
5 votesThank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
-
Allow setting MAILFROM field in crons from Plesk Interface
When a customer adds a cronjob within the Plesk interface through "Scheduled tasks", they can set the recipient (MAILTO field) of the cron with the "Send notifications to" field, but there is no option to set the sender (MAILFROM field). By default, the sender for crondaemon is user@server.tld, which in our case causes SPF errors with the receiving mail server of the recipient.
We do not give our clients CLI access, so they cannot manually set it with the crontab -e command, nor should they (the whole point of the Plesk Interface is for GUI-style ease of use). Could…
2 votesThank you for your idea and your additional explanation. As the use case is probably an edge case, we'll need to see whether many other users believe that this is an important feature that they need.
If you believe it is an important feature, please continue voting for this feature request.
-- PD
-
Additional option for overuse policy- Overuse is allowed up to x %
I would like to have option to set overuse policy as:
Overuse is allowed up to x %
- after percentage threshold is crossed then suspend and send e-mail notification
- with ability to set up percentage freeley, but suspend when disk usage is 110 % or 130 % and so on.2 votesThank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
-
Add a snapshot of the current processes list to existing CPU / memory usage exceeded emails
The Monitoring extension already triggers email notifications when resource usage exceeds the allocations, but if usage has already settled before you notice these emails and click through to the server, it's difficult to find which domain was the cause.
Adding a snapshot of the current processes list to these emails when it's the CPU or memory usage thresholds that have been exceeded would be very useful. Potentially just the "Domains only" filtered list would suffice. Maybe trimmed to the top 50 or so processes ordered by CPU or memory, whichever is appropriate at the time.
1 voteThank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
-
Access to the action log under the customer
Provide the possibility to get information from the action log under the customer that is related to the domains and objects that belong to this customer.
1 voteWe've started to research what is required by the panel to satisfy NIS2, internal ID PPM-5343.
-- PD
-
Add unique identifier to login event parameters
Currently the user login/logout event only gives a contact name as event parameter. This is not a unique identifier since multiple users can have the same contact name. In the psa log_actions database table the username is saved. Please also add the username to the event parameters so there's a unique identifier which user logged in our out.
Not sure about the category, so please replace if there's a better place for this suggestion.
1 voteThank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
-
Allow modification of how long the mail password reset link will take to expire.
Currently the length of time to expire is 24hours. It would be desirable to be able to increase how long the link takes to expire.
3 votesThank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
-
Prohibit user from deleting domains
Hello,
Another customer's domain names were accidentally erased from his control panel, according to us. Please give us a choice to prevent this from occurring again. Alternatively, provide us access to a internal ticket system, which requires staff approval.1 voteThank you for your idea. When deleting a domain, a clear warning an confirmation dialog is displayed. Domains are only deleted when that additional dialog is confirmed. https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/41416156-delete-domain
Nevertheless, we'll consider adding a feature that users won't be permitted to delete domains at all, if this request becomes popular.
-- PD
-
Custom Temporary Domain Names
When you create a new site, you get the amazing option to generate a Temporary domain name.
However, these are randomly generated, which makes finding your dev site difficult, especially if you have a lot of them.
I get that you can change the domain after creation, but hopefully it won't be such a large change to the plesk code to allow you to alter the domain name at creation from "silly-lalande.90-65-15-200.plesk.page" to "(custom-website-name).90-65-15-200.plesk.page"
2 votesThank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
-
Option to set RTL instead LTR text while editing Plesk notifications
Implement an option to set RTL instead LTR text while editing Plesk notifications. Useful for certain languages, like Hebrew.
1 voteThis is a valid idea. We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
-
Installation of TYPO3 and Toolkit similar to WP Toolkit
Our customers wish to install TYPO3 websites after buying an abonnement through WHMCS or the Plesk panel and have a toolkit where they can manage their TYPO3 installations from a panel like WP Toolkit. I searched through all feature suggestions but I didn't find a suggestion. You should be able:
- to rollout TYPO3 installations
- to manage all your TYPO3 installation
- to update your TYPO3 installation
- to stage/test their TYPO3 installation
- to remove your TYPO3 installation
- to reinstall your TYPO3 installation4 votesThank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
-
Add an icon on the Websites and Domains dashboard, under Status with the other icons, that shows the status of SSL whether it is active
Add an icon on the Websites and Domains dashboard, under Status with the other icons, that shows the status of SSL whether it is active or not.
Hover over shows the Expiry date, but that is not essential. Knowing if SSL is active at a quick glance is.
2 votesThank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
-
Option To Auto Add Cloudflare IPs To Fail2Ban Whitelist
Add the option to auto add Cloudflare IPs to Fail2Ban whitelist. A simple check box in the Fail2Ban management panel that will add a Cron job similar to the one described here: https://talk.plesk.com/threads/cloudflare-whitelist-scripts-for-fail2ban-and-nginx.361572/ .
This is something that will help a lot of people using Cloudflare and it's relatively easy to implement.
Thanks.1 voteThank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
-
Allow the creation of forbidden domain names via API
Please implement an option in Plesk, which allows the administrator to create domain names, which are forbidden for creation via Plesk UI.
For example, *.example.com has been added in Plesk > Tools & Settings > Prohibited Domain Names. This limitation should apply to all users in Plesk UI, but the administrator should still be able to create *.example.com subdomains via API calls.
This will be useful when looking to automatically provide users with a free subdomain for hosting, but prevent them from creating unlimited number of *.example.com subdomain via Plesk UI.
4 votesThank you for your idea! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
-
When Nginx and Apache are used, Apache should only listen to ports 7080 and 7081 on localhost.
As discussed in https://talk.plesk.com/threads/security-attack-surface-ports-7080-and-7081.368543 security should be reinforced: When Nginx and Apache are used, Apache should only listen to ports 7080 and 7081 on localhost. When Nginx is not used, Apache should only listen to ports 80 and 443.
6 votes
- Don't see your idea?