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

Outdated Packages

1. 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.

End of Life Operating Systems

If your server is end-of-life (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
/etc/init.d/psa restart

Restart Plesk Panel

2. Many times this error can be fixed by restarting the Plesk panel:

/etc/init.d/psa restart

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:

IPv6: 2607:5300:60:2106::

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

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 - returns:
socket: Bad file descriptor

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

Using chronyc:

chronyc -a makestep

Open a Ticket

5. 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 Utilisateurs l'ont trouvée utile
Cette réponse était-elle pertinente?

Articles connexes

How can I fix the daily cron error: /etc/cron.daily/maldet: line 69: [: ==: unary operator expected?

There is a bug in the Linux Malware Detect v1.6.4 daily cron script. You can fix the error by...

How do I fix the error: Mysql Server has gone away?

When looking at the mail log of the server you see this log entry from Amavis: Aug 3 01:00:20...

What changes does Warden make to the postfix configuration files to enable Amavis?

Important Warden will configure postfix differently depending if you selected to install the...

How hard is it to uninstall if I do not require Warden Anti-spam and Virus Protection any more?

Uninstalling Warden is as easy as going to Extensions -> My Extensions -> Warden Anti-spam...

How hard is it to uninstall if I do not require Sentinel Anti-malware any more?

Uninstalling Sentinel Anti-malware is as easy as going to Extensions -> My Extensions ->...