Plesk locks the GUI the moment its license check fails, so a key problem usually surfaces as a login wall reading "Your license key has expired" or "The license key is invalid." This article maps each error message to its actual cause and the exact plesk bin license command to clear it. It's for admins who already have a valid key from Plesk 360 or a Plesk license and need the server to accept it again.
Every fix below runs over SSH, so a locked GUI doesn't block you.
Start here: check what Plesk thinks is installed
Run the validity check first. It tells you whether the key is structurally invalid, expired, or simply unretrievable:
plesk bin license -c
If that errors or reports an expired key, re-pull it from the licensing server:
plesk bin license --retrieve
--retrieve re-downloads the current key bound to this server. It fixes a stale or not-yet-activated state but does nothing if the key is bound to another IP or genuinely expired — those need the targeted fixes below.
"The license key is invalid" or "has expired"
Two distinct cases hide behind these messages.
The key lapsed. Renew it, then reinstall using the activation code (the five-group AB1C23-4DEF56-... string from your purchase email or the Licenses tab in Plesk 360):
plesk bin license -i AB1C23-4DEF56-7GHI89-JK1L23-MNP456
A reinstall does more than a retrieve — it re-binds the activation code to this server.
The key is active on another server. Plesk's anti-piracy system binds an activation code to the most recent server that installed it. If you reused the same code on a new box, the old server's key goes invalid. Reinstall on the server you actually want to keep with the -i command above; that server wins the binding. Don't run the same code on two production servers — the second install silently kills the first.
IP-bound errors
If the message reads "cannot be used with the X.X.X.X IP address because the license is bound to another IP" or "Request cannot be serviced from the specified IP(s)," your server's outbound IP no longer matches the one the key is tied to.
First, confirm which IP Plesk presents as primary under Tools & Settings > IP Addresses. If the bound IP is still on the server but isn't the primary, the fix is network-side: make outbound traffic exit through the bound IP (set it as the main/source IP in your network config), then --retrieve again.
If the bound IP is gone for good — you migrated hosts or the provider reassigned it — the key needs rebinding on Plesk's side. That's a sales operation, not a CLI one: contact us with the new IP and the activation code and we'll handle the rebind.
Virtual environment mismatch
A VPS-tier key installed on a dedicated (bare-metal) server throws "intended only for use with Plesk operating inside the following virtual environments." Plesk fingerprints the hypervisor. Either move the key to an actual VPS or convert it to a dedicated-server license — see how Plesk license tiers and editions work for which SKU you need.
Connectivity: the key won't retrieve at all
If --retrieve hangs or reports a cURL failure, the server can't reach the licensing endpoint. Plesk talks to ka.plesk.com on TCP 443. Test it:
curl -v https://ka.plesk.com 2>&1 | grep -i "connected\|expired"
No "Connected to" line means a firewall — local (firewalld, iptables) or upstream — is blocking outbound 443. Allow it and retry. Until the server can reach ka.plesk.com, no key install or renewal will complete, even with a perfectly valid code.