58 results found

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

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

   — AY

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

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

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

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

6. 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 in the Plesk Migrator settings would allow us to set how many CPUs to use.

   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… 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  ·  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.
   —
   IG

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

8. 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 downtime

   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.
   —
   IG

9. 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 Migrator should handle this case.

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

   4 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

   The 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

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

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

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

13. 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 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  ·  IgorG responded

    Thank you for your feature request. We will consider the possibility of its implementation if it becomes sufficiently popular and in demand.
    —
    IG

14. 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 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  ·  IgorG 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

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

    —
    IG

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

    —
    IG

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

    2 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

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

    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

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

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