Unable to start migation: Failed to check Plesk API connection to target Plesk server: 400: Bad request

Created:

2016-11-16 13:06:51 UTC

Modified:

2017-08-19 03:09:24 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Unable to start migation: Failed to check Plesk API connection to target Plesk server: 400: Bad request

Applicable to:

  • Plesk 12.5 for Windows

Note: This article has the reference to the issue with the fix available:

  • #PMT-2794 "Migration on Windows failed when IPv6 was used for connection to a target Plesk server."
    Fixed in:
Please consider updating your server:

Symptoms

Unable to start migration, the following error can be found in %plesk_dir%var\\modules\\panel-migrator\\sessions\\your_session_id\\debug.log of Plesk Migrator:

=|2016-04-18_19:24:03,292|D|MT|parallels|||PleskConnectionCheckError: Failed to check Plesk API connection to target Plesk server: HttpClientError(HTTP Error 400: Bad Request, '<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">\\r\

Bad Request\r\\r\

Bad Request - Invalid Hostname

\r\


HTTP Error 400. The request hostname is invalid.

\r\ \r\') +|2016-04-18_19:24:03,296|E|MT|parallels|||Failed to check Plesk API connection to target Plesk server: HttpClientError(HTTP Error 400: Bad Request, '<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">\r\Bad Request\r\\r\

Bad Request - Invalid Hostname

\r\


HTTP Error 400. The request hostname is invalid.

\r\ \r\').

Cause

Plesk is trying to use IPv6 when checking API connection.The issue was caused by software issue with id #PMT-2794 , which was fixed in Plesk Migrator version 1.12. (Plesk 12.5.30 MU#39) https://docs.plesk.com/release-notes/12.5/change-log/ .

Resolution

Apply the latest MU.

Have more questions? Submit a request
Please sign in to leave a comment.