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
2071 results found
-
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.2 votesThank 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
-
Ability to run plesk sbin statistics for entire Plesk Subsription or Customer instead of domains only
I would appreciate your assistance in determining if it is possible to request and calculate statistics for the entire Subscription or Customer. For instance, the user "webmaster999" has three domain names (including one random subdomain), however I have to list all domains in the plesk sbin statistics --calculate-list --domain-names= command in order to calculate their statistics. It would be easier to list only the main Subscription or a unique identifier for the Customer.
1 vote -
Ability to set a Subscription or Domain Backup Default
I'd love the ability to set a subscription such that a Scheduled Backup configuration is enabled by default? E.g. "backup all files, daily, store 1 day"?
Often times I realized after the fact that a domain backup was not turned on. The "scheduled backup list" extension is nice, but I'm looking more for a default option.
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
-
Create a "grid" of permissions where admin can enable or disable parts of menus related to the Service Plan
Can be really usefull increase details of personalizations of the customer's menus, for example:
into smb/iis-app-pool/settings/id (AppPools Settings) to allow to recycle it but not to create a new one
For example, if customer creates a subdomain, it can also create a dedicated appPool for it and this can create problems in some envs.Our suggestion is to create a "grid" of permissions where admin can enable or disable parts of menùs related to the Service Plan, as happens now but much more granular
Thanks
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
-
Make "plesk bin subscription" able to add Apache additional directives for HTTP and HTTPS
Make "plesk bin subscription" CLI command have the option to add Apache additional directives for HTTP and HTTPS. Right now, only nginx additional directives can be added via this command.
1 vote -
Allow wildcard certificates for forwarders without Nginx installed
Due to fixed issue EXTSSLIT-1871, if nginx is disabled, it is no longer possible to start securing a domain with the “Forwarding” hosting type: https://support.plesk.com/hc/en-us/articles/12377017310999.
Please allow at least issuing wildcard certificates for forwarders without nginx installed, since these only require DNS validation.
2 votes -
DKIM Weekly Rotation of key, with new 'selector' where previous selector is removed the next week
As in:
https://proton.me/blog/dkim-replay-attack-breakdownRotating DKIM is highly important.
Currently, it' **** easy to rotate the DKIM key on Plesk, not to talk of updating DNS and running Route 53 update.
This is asked to be implmented, where a second key is added, and new mails use it.
Old key would be depreciated a week later, as previous emails are still in the progress.
Rotate your DKIM keys regularly – Rotating our DKIM keys allowed us to quickly stop the attack and buy time for the permanent solution. Although tedious and risky to do manually, Proton’s DKIM key management system(new window)…
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
-
Oversign Emails' DKIM From, To, and CC headers
As in:
https://proton.me/blog/dkim-replay-attack-breakdownOversign From, To, and CC headers – Most DKIM implementations always sign the From, To, and CC headers if they are present in an email, preventing them from being modified if the message is resent. However, if these headers are missing, they are often unsigned, opening the door to replay attacks with forged headers that make the fraudulent emails seem legitimate. Oversigning mitigates these attacks by signing these sensitive headers in all cases, even if they are blank. If you use Proton to send your email, this oversigning is done for you automatically by our mail servers.
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
-
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
-
Manage BAN commands for Varnish cache inside Plesk
Enable an option inside plesk to manage Varnish cache ban individually per subscription.
1 vote -
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
-
Ability to disable aum automatic updates in mod security and apply it manually
Provide the ability to disable aum
automatic updates in mod security and apply it manually2 votes -
Possibility to use the extension "Site Import" over API or CLI
It would be helpful to have the option of using the Site Import extension over an api endpoint or via cli access. This would allow the creation of automated tasks that involve it.
1 vote -
Add Ubuntu Pro versions to Supported OSes
Please add Ubuntu Pro to Supported OSes, such as Ubuntu 18.04 for example
1 vote -
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 option to mitigate known vulnerabilities by default during installation of WordPress
There is an option in WP Toolkit to mitigate the Unauth. Blind SSRF vulnerability. However, this may only be applied only once WordPress has already been installed. Please add possibility to secure the instance in this regard (and any other vulnerabilities that might be found later, if such option is added to WP Toolkit) directly when installing WordPress.
2 votes -
Make the Grafana Monitoring extension in Plesk use other languages
Once I set the language of Plesk to another language, the language for the Grafana Monitoring extension remains English. It would be nice to have the option of selecting another language in that interface.
5 votes -
Allow to manage Spam Filter settings in Email Security for aditional users
Add permission to edit security settings in plesk email security for users without "create and manage websites" (additional users)
1 vote -
Restrict Mailman access to certain IP addresses
There's restricted mode for Plesk interface, but there's no implementation to allow restriction for Mailman only.
2 votes -
Allow migrating domains from one account to another in Google Workspace extension
If there are several domains set up on server A linked to Google Workspace managed by account #1, then trying to migrate them to Server B with another account #2 would result in an error because these domains are already set up under another account.
Please make it possible to migrate domains in these scenarios without having to re-link the domains to another account and move the data manually.
1 vote
- Don't see your idea?