Licensing Error with DirectAdmin

A

artakservers

Verified User
Joined
Apr 8, 2011
Messages
22
Hello,


I've encountered a licensing issue after upgrading DirectAdmin on my server and need some help resolving it. When I attempt to access the DirectAdmin web page, I receive the following error message:


"Licensing error: DirectAdmin is configured with a license that can only run with legacy code-base. However, a non-legacy DirectAdmin is installed. This server was either installed or upgraded to a non-legacy code-base. Downgrade to a legacy code-base is not supported. Existing licenses can be reviewed and new licenses can be purchased in the Client Account Area. Please install a non-legacy license using command: da license-set '...license-key...' Or perform a full server reinstall with DirectAdmin legacy code-base."


Here's what I've tried so far:


  1. I updated the license key using the da license-set command with a new key.
  2. I ran /usr/local/directadmin/scripts/getLicense.sh followed by a server restart.
  3. Checked the license key file at /usr/local/directadmin/conf/license.key and confirmed that the new key is there.

Despite these steps, the error persists. I've verified that the license key matches my account details in the DirectAdmin Client Area. I'm unsure if there's a compatibility issue between the version of DirectAdmin installed and the type of license I have, or if there's another underlying problem.


Any advice or insights would be greatly appreciated. Thank you!
 
You again? What you're telling can't be true, but I won't go into it further. You did something wrong and now you're f*cked.

However I won't go into that further. There are 2 solutions now.
1.) Create backups via CLI and install server newly with your legacy license.
2.) Get a modern license (yes they aren not cheap) and change your license key to the modern license.
 
Is DirectAdmin no longer working on CentOS 7 versions?

[root@mailserver ~]# cat /etc/centos-release
CentOS Linux release 7.9.2009 (Core)
[root@mailserver ~]# /usr/local/directadmin/directadmin v
DirectAdmin v.1.665 92be28b19a1bf46189bd72b648cc39ee0792ce51
[root@mailserver ~]#
 
@artakservers, this can only be triggered if you do license hopping. Stop pretending these errors happen out of thin air.
 
It turns out it was an accidental license downgrade. The error message had an accurate explanation on what happened. Happy see the issue is resolved and sorry for assuming licensing abuse.
 
This can only happen when license is changed. And in this particular case - it happened after license hopping. The only difference was is that the server owner did this by accident (license change). So the error message explained exactly what happened, but the server owner searched for other explanations.

By "license hopping" I mean jumping back and forth between legacy and modern licenses.
 
Oke so indeed by license hopping and not by updating, then my thoughts were correct (something wrong was done), only this time by accident, thank you for explaining.
Can you resolve this or is the solution indeed re-installation?
 
fln said:
This can only happen when license is changed. And in this particular case - it happened after license hopping. The only difference was is that the server owner did this by accident (license change). So the error message explained exactly what happened, but the server owner searched for other explanations.

By "license hopping" I mean jumping back and forth between legacy and modern licenses.
Click to expand...
This server belongs to our client for whom we had purchased a standard license. Since the root password of the server was in the user's possession, we are unsure if the issue happened accidentally or if the user made any changes themselves. The user submitted a ticket to us stating that the license had stopped working. At first, I thought the issue was due to the old operating system and suggested a rebuild, but the client was not willing to rebuild. Upon further investigation, I realized that the user was using a lifetime license (as a few years ago, we had provided this client with a server with a lifetime license). I updated the license, and since then, the user has not responded to the ticket. It seems the problem has been resolved!
 
You must log in or register to reply here.
Back
Top