When DirectAdmin cannot confirm its license, it does not degrade gracefully. The panel simply stops serving logins, and the hosting accounts underneath keep running while you lose the ability to manage them. That makes licensing errors feel more serious than they usually are. Nearly all of them come from a short list of causes, and DirectAdmin is helpful enough to tell you which one you have, if you know where to look. If you run cPanel as well, the same situation is covered in our guide to the cPanel invalid license error, and the fixes are similar in spirit but different in detail.
Read the service log before changing anything
DirectAdmin writes every licensing failure to its service log. Reading it removes the guesswork, because the exact wording identifies the cause:
journalctl -u directadmin -n 50Match what you see against the sections below. The official DirectAdmin licensing documentation lists these messages too, and is worth keeping open while you work, since the vendor updates it as the licensing system changes.
Lost license session
This one catches people out. It means the license is currently in use on another server, or that you have reached the server limit on the license. The classic cause is a restore: a backup or a cloned virtual machine was brought up on a second host, and that copy claimed the license first. If you know the other server is a stray copy and the original is the one you want, restart DirectAdmin on the main server so it reclaims the license:
systemctl restart directadminIf you do not recognise the other server at all, treat that as a security question, not just a licensing one. Reset the license key from your client account area on the vendor's site, then apply the new key on your server. Do not simply restart and move on, because something you do not control is running your license.
Context deadline exceeded
This error means the server cannot reach the licensing servers at all. It is a network problem, not a license problem, and the fix is to find what is blocking the connection. Check DNS and a direct request from the server itself:
dig +short licensing.directadmin.com
curl https://licensing.directadmin.comThe first command should return IP addresses and the second should return a page of HTML. If DNS fails, look at the resolver settings in /etc/resolv.conf. If DNS works and the request times out, a firewall rule, a new security tool or an outbound filtering policy is the usual suspect. The documentation does not name specific ports, so rather than guessing, confirm that outbound HTTPS to that hostname is permitted. On servers without direct internet access, licensing requests can be routed through a proxy by setting HTTPS_PROXY in a systemd drop-in for the directadmin service.
License is IP restricted
DirectAdmin licenses are tied to IP addresses. If your server's address is not within the ranges allowed on the license, it will be refused. This turns up after a migration, after a hosting provider changes the primary address, or when a server gains an IPv6 address that was never added. Dual-stack servers need both the IPv4 and the IPv6 address listed. Add the addresses in your client account area, then restart the service and check the log again.
Request time is out of sync
A server clock that has drifted causes licensing requests to be rejected, and it looks nothing like a clock problem from the panel's point of view. Check that time synchronisation is running and the clock is correct:
timedatectlFix the clock first, then restart DirectAdmin. This is also a good moment to confirm NTP is enabled so it does not recur.
Too many requests, try again later
When several servers compete for one license, the licensing system throttles them. Make sure only one DirectAdmin instance is genuinely running on that license, wait about ten minutes, then restart the service on the server you want to keep. Repeatedly restarting makes the throttling last longer.
Invalid key, or a license that is not active
Messages such as invalid license key, license expired, suspended, not active or not verified are account-side problems. Log in to your client account area and look at the license status there. An expired or suspended license needs a billing fix, not a server fix. If the key on the server is simply wrong or empty, you can apply the correct one by hand:
cat /usr/local/directadmin/conf/license.key
echo 'your-license-key' > /usr/local/directadmin/conf/license.key
chmod 0600 /usr/local/directadmin/conf/license.key
systemctl restart directadminKeep the permissions at 0600. The key is a credential, and it should not be readable by other users on the server.
After a migration, plan the license first
Most licensing incidents we are asked about follow a server move. The new machine has a different IP, the old one is still running, and the license is claimed by whichever starts first. If you are changing control panels altogether, our guide to moving from cPanel to DirectAdmin covers the planning, and the same discipline of sorting licensing out before cutover applies to any panel migration, as we explain in our guide on migrating from cPanel to Plesk without downtime.
If a DirectAdmin server is locked and your clients are waiting, our DirectAdmin server management engineers can trace the exact licensing fault, restore panel access and tidy up the cause so it does not return.
Get hands-on support for your DirectAdmin server
Our engineers manage DirectAdmin licensing, mail, backups, security and day-to-day server problems.
