How can I fix the error: The licensing server was invalid or could not be reached ?

Restart Plesk Panel Interface

1. Many times this error can be fixed by just restarting the Plesk panel interface. This happens when curl libraries are updated and the Plesk panel process needs to be restarted otherwise the PHP curl functions required by the extension will not work properly. Run the following command (as root):

systemctl restart sw-engine && systemctl restart sw-cp-server

Outdated Packages

2. Make sure your openssl, curl, and ca-certificates packages are up to date. Outdated packages can result in SSL errors when your server tries to communicate with our licensing server.:

// Centos/RHEL/CLoudLinux/AlmaLinux
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.com

Blocked Licensing Server IP Address

3. Make sure that you are not blocking the licensing server IP addresses on the servers firewall. Imunify360 is known to block our server IPs for some reason. Our licensing server IP addresses are:

IPv4: 158.69.247.150
IPv6: 2607:5300:120:796::1

You can run the following command to see if your server can connect to the licensing server. You should get a response of Verify return code: 0 (ok) if the connection was successful.

openssl s_client -connect www.danami.com:443

If you get the error below that means that your server cannot connect to our licensing server (usually that means there is a firewall or connection problem):

openssl s_client -connect www.danami.com:443 - returns:
socket: Bad file descriptor
connect:errno=9

Incorrect Time

4. Make sure that the date and time on the server is correct (The wrong time will cause the SSL certificate connection to fail). Install a NTP time sync daemon on your server like Chrony or if ntpdate is installed on the server you can sync your server time using the command:

Using ntpdate:

/usr/sbin/ntpdate -b -s time.nist.gov

Using chronyd:

systemctl stop chronyd && chronyd -q 'server pool.ntp.org iburst' && systemctl start chronyd

End of Life Operating Systems

5. If your server is end-of-life (Debian 9, Debian 8, or Ubuntu 16) then it will not be getting any type of package security updates so you can't update your openssl, curl, or ca-certificates packages . These outdated operating systems can no longer talk to any server that uses a Let's Encrypt certificate (like our licensing server). Users of end-of-life operating systems can use the fix below until they get their OS properly updated:

sed -i 's/mozilla\/DST_Root_CA_X3.crt/!mozilla\/DST_Root_CA_X3.crt/g' /etc/ca-certificates.conf
update-ca-certificates
/etc/init.d/psa restart

Open a Ticket

6. If you have tried all of the above steps and you are still not able to connect to the licensing server please open a support ticket and include your servers IP address. The tech will run some additional tests on our side to see what the problem is.

  • license
  • 4 Users Found This Useful
この回答はお役に立ちましたか?

Related Articles

How can I fix the error: Host '127.0.0.1' is not allowed to connect to this MariaDB server?

When looking at the server mail log you see this: Apr 4 11:01:15 alma amavis[3540852]:...

ClamAV will not start. How can I fix the ClamAV error: daily.{c[vl]d,inc} was not met?

ClamAV refuses to start and when viewing the status you see...

How can I fix any statistics generation problems?

Missing the Warden Crontab Entry There is a crontab entry that will update Warden statistics...

How can I fix the error: "milter-reject: END-OF-MESSAGE from..." in the log and found the AV in error (cannot read /etc/clam.d/scan.conf).

Cloudlinux / Imunify360 added their own version of ClamAV to their repo which accidentally...

How can I fix the error: Can't connect to TCP port 10024 on 127.0.0.0 [Address already in use] when trying to start Amavis?

When trying to start Amavis you see this in the mail log: Oct 02 03:20:15 condor3648 systemd[1]:...