2068 results found

1. Add the Flutter support to Plesk

   Please add the the Flutter support to Plesk

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Plesk (general)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.

   Everyone, please continue voting for this feature if you consider it important.

   -- SH

2. Add the Vite support to Plesk

   Please add the Vite support to Plesk

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Plesk (general)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.

   Everyone, please continue voting for this feature if you consider it important.

   -- SH

3. ability to toggle WordPress REST API endpoints

   I've recently discovered that by default, WordPress exposes a REST API endpoint at /wp-json/wp/v2/users which can be exploited to enumerate users. While I have found a workaround by creating a custom rewrite rule in IIS to block access to this endpoint, I believe this should be a built-in feature of the WP Toolkit.

   I propose that Plesk add an option within the WP Toolkit to easily enable or disable access to specific REST API endpoints, such as /wp-json/wp/v2/users. This would provide an additional layer of security for WordPress sites and make it easier for administrators to protect their websites.

   I believe that this feature would be highly beneficial to the Plesk community and would contribute to a more secure WordPress hosting environment.

   I've recently discovered that by default, WordPress exposes a REST API endpoint at /wp-json/wp/v2/users which can be exploited to enumerate users. While I have found a workaround by creating a custom rewrite rule in IIS to block access to this endpoint, I believe this should be a built-in feature of the WP Toolkit.

   I propose that Plesk add an option within the WP Toolkit to easily enable or disable access to specific REST API endpoints, such as /wp-json/wp/v2/users. This would provide an additional layer of security for WordPress sites and make it easier for administrators to protect their websites.

   I… more

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  WP Toolkit  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.

   Everyone, please continue voting for this feature if you consider it important.

   -- SH

4. Prohibit creation of domains that resolve to another server

   Prohibit creation of all domains that resolve to other servers.
   Currently need to add the domains one by one, need to apply to all possible domains.

   15 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Plesk (general)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.

   Everyone, please continue voting for this feature if you consider it important.

   -- SH

5. URL-based branding logos

   I suggest enabling Plesk to allow different branding logos in the login screen and the top left corner of the session, depending on the full-qualified hostname used to reach the server. For example, if a server can be reached through 2 different names, the idea would be to be able to set a default branding logo and have alternative ones depending on the URL used to connect to the server. Here's an example:

   plesk.domain1.com -> main logo (default)
   plesk.domain2.net -> alternative logo 1
   hosting.domain3.co -> alternative logo 2
   any other aliases/URLs -> main logo (default)

   •  

   •  

   •  

   •  

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Plesk (general)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.

   Everyone, please continue voting for this feature if you consider it important.

   -- SH

6. avoid Plesk panel update when a backup is running

   Plesk updates the panel while a backup process is running. This can interrupt a backup, for example:

   Error: Server "<hostname>"
   Value at Plesk\backup\Agent\Schema\Backup\Admin\AdminAType\PreferencesAType -> Plesk\backup\Agent\Schema\Backup\Admin -> Plesk\backup\Agent\Schema\Backup\MigrationDump is expected to be an object of class Plesk\backup\Agent\Schema\Backup\ScheduledTasks but is of type array
   Error:
   Unable to create the remote backup: Repository error: Failed to open the file '/usr/local/psa/PMM/tmp/pmm-de-tmp-repo-NnwqUP/backuplickey002410212254.tzst': No such file or directory

   but I have observed other similar issues before. On large servers, a full backup can run for many hours. If it fails, many hours of high cpu load are lost and the backup must be repeated the next night. It would be better to move the Panel updates dynamically forward into a time frame when the software detects that no backups are running.

   Plesk updates the panel while a backup process is running. This can interrupt a backup, for example:

   Error: Server "<hostname>"
   Value at Plesk\backup\Agent\Schema\Backup\Admin\AdminAType\PreferencesAType -> Plesk\backup\Agent\Schema\Backup\Admin -> Plesk\backup\Agent\Schema\Backup\MigrationDump is expected to be an object of class Plesk\backup\Agent\Schema\Backup\ScheduledTasks but is of type array
   Error:
   Unable to create the remote backup: Repository error: Failed to open the file '/usr/local/psa/PMM/tmp/pmm-de-tmp-repo-NnwqUP/backuplickey002410212254.tzst': No such file or directory

   but I have observed other similar issues before. On large servers, a full backup can run for many hours. If it fails, many hours of high cpu load are lost and the backup must be repeated the… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Plesk (general)  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.

   Everyone, please continue voting for this feature if you consider it important.

   
   

   In the meantime, you may consider scheduling Plesk's major updates for days/times when backup jobs are not expected to run.

   -- SH

