Resolved Plesk TuxCare ELS: Previous Registration Preventing Re-activation

[Rabah]

Server operating system version

CentOS 7.9

Plesk version and microupdate number

Obsidian 18.0.72 Update #2

Hi,

I’m running into an issue re-enabling the TuxCare Extended Lifecycle Support (ELS) extension on Plesk Obsidian 18.0.72 Update #2. The extension was previously active, then disabled, and now fails to register with the following message:

You cannot register a new server! Right now you have 1 server and your license limit is 1.

The TuxCare ELS integration is provided through my Plesk VPS Web Host Edition license (Parent Key) rather than a standalone CloudLinux license, so the resolution steps in this CloudLinux article don’t really apply.

It looks like the previous TuxCare registration is still bound to this server instance. Any help to clear this state so I can re-enable the extension?

Thanks,

 

[scsa20]

Pretty sure the licenses is done by CloudLinux and not Plesk directly since the repo is managed by CloudLinux and not Plesk. Plesk just have the extension to manage it easier. So doesn't hurt to double check but this is assuming you've already checked in Plesk 360 and made sure the license doesn't show up there (usually if you bought a license directly through plesk it will show up as an additional license in Platform360 but in some instances it'll be an additional license through whichever third party, in this case pretty sure the license still exist in CloudLinux side of things).

 

[Sebahat.hadzhi]

Hello, @Rabah . If the issue still persists, I would recommend getting in touch with our Customer Support team so they can take a further look. If necessary, they can involve CloudLinux:

• Contact Us - Plesk Support Will Help

 

[Rabah]

Pretty sure the licenses is done by CloudLinux and not Plesk directly since the repo is managed by CloudLinux and not Plesk. Plesk just have the extension to manage it easier. So doesn't hurt to double check but this is assuming you've already checked in Plesk 360 and made sure the license doesn't show up there (usually if you bought a license directly through plesk it will show up as an additional license in Platform360 but in some instances it'll be an additional license through whichever third party, in this case pretty sure the license still exist in CloudLinux side of things).

Well, TuxCare (CloudLinux) manages the repositories and delivers the ELS packages, i think that’s obvious. But the question was, when the ELS entitlement comes bundled via its parent key, Plesk Web Host Edition parent license, maybe the license lifecycle and registration tokens are controlled entirely, or at least mostly, by Plesk’s internal Key Administrator (KA) / Partner Central backend, don't you think ? I could be wrong, but that’s what the behavior suggests...

So, if that's the case, the Plesk ELS extension is basically an orchestration layer i guess; it queries KA for entitlement validation, issues a transient activation token, and maps that token to the server instance. Those tokens are tracked as additional keys under the parent license, which means stale objects can persist even if the extension is disabled or removed... Anyway, following that reasoning, I actually "fixed" the issue by logging into Plesk Partner Central / KA, locating the stale ELS additional key tied to the parent license and instance, terminating it, and then retrieving a new key.

 

[Rabah]

Hello, @Rabah . If the issue still persists, I would recommend getting in touch with our Customer Support team so they can take a further look. If necessary, they can involve CloudLinux:

• Contact Us - Plesk Support Will Help

Hello @Sebahat.hadzhi . The issue is resolved ; This thread can be closed. Thank you for your recommendation.