• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • 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.

Key question

D

Dimka

Guest
Few days ago I have updated my server to a latest vision and on the boot I have an error that key authorization failed and despise that error plesk starts ok and today I have noticed another admin with ip 127.0.0.1

Please advise what could possibly cause plesk key authorization and who can access my control panel ? I am the only one who has password and on my license key .Also I have Key expiration date April 17, 2005 .I have owned license with 100 domains , shouldn’t key be with unlimited expiration date?

Thanks in advance
 
Hi,

Did you find any info about the key expiration date?

I have the same problem and I think there shouldn't be any expiration date for it, like it was before the upgrade ...

Thanks.
 
Back
Top