

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. Using ntpdate: /usr/sbin/ntpdate -b -s ĥ.
#Openssl connect install
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: Make sure that the date and time on the server is correct (The wrong time will cause the SSL certificate connection to fail). 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:Ĥ. You should get a response of Verify return code: 0 (ok) if the connection was successful.

You can run the following command to see if your server can connect to the licensing server. On Linux, OpenSSL is installed from the base repositories: sudo apt-get install openssl on Ubuntu/Debian sudo yum install openssl on CentOS/RedHat In order to connect to the SMTP host from the command line with the SSL/TLS encryption, use the following command: openssl. Our licensing server IP addresses are: IPv4: 198.27.80.6 Imunif圓60 is known to block our server IPs for some reason. Make sure that you are not blocking the licensing server IP addresses on the servers firewall. Many times this error can be fixed by restarting the Plesk panel: /etc/init.d/psa restartģ. 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/nfĢ. These outdated operating systems can no longer talk to any server that uses a Let's Encrypt certificate (like our licensing server).
#Openssl connect update
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. If you get an expired certificate error then your server packages are out of date. You can test if your server can communicate properly with our licensing server using the wget command
#Openssl connect upgrade
Outdated packages can result in SSL errors when your server tries to communicate with our licensing server.: // Centos/RHEL/CLoudLinux/AlmaLinuxĪpt-get upgrade openssl curl ca-certificates Make sure your openssl, curl, and ca-certificates packages are up to date. If you have any problems using the SSL Checker to verify your SSL certificate installation, please contact us.1. Openssl s_client -connect For a more detailed report of the SSL security of your server (including revocation, cipher, and protocol information), check your site using SSL Labs' SSL Server Test. You can check SSL installations on internal names by downloading OpenSSL and running this OpenSSL command: SSL Checker entries may be cached up to a day after repeated checking to conserve server resources. Other problems such as old hash functions.Whether the correct hostname is included in the certificate.If activated, you will get CONNECTED else handshake failure. The certificate's expiration date - The SSL Checker even lets you set up a reminder of a certificate's expiration so you don't forget to renew your certificate on time and avoid embarrassing error messages. openssl sclient -connect :443 tls12 If you are securing a web server and need to validate if SSL V2/V3 is enabled or not, you can use the above command.Whether the server is giving out the correct intermediate certificates so there are no untrusted warnings in users' browsers.Whether an SSL certificate is installed.The SSL Checker makes it easy to verify your SSL certificates by connecting to your server and displaying the results of the SSL connection.
