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

Resolved Plesk Migrator gives urlopen error

Wes

New Pleskian
Hi,

I am migrating from a Plesk server to a Plesk server.

During the migration the following error is shown:

Failed to connect to target Plesk server by Plesk API: <urlopen error [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:590)>

Couldn't find anything in the Plesk KB articles.
 
Looks like you have an issue with accessing target Plesk API. As a workaround you can configure Plesk Migrator to access target Plesk API via http instead of https, but it is not secure and available only via CLI. You need to add following lines into migration configuration file (config.ini):

[plesk]
...
plesk-protocol: http
plesk-port: 8880
...

Or, of you provide me access to you target server via private conversation we try to find and fix the root cause.
 
Hi. Plesk gives an error in cli mode and its saying that only https is allowed.

I will check if I can fix the "<urlopen error [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:590)>"error.

Thanks for your help.
 
[ERROR] Failed to connect to target Plesk server by Plesk API: Plesk error [1006]: Access to API via HTTP is not allowed due to security reasons. Use HTTPS instead.

This is the error I get.
 
I am sorry, I miss one another thing: you also need to allow access to Plesk API via HTTP by adding following lines into panel.ini:

[api]
allowPlainHttpAccess = true

But be aware: such configuration is insecure and very undesirable, so it could be used only as a workaround.
 
  • Like
Reactions: Wes
Back
Top