Skip to content

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.

For technical assistance, contact Plesk support
For questions, bug reports, discussions and free assistance, check our Forum and Facebook page
For additional information, see Documentation, Knowledge Base and Blog
Follow us on Twitter for more news on Plesk development

Off-topic posts will be removed from here

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

32 results found

  1. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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
    <plesk
    vhostsdir><username><maindomainname><docroot>
    In order the structure of virtual hosts and related users would be clearer,

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    open discussion  ·  IgorG responded

    Thank you for your feature request. We will consider the possibility of its implementation if it becomes sufficiently popular and in demand.

    IG

  6. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    open discussion  ·  IgorG responded

    Thank 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

  7. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    open discussion  ·  IgorG responded

    Thank 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

  8. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
2 Next →
  • Don't see your idea?

Feedback and Knowledge Base