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

291 results found

  1. Add a column to Domain List to show if SSL is installed

    On the domain list, it would be helpful and save a LOT of time by having an additional column to show if a domain has SSL installed on it. See Image

    3 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. 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 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. SMTP Connection in SiteJet Builder

    Store SMTP connections in Sitejet Builder. phpsendmail is not a quality solution.

    6 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. Limit maximum crontab frequency and preventing cronjobs pile-up

    Plesk administrator should be able to limit the maximum crontab frequency allowed for user's crontab (example: deny the creation of cronjob that run more often than once in 5 minutes)

    Crontab pile-up should be prevented, so a user can't run a cron job if the same job isn't finished yet.

    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)

    Thank you for your idea.

    For the time being, please consider that a script that is started via cronjob, should check itself if another instance of the same script is already running, if there is a risk that a further instance causes problems. Crontab cannot check that. 

    Also, please be aware that users are not bound to repeat actions in a script in a while-loop. They can easily start a script every 10 minutes, yet let it run over and over again by just putting their content into a while-loop, maybe even wait a few seconds after each iteration. So limiting them to create cronjobs for only every n minutes will not keep users from executing scripts all the time.

    We'd like to hear more from other users what they think about the idea. If it still becomes popular, it might find its way into a future version of the…

  5. Add a "Service Plan" column in the Subscriptions list

    We absolutely miss a "Service Plan" column in the Subscriptions list.
    This is very annoying not knowing which Service Plan a Subscription is using.

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

    Thank 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

  8. Implement Alert System for nginx Service Failures in Plesk

    Introduce a feature in Plesk to automatically detect and notify administrators through Plesk panel (if accessible) and email alerts when the nginx service fails to start or encounters any issues to ensure immediate awareness and prompt resolution.

    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)
  9. 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 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. 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 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. 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

    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. 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 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)
  13. 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 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)
  14. 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 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)
  15. 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 installation

    4 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)
  16. 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 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)
  17. 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 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)
  18. 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.

    Reference: https://docs.plesk.com/en-US/obsidian/administrator-guide/server-administration/event-parameters-passed-by-event-handlers.67897/#plesk-user-logged-in

    Not sure about the category, so please replace if there's a better place for this suggestion.

    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)
  19. Convert existing alias to domain

    Convert existing alias to domain

    5 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)
  20. 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 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)

    Thank 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

← Previous 1 3 4 5 14 15
  • Don't see your idea?

Feedback and Knowledge Base