• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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