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
-
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
-
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.
-
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
-
Migrating tool for Apache2 (Wordpress) linux server confs and sites.
Just reading with ssh root access /etc/apache2/sites-enabled/ and listing sites to be copied with their files and databases. Also Nginx sites.
It could be payable extension linked to Plesk license.1 voteThank you for your suggestion. Could you please explain your request in more detail so we can get better idea?
Thank you in advance.
-- SH
-
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.
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.
— 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
-
Add Auto Install SiteJet Website Option to Plesk Service Plans
Requesting a feature to add an option on the Plesk Service Plan "Additional Services" page to automatically install a SiteJet site. This would be similar to the same options that currently exists for WordPress from the WordPress Toolkit dropdown on that same page.
9 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
-
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
-
Plesk Migrator support the migration of Postgres databases
Provide to Migrator the ability to import postgres databases.
1 voteThank 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.
-- KvD
-
Identify live domains by verifying they're reachable
I have two servers that basically just mirror my domains. When I need to update the operating system on one of them, I migrate to the other and repoint the IP addresses. Fairly simple, DIY manual failover basically. (BTW, it would be great if this was more automated with regular incremental backups to the failover server.)
When I'm on the "inactive" failover server (when the domains are pointed at the other server's IP address), there is no indication that the domains are not reachable by the current server's IP address, which leads to confusion when switching between browser tabs to…
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
-
has ability to use rsync in transvhosts for data migration.
transvhosts script should have ability to migrate data with rsync instead of mv.
1 voteThank 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
-
Run pre-migration checks only for the domains to be migrated
Migrating more than one subscription causes a problem. The pre-migration check scans all users and all files on the backup disk, which takes quite a long time with a large number of backups (7TB+). Instead of scanning only the files of the users to be migrated (as when migrating a single subscription).
When I unmount the backup disk, Plesk doesn't scan it and the migration takes only a few minutes.
2 votes -
Ability to migrate websites added to 360 Monitoring via Plesk
The extension Monitoring allows adding websites on a Plesk server to 360 Monitoring but the websites remain linked to the source server after a migration.
It would be easier to migrate them, avoiding re-adding manually with losing the history2 votes -
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
-
Keep the collation MySQL settings during the migration
Migration of the databases from the old MySQL servers should keep the original collation of the tables. If the databases on the source server have the different collation setting these databases should have the same collation settings on the target server after the migration.
2 votes -
Plesk Migrator extension should be able to migrate server settings
Plesk Migrator should have options for migrating Server Settings. For example, have a checkbox for migrating the server timezone, Server hostname, DNS Template, etc.
8 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 the migration process to do multiple sessions when migrating to the same destination server
When I migrate from (Server B) to (server A) and the session is running, then I can no longer create a new migration session from (server C) to (server A)
I want to be able to migrate multiple process/session simultaneously so that the data migration process is more efficient.
1 vote -
Add a Warning to Plesk Migrator for when there are clients to be migrated with the same name in both the source and the target server.
E.g.: When migrating data from Server A to Server B, if the name of the client being migrated from Server A is the same as the name of an existing client on Server B, then Plesk Migrator imports such data into the existing client without giving a warning that the name of the client to migrate already exists on Server B.
1 vote -
Transfer DNSSEC configuration for a domain during migration
It would be great if transferring of generated keys and DB records of DNSSEC configuration for a domain during Migration will be implemented. Thus there would be no need to recreated them for each migrated domain.
6 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
-
migration manager respect ssh config
migration manger via ssh keys ignores config in /root/.ssh/config
I want to migrate from a server I have to access via a jumphost. I have ssh config so that I can just "ssh sourceserver" at the command line. The migration manager ignores the config and cant be made to access the source server.
1 vote
- Don't see your idea?