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

unknown migration option in plesk 12.5.30

Linulex

Silver Pleskian
At the migration settings page there is a new option

Check operability Check the operability of services after migration (will increase the migration time)

What does this do ???

If i use the help on the migration settings page i go to this page

https://docs.plesk.com/en-US/12.5/a...ation/migration-from-other-hosting-platforms/

When i follow the link Deployment Guide. on this page i get an error 404, page not found.

https://docs.plesk.com/en-US/12.5/a...//en-US/12.5/administrator-guide/about-plesk/

regards
Jan
 
It seem the process migration test website when have been migrated (even if dns of domain not working with this server), in resume logs I see sometime that site have return error message 500 if there is some error.
 
Sorry, but documentation still under developing and construction. We are going to completely replace migration documentation in 2-3 days.
 
Well, there is no problem with migration, it's works fine (I am migrating a lot of old plesk 8.6 domains to new plesk 12.5)
 
I am glad to inform you that Plesk Migrator initial guide was published at https://docs.plesk.com/en-US/12.5/migration-guide/introduction/. Not all available features, scenarios and options are described at this moment, but this guide will be expanded and improved on an ongoing basis.

That's about post migration checks, following aspects of domains availability will be checked:
  • Websites
  • Mail
  • DNS
  • Databases
  • System users
In scope of websites availability, following aspects will be checked:
  • Response code and title of domain's the home page
  • Response codes and titles of pages, linked with the home page
  • Title pages of APS applications registered in Plesk and placed on the domain
If a site is configured to use SSL, HTTPS addresses are also checked

Error will be reported in following cases:
  • Requested page is unavailable on target
  • Source and target HTTP response codes are different
  • Target HTTP response code is 4xx or 5xx (except 401 both on source and target - it is valid in case of password-protected area)
 
There are several key benefits of Plesk Migrator:
  • Better error reporting - Solution for each issue, attention on severity (impact) and details for debugging
  • Better isolation - Failure on one subscription does not affect others
  • Better robustness - Repeat command on failures to avoid temporary network or reliability issues
And more things like:
  • Pre-checks - Check system services, check ability to transfer data between source and target servers), check capability of target server to restore hosting settings of transferred domains
  • Post-checks - Check domains availability after migration and many other things: databases, mail, DNS, etc
  • Move to production - Provide ability to sync web and mail content, transfer databases, and finally enable DNS forwarding on source server for migrated domains automatically
 
Back
Top