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 licencing server using the wget command // If you get an expired certificate error then your packages are out of date. wget https://www.danami.com
Restart Plesk Panel
2. Many times this error can be fixed by restarting the Plesk panel:
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: 184.108.40.206 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 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
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:
/usr/sbin/ntpdate -b -s time.nist.gov
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.