• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Turn off "License key is not prolongated yet"

eugenevdm

Regular Pleskian
How do I turn off this annoying message? It intermittently appears in our help desk and it creates a ticket every time, causing daily overhead in running the support department:

-----------
Plesk additional key update terporary error

There were problems while trying to update your additional Plesk key.
Plesk will continue trying.
Details:

Server response: License key is not prolongated yet
-----------

I DON'T WANT TO RECEIVE THIS "TERPORARY ERROR"
 
Hello

You can just remove additional license key, seems it is expired and useless.
Go to Plesk CP > Server > License management > Additional key and remove the key installed there.
 
Our drweb license is expired, and we turned off drweb daemon in Plesk Panel. Also, we removed additional key from Panel, as described (Plesk CP > Server > License management > Additional key and remove the key).

But, after restarting server or Plesk service, additional key for drweb is newly presented in Plesk Panel (of course, expired, internal properties is equivalent deleted key). Also, we receiving again mails "Plesk additional key update terporary error".

Why happen this strange thing and how can we turn off this annoying issue?
 
This problem does still exist in 2024 under specific circumstances. We have an extension where we did exchange the license key to an external one (not bought from Plesk). The old subscription was cancelled via cleverbridge (Plesk). The already expired key was deleted under "Tools & Settings - License Information" and the new key from the external partner was activated. Nevertheless the old expired key gets re-installed automatically after some days including the then following "Plesk key update deferral notification".

How can we remove the key forever without being reinstalled all the time?
 
Does this also happen when you retrieve keys manually in Tools & Settings > License Management? And is the cancelled license still visible when you login to Plesk 360 and review your licenses there?
 
Yes it also happens when we retrieve the keys manually. We did not sign up for Plesk 360 yet.
 
I'd suggest giving Plesk 360 a go. If you still see your cancelled license there then contact license support (it's free) and let them know that the cancelled license is (probably ) causing "License key is not prolongated yet" notification.
 
Adding a server to Plesk 360 does involve a lot of private data transfer where we do not have the permission of our clients for. I will make a bug report soon.
 
Connecting a server to Plesk 360 (platform360.io) will synchronize the client list and the domain list from that server to Plesk 360. However, synchronization is only done after explicit user confirmation.

It's also not necessary connect a server to Plesk 360 to view which licenses are in use.
 
@Kaspar@Plesk Thanks for the clarification. The problem did disappear when the license status switched from "expired" (orange label) to "terminated" (red label) in Plesk 360. Then the license will not be re-installed automatically anymore. Maybe Plesk should stop downloading keys with the "expired" status. Then also the warnings would not happen. Still looks like a bug.
 
Back
Top