Overview
This article provides step-by-step instructions to resolve the error message: "The licensing server was invalid or could not be reached." This issue typically occurs due to service interruptions, outdated system packages, firewall restrictions, time synchronization discrepancies, or unsupported operating systems.
Prerequisites
- Root access to the server via SSH
- Administrative privileges for package management and service control
Restart Plesk Panel Services
If recent updates were applied to system libraries (such as curl), the Plesk panel processes may require a restart to load the updated dependencies. Execute the following command with root privileges:
systemctl restart sw-engine && systemctl restart sw-cp-serverUpdate System Packages
Outdated security packages can cause SSL/TLS handshake failures when communicating with the licensing server. Ensure that openssl, curl, and ca-certificates are updated to their latest versions.
// AlmaLinux/CloudLinux/RHEL
yum update openssl curl ca-certificates
// Debian / Ubuntu
apt-get upgrade openssl curl ca-certificates
// You can test if your server can communicate properly with our licensing server using the wget command
// If you get an expired certificate error then your server packages are out of date.
wget https://www.danami.comVerify Firewall Configuration & IP Allowlisting
Ensure that the server firewall or security modules (such as Imunify360) are not blocking traffic to the licensing server. Whitelist the following IP addresses if necessary:
IPv4: 158.69.247.150
IPv6: 2607:5300:120:796::1To verify connectivity, run the following command. A successful connection will return Verify return code: 0 (ok):
openssl s_client -connect www.danami.com:443If the output displays the error below, a firewall rule or network restriction is likely blocking the connection:
openssl s_client -connect www.danami.com:443 - returns:
socket: Bad file descriptor
connect:errno=9Synchronize System Time
Incorrect system time will cause SSL certificate validation to fail. Install and configure a Network Time Protocol (NTP) daemon such as Chrony, or synchronize the clock manually using one of the following methods:
Using chronyd:
systemctl stop chronyd && chronyd -q 'server pool.ntp.org iburst' && systemctl start chronydTroubleshooting & Support
If the licensing server remains unreachable after completing all previous steps, please submit a support ticket. Include your server's public IP address in the ticket description so our engineering team can perform additional network diagnostics.
