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

Upgrading Plesk 8.6 to 9.0 without a valid license key

R

Rodorm

Guest
Hi all,

is it possible to upgrade Plesk 8.6 to 9.0.1 without a valid license key? We have two license keys for 8.6 and 9.x, but Plesk doesn't accept any of them. We were suggested to continue with the upgrade and to add the new license key afterwards. Is that possible without all the customers and domains being deactivated or even deleted? We have many custormers on this server and get into deep trouble if all their domains were deactivated or deleted. The error message we get (translated from German) is:

XMLRPC remote call failed: HTTP error #-1 occurred error: connection to the licensing server failed.

Any ideas?

Thanks in advance!
 
Hi,

Please, make sure port 5224 is open for outgoing connection with licensig server ka.parallels.com.
If you have SUS support on your license key (http://kb.odin.com/en/111)
so the key will be update to 9.x version along with Plesk upgrade.

Also, Plesk CP does not suspend/delete clients or domains during upgrade.
 
Thanks for your answer. We don't have any firewall active, so the port should open when the application tries to connect to the licensing server, shouldn't it?
 
Back
Top