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
34 results found
-
Add ability to hide hide controls for "rejection of messages for non-existent mail addresses" for admins and resellers
Currently, the function Tools & Settings --> Interface management --> Interface control visibility
--> "Hide controls for rejection messages for non-existent mail addresses" hide control only for users. Admins and resellers still can manage this.Add the ability to hide this function for admins and resellers into Plesk restricted mode settings
2 votesThank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
--
IG
-
If disk limit reached don't suspend website but block access for owner to website
If the website reached the hard disk limit it is required that website still remain live but owner cant add new images or blogs. Instead of suspending website.
2 votesThank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
--
IG
-
Custom CAS Trust level
It is required to implement custom CAS Trust level. In Plesk only predefined available. Imlementation of the custom CAS Trust Level directly in IIS cause issued in Plesk
2 votesThank you for your input! 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.
—
IG -
Insert username in physical path of users's virtual host
Would be great to make virtual host's directories structure depending on username instead of main domain name. Or make it a switching option. Or add username in a path.
Examples:
<plesk_vhosts_dir><username><docroot>
or
<pleskvhostsdir><username><maindomainname><docroot>
In order the structure of virtual hosts and related users would be clearer,2 votes -
Subscription Templates
We often have the case that we create a new subscription and then perform the same tasks: Create a subdomain for the subscription (e.g. development.MAIN_DOMAIN), create some standard mailboxes, etc. It would be great to be able to configure this a kind of template which can be used when creating a new subscription.
2 votes -
Add possibility to use {{ panel link }} placeholder for Site creation Plesk notification
At the moment it is not possible to use {{ panel_link }} placeholder for "Site creation" Plesk notification task.
Instead of value for {{ panel_link }} placeholder, the empty text is shown in the received mail.
It will be very helpful to use this placeholder for example when we create a Customer Account with the website.
Example:
New user account can now be used to log in via following URL using the username and password you assigned: http://www.{{ domain }}:8880 if the dns is pointing to the site, or at any time you can use {{ panel_link }}
2 votesThank you for your feature request. We will consider the possibility of its implementation if it becomes sufficiently popular and in demand.
—
IG -
Show overusing mailboxes if subscriber cannot be changed due to insufficient resources warning
When attempting to change subscriber for a subscription under a reseller, the following warning is returned:
Unable to continue subscription transfer: this subscription requires more resources than can be provided by the new owner's provider. However, the mailboxes exceeding the limit are not specified.It is impossible to see which mailboxes exceed limits, especially if there are hundreds of domains on the reseller.
The suggestion is to include affected mailboxes into the warning, or at least to provide a [GUI] tool to find such mailboxes among all subscriptions under the affected reseller.
2 votesThank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IG -
Ability to assign dedicated IP to reseller without lock from syncing with service plan
When you add IP address at Tools & Settings > IP addresses the Reseller becomes locked from sync with service plan. This is expected because such resource is not set in service plan.
If you set 1 to "Allocate dedicated IPv$ addresses" option all resellers under this service plan will have dedicated IP assigned.
It is required functionality to assign dedicated IP to reseller without lock from syncing with service plan and in the way that only this reseller has dedicated IP assigned. It can looks like Reseller service plan add-on.
2 votesThank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IG -
Allow resellers to change main customer's domain name
If the option 'Forbid customers to change the name of their main domain' set in Tools & Settings > Server Settings, reseller also unable to change the main domain.
The Reseller is Administrator for his customers and should have this right.
2 votesThank you for your input! 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.—
IG -
Add warning message if Postgres installed on the Web Admin License but without Developer pack extension
The Postgres installed on the Plesk Web Admin edition but not persists in Tools & Settings > Database servers.
To manage PostgreSQL Developer pack extension required. But it does not produce any warnings about that which is confusing.
Also, there is no information about Developer pack in license management. I would suggest to add new tab "paid extension" in Tools & Settings > Licensing management
2 votesThank you for your input! We will consider this functionality for the upcoming releases if it becomes popular enough.
Everyone, please keep voting for this feature if you consider it important.
— AS
-
Plesk IP management logic of VPN interfaces/IPs
Please do the adjustments to the IP management logic of Plesk - currently it starts to manage VPN intefaces IPs by default, and it can cause issues with Apache and Nginx.
Currently it is possible to ignore such interfaces via panel.ini, but it has to be configured prior to adding the VPN interface to server. It would be great if Plesk would show such addresses in IP Addresses menu and ask if it should manage these addresses/intefaces or just ignore them.1 voteThank 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
-
Ability to set limit on the count of cron tasks in service plan settings
Some users creates a lot of cron tasks and can overload server. Please add Ability to set limit on the count of cron tasks in service plan settings
1 voteThank you for your input! We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
--
IG
-
Introduce Reseller login or username in Event parameters
Currently some Events in Plesk use the reseller contact name and the reseller login or username cannot be used.
For example, the event "Disk space limit for reseller account reached": https://docs.plesk.com/en-US/obsidian/administrator-guide/server-administration/event-parameters-passed-by-event-handlers.67897/#disk-space-limit-for-reseller-account-reached
The events related to Reseller tasks should use the reseller login or username to perform important tasks on the backend because the reseller login is unique, when there are Resellers with the same contact name this breaks the business logic implemented in the backend.
1 voteThank you for your input! 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.
—
IG -
Ability to create wildcard subdomain for domain alias
Ability to create wildcard subdomain for domain alias. For example, *.example-alias.com. It is required to have ability to configure redirects from {somename}.example-alias.com to main domain or another domain.
1 voteThank you for your input! 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.
—
IG
- Don't see your idea?