• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Unable to update . An error occurred while processing your key. You can try updating

dcrouch

New Pleskian
#Getting the following error in email:

Unable to update . An error occurred while processing your key. You can try updating it later.

# Ran test from http://kb.parallels.com/en/111198 and received the following:

/usr/local/psa/bin/sw-engine-pleskrun -f ./test.php
ERROR: Zend_Exception
No entry is registered for key 'log'

0: Registry.php:147
Zend_Registry::get(string 'log')
1: common_func.php3:5268
notifyAboutKeyUpdateResults(string '', boolean false, string 'No entry is registered for key 'log'')
2: test.php:20

cat /usr/local/psa/version
11.0.9 CentOS 6 110120608.16
 
Try upgrade with autoinstaller with --ignore-key-errors option. When upgrade successfully completed you may upgrade license in Plesk GUI.
 
Following: https://solutions.hostmysite.com/in...grading-plesk-from-11-to-115-via-command-line

We receive the following.

/usr/local/psa/bin/ipmanage --reread && wget https://autoinstall.plesk.com/plesk-installer && chmod +x plesk-installer
The license key is invalid. In order to use the Panel, please obtain and install a new valid license key.
Your license key has expired. To continue using your Panel, you must purchase a non-expiring commercial license key.

Seems the license has expired.

Next license key update Mar 21, 2014
Key expiration date Mar 31, 2014
The expiration date will be automatically extended on Mar 21, 2014. For the automatic update you must allow connections to ka.swsoft.com. For more information, refer to the following help topic.

A dig on ka.swsoft.com shows:

;; ANSWER SECTION:
ka.swsoft.com. 3600 IN CNAME ka.parallels.com.
ka.parallels.com. 600 IN A 77.245.23.80

I have added 77.245.23.80 to the allow list in firewall. Hopefully this will prevent this error from reoccurring.
 
Back
Top