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

Expired License and Forced Upgrades?

  • Thread starter Victor AlexanderD
  • Start date
V

Victor AlexanderD

Guest
Hello,

We obtain our Plesk licenses through our server provider. Occasionally a license will fail to update with a "Key Authorization Problem" or similar error. This has been a problem since the 7.x days when we started using Plesk. Usually the provider would just install a new license and everything would be fine.

Recently (maybe the past year or so) though, we're being told that to fix the problem an upgrade to the newest Plesk version is required (first from 8 to 9 and now from 9 to 10). We've endured this until now, but with Plesk 10 it looks like when you upgrade with an expired license, all the hosted websites go offline.

My question is, what is the reasoning behind the forced upgrades (if that information is true)? Plesk 10 is only a couple of months old. Also, why get rid of the non-expiring trial license when the license update fails? Give your customers the benefit of the doubt. This key update failed problem has been recurring for years, which would suggest that your renewal system itself is flawed.

What is everyone else doing? Any advice would be greatly appreciated.
 
Back
Top