• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Forwarded to devs Cannot migrate, Overall - Fetch configuration data from Plesk servers stucks

Nils Putnins

New Pleskian
TITLE:
Cannot migrate, Overall - Fetch configuration data from Plesk servers stucks​
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk Onyx​
PROBLEM DESCRIPTION:
Trying to migrate Plesk from https://ilze.influent.solutions:8443/ to http://185.185.25.226:8880/ and it keeps on sticking with the configuration fetching.​
STEPS TO REPRODUCE:
Provide the SSH credentials for root etc., and press migrate​
ACTUAL RESULT:
Stuck​
EXPECTED RESULT:
Migrated​
ANY ADDITIONAL INFORMATION:
​
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Help with sorting out​
 
Any additional details, logs, error messages, a full specification of "PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE" at least, etc?
 
What about full specification of "PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE" for target and source Plesk servers?
 
Target server: Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-20-generic x86_64), Plesk Onyx 17.9.9
Source server: Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-30-generic x86_64), Plesk Onyx Version 17.8.11 Update #35
 
According to the logs, developers can't conclude that migration got stuck: pre-migration checks were finished successfully, there are several warnings, but none of them are critical to proceed with the migration. There are no other errors in the logs.

Could you please clarify, how exactly migration gets stuck? Maybe screenshots, video, or more detailed explanation - which buttons you click exactly, and how much time you wait for results?

Anyway, I think that the request could be processed more quickly with the help of Plesk Support, especially if you provide them with access to the servers and the panels. Why not add a request for them?
 
Back
Top