• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Migration Manager broken in Plesk 12.5.30

Dree

Basic Pleskian
The migration manager seems to be rebuilt and uses the API now.
The problem is that the migration manager does not check which port Plesk is running on, and 8443 is hardcoded. Running Plesk on a different port (for security reasons) is no longer supported when using Migration Manager.

Perhaps this could be configured when starting the migration?
 
Also, the migration manager is even slower than it was before. It's hanging on this command for a very long time:

/opt/plesk/python/2.7/bin/python /usr/local/psa/admin/sbin/modules//panel-migrator/plesk-migrator generate-migration-list /usr/local/psa/var/modules/panel-migrator/sessions/20151118100919/config.ini --skip-services-checks --async
 
This seems to be due to this command on the source server:
python /tmp/panel_migrator/hosting_analyser_agent.py -f -d /var/www/vhosts -n /tmp/panel_migrator/_rsync_network_report
It looks like it's reading all vhosts on the source server, which is going to take a while for 950 GB of data.
 
The migration manager seems to be rebuilt and uses the API now.
The problem is that the migration manager does not check which port Plesk is running on, and 8443 is hardcoded. Running Plesk on a different port (for security reasons) is no longer supported when using Migration Manager.

Perhaps this could be configured when starting the migration?
Now it could be configured only when using Plesk Migrator from CLI:
you could specify "plesk-port" option in target and source server sections in configuration file.
For example:
Code:
[GLOBAL]
source-type: plesk
source-servers: pfu
target-type: plesk

[plesk]
ip: 192.168.1.1
os: unix
# Plesk panel port on the target server
plesk-port: 8448

[pfu]
ip: 192.168.1.2
os: unix
ssh-password: 123qwe
# Plesk panel port on the source server
plesk-port: 8449
 
A command line utility for Migration Manager is actually very nice!
Is there documentation for this?
 
Back
Top