7. Usage of "Quick Preview" DNS should be made more clear.

   The fact that Plesk must be the DNS server for the "Quick Preview on a domain in Plesk" option should be underlined and more prominent in the interface. The necessity of a Wildcard SSL cert should be clearer too. That would help your clients and avoid some tickets to Plesk support.

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Usability and UI  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.

   Everyone, please continue voting for this feature if you consider it important.

   -- SH

8. Improve the Backup Manager for when it freezes or aborts when using S3/Scaleway

   Plesk should have a native mechanism to detect when a backup job is stuck; helping to manage backups more efficiently without relying on manual intervention.

   Plesk should allow backups to automatically resume from the point where they fail, rather than starting from the beginning; saving time and resources, especially for large backups.

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Backup / Restore  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.

   Everyone, please continue voting for this feature if you consider it important.

   -- SH

9. Be able to change URL structure of domains in Preview mode

   The preview in "Quick Preview" mode only allow a basic preview, without usage of SSL/TLS certificates, as the URLS begin with the IP address, like this:
   http://111.222.333.444/plesk-site-preview/www.some-website.com/

   The "Quick Preview on a domain name in Plesk" could be improved. It allows to select an existing domain as a "support" for previewing websites. This sounds promising, as a SSL/TLS certificate already exists on this domain name.

   But the problem is that the preview Urls generated by Plesk now use a different structure based on subdomains, like this: http://some-website.com.212-83-133-74.preview-domain.com/

   This is rendering this functionality cumbersome : need to add this "some-website.com.111-222-333-444" subdomain to the DNS records of "preview-domain.com", and need to re-emit the SSL/TLS certificate for "preview-domain.com" if not a wildcard.

   This ticket suggest that Plesk allows us to be able to use the "Quick Preview on a domain name in Plesk" withs URLS of this structure :
   http://preview-domain.com/plesk-site-preview/www.some-website.com/

   The preview in "Quick Preview" mode only allow a basic preview, without usage of SSL/TLS certificates, as the URLS begin with the IP address, like this:
   http://111.222.333.444/plesk-site-preview/www.some-website.com/

   The "Quick Preview on a domain name in Plesk" could be improved. It allows to select an existing domain as a "support" for previewing websites. This sounds promising, as a SSL/TLS certificate already exists on this domain name.

   But the problem is that the preview Urls generated by Plesk now use a different structure based on subdomains, like this: http://some-website.com.212-83-133-74.preview-domain.com/

   This is rendering this functionality cumbersome : need to add this "some-website.com.111-222-333-444" subdomain… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Web / SSL  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

   Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.

   Everyone, please continue voting for this feature if you consider it important.

   -- SH

10. Listen on all IPs for all vhosts

    Let the webserver for all vhosts listen on all IPs on a server. With Apache httpd you can use * instead of the IP (or list all IPs on a server). This would make it easier to migrate users between servers without having to manually check the IP to update the (external) DNS. This would also make it possible to prepare everything for IPv6 at the same time as you would only need to add AAAA records after this step.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Web / HTTP functions  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Allow to postpone changes to DNS zone

    Sometimes it is not convenient to reload all zones on every change, so it would be helpful to have an option to apply changes either immediately, or at a designated time.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  DNS  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.

    Everyone, please continue voting for this feature if you consider it important.

    -- SH

12. Enhancing the visibility of protection status in WordPress Toolkit

    Recently, Plesk added a vulnerability status feature to the WordPress Toolkit, which is a great step forward. However, both the vulnerability status and the protection status are currently accessed through the same link, making it harder to find the protection details quickly.

    It would benefit users, especially those less familiar with these features, if Plesk were to separate these into two distinct links. This way, the protection status would be more visible and easier to access, helping users stay informed about the security of their WordPress installations without extra steps.

    For example, the current "Security: Fix vulnerabilities" entry in the status table could be split into two separate lines:

    • Security Measures: Review security settings
    • WordPress Vulnerabilities: Fix detected vulnerabilities

    Both options would lead to their respective sections, making it easier for all users, especially beginners, to find and address both types of security issues. Clearer access to these statuses could also address the concern about the perceived gaps in protection, such as with xmlrpc.php, making Plesk's security offerings feel more complete and transparent.

    Recently, Plesk added a vulnerability status feature to the WordPress Toolkit, which is a great step forward. However, both the vulnerability status and the protection status are currently accessed through the same link, making it harder to find the protection details quickly.

    It would benefit users, especially those less familiar with these features, if Plesk were to separate these into two distinct links. This way, the protection status would be more visible and easier to access, helping users stay informed about the security of their WordPress installations without extra steps.

    For example, the current "Security: Fix vulnerabilities" entry in the… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  WP Toolkit  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.

    Everyone, please continue voting for this feature if you consider it important.

    -- SH

