• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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