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
59 results found
-
Migrate AWStats customizations
Currently any customization made into AWStats configuration files (for domain /usr/local/psa/etc/awstats/* or server-wide /etc/awstats/awstats.conf), for example, language changing are not migrated. It would be nice feature to add ability to migrate such settings, so that users do no have to turn it back manually
6 votes -
website importing with different ip for ftp and www
The current website import function only allows entry of the source domain name.
I need to specify the ftp server details separately as for some hosts the ftp server is on a different ip to the website and the current import function fails as it fails to access either the website or ftp server depending on which info was entered as the source domain.6 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.
— AY
-
Provide migration licenses 24/7, not only on workdays
Often times migrations are done on weekends. I'd like to be able to get a migration license as described in https://support.plesk.com/hc/en-us/articles/12388069544215-How-to-get-Plesk-Web-Host-edition-trial-license-for-migration at any time. The current workflow where this can only be requested and handled on weekdays during business hours can block my own workflow, e.g. when I have and emergency and absolutely must migrate.
4 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.
— AA
-
Migrate SpamAssassin training database to a new server when using Plesk Migrator
When migrating data to a new server using Plesk Migrator, all SpamAssassin trainings are lost, hence users receive more spam on the new server than they did before. It would be good to migrate SpamAssassin training content to the new server.
4 votesThank 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
-
Set LVE to "unlimited" for users created temporarily on Migration to speed up Migration on CloudLinux
The CloudLinux employs several techniques to limit performance, among others "LVE" limits. These are limits on resource usage such as CPU speed, RAM, I/O speed, number of processes, etc.. It is an established fact that the Plesk Migrator is capable of modifying CloudLinux components to allow the Migrator to do it's job, like disabling CageFS for the source user and target server. So, it stands to reason that the Plesk Migrator could also modify these LVE limits to improve performance of the data-transfers to the target server. The I/O limit of 1 MB/s is an LVE default limit for users…
4 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
-
Allow multi-thread options in Plesk Migrator to speed up huge migrations
The Plesk Migrator tool is very limited when migrating a big amount of subscriptions, databases and mails.
Checking the CPU usage when performing a migration, Plesk Migrator utilities are not reaching 20% of the CPU because this tool is not supporting multi-threading.
Therefore, due to this limitation, a huge migration can take a few days or even more than a week to be completed.
If Plesk Migrator would use the full capabilities of the hardware available in our servers, the migration can be faster and match our migration deadlines.
It would be great that a few options in panel.ini or…
4 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 -
Use of CSV for account detail upload
I would have started using plesk right away . Sorry to say I need to be able to upload a few thousand account details via CSV files
4 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.Until .csv import is available, we would suggest running bulk operations in CLI or XML API.
—
IG -
forwarding HTTP(S) requests from the source server to the target
In case of migration and the customer use 3rd party Name servers, it would be useful to be able to redirect all requests that come to old ip to the new server ip.
This will helpp to avoid downtime4 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 -
Better migration of "PHP from OS vendor" parameters
Please consider the following use case:
- testdomain.tld on a CentOS target server is using "PHP from OS vendor" version 5.3;
- The destination server is Ubuntu 14, with newer version of PHP from OS vendor, so you install PHP 5.3 with Plesk Installer;
- The migrated testdomain.tld will have different PHP parameters that may cause disruption of the website.An example: PHP short open tag is enabled by default on PHP from CentOS repository, but is disabled on PHP 5.3 handler installed via Plesk Installer. If a PHP code uses short open tags, the script will stop working. Plesk…
4 votesThe problem may be in that destination server will not be able to use specified version of PHP for the migrated domain because of absence in official OS vendor’s repository. To prevent this kind of problems we see improvement of pre-migration checker which will notify you about possible post-migration issues. After that, the server administrator must solve the problem himself. The automatic resolving of these incompatibilities looks very dangerous.
—
IG -
Possibility to convert Plesk server with AlmaLinux 8 to AlmaLinux 9 OS
Add possibility to convert Plesk server with AlmaLinux 8 to server with AlmaLinux 9 OS
3 votesThank 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
-
Update GUID during process migration
Update GUID during process migration. Plesk migration tool needs to be updated to do this. This will avoid any issues with GUID conflicts.
3 votesThank 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
-
Mail Importing improvement
Within the "Mail Importing" section it would be helpful to show percentages of work (and other stats) and a remove button to hide old unnecessary import requests.
Best regards.3 votesThank you for your feature request. We will consider the possibility of its implementation if it becomes sufficiently popular and in demand.
—
IG -
Make Plesk Migrator also migrate cronjobs for domain while migrating from cPanel
Make Plesk Migrator also migrate cronjobs for domain while migrating from cPanel. This decrease the number of manual actions that required to perform by customer after the migration.
3 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 -
Service plans migration from cPanel
Hello,
Please add possibility to migrate service plans (packages) during migration from cPanel.
Currently, Service plans are not automatically created on Plesk servers.3 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 -
Mail filters should also be migrated when using the plesk migrator
Mail filters should also be migrated when using the plesk migrator
/var/qmail/mailnames/example.com/jdoe/sieve/*
3 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 -
Ability to ignore missing PHP on target warnings for Migrator
Add the ability to ignore missing PHP on target warnings for Migrator as it is right now, when that happens, all the domains end being marked with a "Warning" and they need to be checked one by one
3 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 -
Add an opportunity to migrate additional FTP accounts with 'crypt' password via Plesk Migrator
Add an opportunity to migrate additional FTP accounts with 'crypt' password via Plesk Migrator
Right now, these accounts are not migrated because Plesk cannot store hashed passwords for system users
3 votes -
Plesk Migrator should be able to migrate customers, Resellers and Service Plans that do not have any Subscriptions attached
Service Plans with no Subscriptions assigned as well as Resellers and Customers that do not have any Subscriptions assigned are not migrated via the Plesk Migrator to the new Plesk server by design, because they are considered obsolete and unnecessary.
Yet in many cases, such a transfer of data in necessary, due to which an option that allows this to happen should exist.
2 votesThank 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
-
Change domain name during migration
Add an option to Plesk Migrator allowing to change names of subscription/domains/databases, etc. during migration. For example on source server subscription name is example.com and on target it should be example.net. It is better than manual rename of subscription and both websites can be live on different servers
2 votesThank 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.
-
Improve speed of Migration Manager re-sync process
Because there is a re-sync option, the overall speed of the initial data transfer with Plesk Migration Manager (PMM) doesn't matter that much (to us), however when re-syncing the speed of the process is super important because domain web and email services on the source server must be down/offline to prevent data inconsistencies. The re-sync process currently takes roughly 1 hour per 100 subscriptions.
Here's three ways the re-sync process could be improved to minimize web and email service downtime:
# 1. Fetch configuration data ONCE
PMM batches 5 subscriptions at a time, and prior to each batch of 5,…
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
- Don't see your idea?