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

Migration from 10.3.1 to 10.3.1 won't work: SNI is not supported

SacAutos

Regular Pleskian
I need to move an ecommerce website from one server to another. However, no matter what I try, I can't get it to go. Here's the error message that the migrator gives me:

Warning: phosting "website.com"
SNI is not supported. SSL certificate will not be restored on website.com

Error:
Failed deployment of client WebSite

(I've obviously changed the name of the domain to "website".) The domain is "owned" by a customer that has it and an email-only domain within it. There is also an error that follows about being unable to create the account because the email address already exists. I don't believe that's relevant to my main problem, as I've moved domains before with that error and the domain still deployed.

This is a big problem. Does anybody have any ideas on how to get around this? I've even tried disabling the secure certificate for the domain and moving it to a shared IP address and it STILL failed.

HELP!!
 
It turned out to be the customer that blocked it

Well, I've answered my own question. I was about to move the site manually when I had an idea to try moving the domains without moving the customer that owned them. That seemed to work. I recreated the customer info at the other end and reassigned the subscriptions to it. Annoying but it worked.
 
Back
Top