58 results found

1. Plesk Migrator should be able to use a sudo user's key and su to root to perform the migration

   Plesk Migrator should be able to use a sudo user's key and su to root to perform the migration. This is to be done inline with VPS provider security recomendations.

   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

   1 comment  ·  Migrations  ·  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

   Submit Rating

2. Automatically issued certificates (Let's Encrypt) are not properly migrated using Plesk Migrator

   Currently, Plesk Migrator does not properly transfer automatically issued certificates (Let's Encrypt).
   This request is to improve the migration process and ensure that automatically issued certificates (Let's Encrypt) are fully functional after migration.

   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  ·  Migrations  ·  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

   Submit Rating
   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. 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

   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  ·  Migrations  ·  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

   Submit Rating
   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. 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 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  ·  Migrations  ·  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

   Submit Rating
   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. 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 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  ·  Migrations  ·  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

   Submit Rating
   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.

6. 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 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  ·  Migrations  ·  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

   Submit Rating
   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

7. 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 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  ·  Migrations  ·  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

   Submit Rating
   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 will be popular.

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

   — AA

8. 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, it sits for 3-4 minutes saying "Fetch configuration data from Plesk servers"

   Presumably it's grabbing info on the next 5 subscriptions.

   PMM should fetch configuration data for all subscriptions in the queue at the start of the re-sync, as we don't have to block access to the server during that part of the process. Once it actually moves on to copying data from the subscriptions, we would then start the downtime portion.

   # 2. Always keep 5 processes running

   Currently PMM batches 5 subscriptions at a time, however as the data transfers for each subscription complete, it does not start additional subscription migrations to keep 5 going at all times. That means it can be sitting migrating a single subscription (ex: with larger databases or more emails) and nothing else happening, which wastes time.

   If (1) above is implemented, then PMM could always keep 5 subscriptions migrating simultaneously, such that when one completes, another subscription migration begins.

   Even if (1) above is not implemented, it could at least start Fetching configuration data for the next 5 subscriptions after the first subscription (in the prior group) finishes migrating. That way the 5 processing slots would look something like this after the first subscription finishes migrating:

   1. Subscription data copy
   2. Subscription data copy
   3. Subscription data copy
   4. Subscription data copy
   5. Fetch configuration data for next batch of 5

   3. Allow admin to configure the number of subscriptions to migrate in each batch

   Rather than a fixed value of 5, why not allow the admin to configure that. If, for example, the server has 16 cores, it would make sense to allow something like 12 simultaneous subscriptions to re-sync at once.

   Or Plesk could monitor the server load and, if it's less than the number of cores on the server, automatically scale the number of simultaneous subscription migrations to match.

   ---

   Implementing these options could result in reducing the total re-sync time by half or potentially more.

   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,… 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  ·  Migrations  ·  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

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

   Thank 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

9. 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 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  ·  Migrations  ·  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

   Submit Rating
   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. 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 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  ·  Migrations  ·  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

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

    Thank 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

11. Plesk Migrator support the migration of Postgres databases

    Provide to Migrator the ability to import postgres databases.

    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  ·  Migrations  ·  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

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

    Thank 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

12. 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 manage both servers. This should really be something that's communicated in the dashboard.

    Basically, I wants a heads up of some kind in the domain list (/smb/web/view) and on the individual domain control panels (/smb/web/overview/id/9/type/domain).

    "Is this site currently reachable via this server's public IP address? [YES/NO]"

    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… 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  ·  Migrations  ·  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

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

    Thank 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

13. has ability to use rsync in transvhosts for data migration.

    transvhosts script should have ability to migrate data with rsync instead of mv.

    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  ·  Migrations  ·  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

    Submit Rating
    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. 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

    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  ·  Migrations  ·  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

    Submit Rating

15. 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 history

    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  ·  Migrations  ·  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

    Submit Rating

16. 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 that are not assigned to a Service Plan. Our suggestion is that the Plesk Migrator sets the LVE to "unlimited" for all users that are created specifically and temporarily for the migrator to do it's job. This can be done via a CLI command: lvectl set-user <username> --unlimited We suspect that the Plesk Migrator has knowledge of which temporary username(s) are created, so it would be an easy job to set the LVE limits for that newly created temporary user to unlimited.
    This would greatly increase speed of the transfers.
    This would only be needed if the detected OS on the target and/or source is CloudLinux ofcourse.

    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… 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

    0 comments  ·  Migrations  ·  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

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

    Thank 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

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

    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  ·  Migrations  ·  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

    Submit Rating

18. 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 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  ·  Migrations  ·  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

    Submit Rating
    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 is popular. Everyone, please continue voting for this feature if you consider it important.  

    
    

    --

    IG

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

    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  ·  Migrations  ·  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

    Submit Rating

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

    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

    0 comments  ·  Migrations  ·  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

    Submit Rating
    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 is popular. Everyone, please continue voting for this feature if you consider it important.

    --

    IG