13. Add option to create temporary admin account in WordPress Toolkit for support access

    Our customers regularly ask us to assist by logging into their WordPress site. It would be very helpful if the WordPress Toolkit had an option to create a temporary additional admin account, allowing us to log into their WordPress website securely for troubleshooting or support.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  WP Toolkit  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.

    Everyone, please continue voting for this feature if you consider it important.

    -- SH

14. Custom color wheel for private branding

    Currently, Plesk provides only two options for branding customization, which can be limiting for users managing multiple internal companies with distinct branding needs. I propose the addition of a custom color wheel for private branding in Plesk.

    This feature would allow administrators to choose from a broader range of colors, offering more flexibility in aligning the Plesk interface with specific company branding. For users handling multiple companies, this customization option would be a significant improvement, making it easier to differentiate between brands.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Usability and UI  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.

    Everyone, please continue voting for this feature if you consider it important.

    -- SH

15. Display MySQL/MariaDB versions with warnings for unsupported versions in the Dashboard

    Many users run unsupported versions of MySQL or MariaDB, leading to issues such as failed updates or database errors. Since Plesk only supports LTS versions of MySQL/MariaDB, it's important to make this clear to administrators.

    I propose adding the following improvements to the Dashboard:

    • Display the installed MySQL/MariaDB version directly on the Dashboard.
    • Include warnings for unsupported MySQL/MariaDB versions, with a color-coded alert system similar to the OS warnings.

    These warnings should also link to support articles that explain the importance of running supported database versions and provide instructions for updating to a supported version.

    By implementing this, administrators can easily identify when their database version is outdated and take appropriate steps before it causes issues.

    Many users run unsupported versions of MySQL or MariaDB, leading to issues such as failed updates or database errors. Since Plesk only supports LTS versions of MySQL/MariaDB, it's important to make this clear to administrators.

    I propose adding the following improvements to the Dashboard:

    • Display the installed MySQL/MariaDB version directly on the Dashboard.
    • Include warnings for unsupported MySQL/MariaDB versions, with a color-coded alert system similar to the OS warnings.

    These warnings should also link to support articles that explain the importance of running supported database versions and provide instructions for updating to a supported version.

    By implementing this, administrators can… more

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Usability and UI  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.

    Everyone, please continue voting for this feature if you consider it important.

    -- SH

16. Add warnings for unsupported operating systems in the Dashboard

    Many Plesk users continue to run outdated operating systems, which often results in non-functional repositories, failed updates, or even security risks. While the current Dashboard displays "Server Information," including the OS version, it lacks any warnings about the support status of the operating system.

    I propose adding the following to the Dashboard:

    • Display an orange warning when the OS has 6 months or less of support remaining.
    • Display a red warning when the OS is end-of-life and no longer receives updates.

    These warnings should include links to support articles explaining the risks and offering steps to update or migrate the server to a supported version.

    Adding these color-coded warnings will help administrators stay informed and take action before encountering major problems due to unsupported operating systems.

    Many Plesk users continue to run outdated operating systems, which often results in non-functional repositories, failed updates, or even security risks. While the current Dashboard displays "Server Information," including the OS version, it lacks any warnings about the support status of the operating system.

    I propose adding the following to the Dashboard:

    • Display an orange warning when the OS has 6 months or less of support remaining.
    • Display a red warning when the OS is end-of-life and no longer receives updates.

    These warnings should include links to support articles explaining the risks and offering steps to update or migrate the… more

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Usability and UI  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.

    Everyone, please continue voting for this feature if you consider it important.

    -- SH

17. restore files from .trash of filemanager

    It is would be great to have ability to restore files from .trash folder not manually, but with some tools that remembers path of deleted file. Or have ability to see original folder where file is deleted..

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  FTP  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.

    Everyone, please continue voting for this feature if you consider it important.

    -- SH

18. SiteLock Website Security extension for Linux and Windows

    Would like to have a Plesk SiteLock extension for Windows and Linux platforms

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.

    Everyone, please continue voting for this feature if you consider it important.

    -- SH

19. Suspend database when subscription is suspended

    When a site is suspended, the database and database user isn't suspended.
    This can be used by a customer to consume database resources from another unsuspended subscription.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Databases  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.

    Everyone, please continue voting for this feature if you consider it important.

    -- SH

20. Bypass MFA when using session token to login

    Currently, when session tokens are used for logging into Plesk and MFA is enabled, the MFA code is still required.

    It would be useful to have an option to bypass MFA when using session tokens to log into Plesk.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Plesk (general)  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    open discussion  ·  AdminPlesk Staff (Community Manager, Plesk International GmbH) responded

    Thank you for your input! We will consider this functionality in upcoming releases if it becomes popular.

    Everyone, please continue voting for this feature if you consider it important.

    -- SH