Bobcares

DirectAdmin License Check Failure | How We Fix It?

by | Nov 17, 2024

To fix the license check failure in DirectAdmin, we must follow the steps in this article. At Bobcares, with our DirectAdmin Support Services, we can handle your issues.

Overview
  1. Fixing “DirectAdmin license check failure” error
  2. Common Causes of License Check Failure
  3. Troubleshooting the DirectAdmin License Check Failure
  4. Preventing Future License Check Failures
  5. Conclusion

Fixing “DirectAdmin license check failure” error

The “DirectAdmin license check failure” error can leave us locked out of the server management panel, rendering it impossible to manage the server resources. This issue typically arises when DirectAdmin cannot verify the validity of the license. Fortunately, most of the causes are easy to resolve, and we’ll walk us through the steps to fix the problem and prevent it from happening again.

directadmin license check failure

Common Causes of License Check Failure

1. Network Connectivity Issues DirectAdmin requires a stable internet connection to communicate with its licensing servers. If the server is facing network problems—like DNS issues or firewall restrictions—DirectAdmin won’t be able to validate the license, resulting in a failure.

2. Incorrect IP Address or Hostname DirectAdmin licenses are tied to specific IP addresses or ranges. If the server’s IP address changes (due to dynamic IPs or server migration), DirectAdmin will fail to authenticate the license.

3. Expired License Like all software, DirectAdmin licenses need periodic renewal. If the license has expired, or if there’s an issue with payment (for subscription plans), the license check will fail.

4. Invalid or Misconfigured License Key An incorrect or improperly configured license key can prevent DirectAdmin from verifying the license, causing a failure.

5. DirectAdmin Licensing Server Downtime While rare, if DirectAdmin’s licensing server is temporarily down, the server won’t be able to reach it, leading to a license check failure.

6. Firewall or IP Blocking If the firewall blocks outbound connections to DirectAdmin’s licensing server, we’ll encounter a license validation issue.

7. Corrupted License Files License files can become corrupted due to various reasons, such as accidental deletion or changes, which disrupt the validation process.

8. Incorrect Server Time or Timezone DirectAdmin uses the server’s date and time for periodic license checks. A large time discrepancy can lead to license validation failures.

Troubleshooting the DirectAdmin License Check Failure

1. Check Network Connectivity

Ensure the server can connect to the DirectAdmin licensing server. Run these commands to check connectivity:

ping license.directadmin.com




curl -v https://license.directadmin.com

If these commands fail, resolve any network issues related to DNS or firewall settings.

2. Verify the IP Address

Make sure the server’s IP matches the one registered with DirectAdmin. To check the server’s public IP:

curl ifconfig.me

Compare it with the IP registered in the DirectAdmin client portal. If they differ, update the IP in the client portal or contact DirectAdmin support.

3. Check for Expired License

Log in to the DirectAdmin client portal to verify the license status. If expired, renew the license or resolve payment issues. We can also manually force a license update with:

/usr/local/directadmin/scripts/getLicense.sh your_client_id your_license_key

4. Manually Force a License Check

We can force DirectAdmin to perform a license check by running:

echo 'action=directadmin&value=restart' >> /usr/local/directadmin/data/task.queue

5. Verify Firewall Rules

Ensure the firewall isn’t blocking outbound traffic to the licensing server. Check the firewall settings:

For iptables:

iptables -L

For firewalld:

sudo firewall-cmd --list-all

Look for any rules blocking outbound traffic on port 443 (HTTPS).

6. Ensure Correct Server Time

Check if the server’s time is accurate:

date

If incorrect, synchronize the time with NTP:

sudo timedatectl set-ntp true

Or manually set the time:

sudo date -s "YYYY-MM-DD HH:MM:SS"

7. Reinstall or Reissue License

If the license files are corrupted, we can download a fresh license by running:

/usr/local/directadmin/scripts/getLicense.sh

8. Check DirectAdmin Licensing Server Status

Occasionally, DirectAdmin’s licensing server may experience downtime. Check their support forums or contact their team to verify if there’s an ongoing issue.

Preventing Future License Check Failures

To avoid facing the “license check failure” error again, follow these best practices:

1. Keep the IP Address Static Use a static IP for the server to prevent mismatches between the registered and current IP address.

2. Monitor License Expiry Dates Stay on top of the license’s expiration date and ensure timely payments or renewals.

3. Ensure Stable Connectivity Regularly check that the server can connect to DirectAdmin’s licensing server, especially after network or firewall changes.

4. Use NTP for Time Synchronization Keep the server’s time synchronized using NTP to prevent time-related validation issues.

5. Configure Alerts for License Failures Set up monitoring to alert us if DirectAdmin’s license check fails. This way, we can address the issue immediately.

[Need to know more? Get in touch with us if you have any further inquiries.]

Conclusion

By understanding the common causes and troubleshooting steps, we can quickly resolve any DirectAdmin license validation issues and ensure smooth operation of the server. Keep the license updated, network settings stable, and system time accurate, and we’ll avoid future interruptions.

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF