The SSL connection could not be established

Error Description

Users are encountering the following error message when attempting to connect to the server. The error message indicates that there was a failure to establish a secure connection (SSL/TLS) between the client and server due to issues with the validity of the server's SSL certificate (likely due to issues with time validity (e.g., expiration) or certificate chain configuration).

The SSL connection could not be established: The remote certificate is invalid because of errors in the certificate chain: NotTimeValid

Applies to

UOF SDK - all versions

Symptoms

The above message is observed in the SDK execution logs.

Resolution

To resolve this issue, follow these steps:

1. NotTimeValid: This relates to the validity period of the SSL/TLS certificate used by the server. SSL/TLS certificates have a defined duration of validity, and this error occurs under the following conditions:

   • The certificate has not yet become valid (i.e., the current date is before the "valid from" date of the certificate).

   • The certificate has expired (i.e., the current date is after the "valid to" date of the certificate).

2. Check the System Clock: Ensure that the system clock on the client machine (where the error is occurring) is set to the correct current date and time. Incorrect system time can lead to certificate validation errors.

3. Examine the Certificate: Inspect the validity dates (valid from and valid to) of the server's SSL/TLS certificate. This can typically be done using a web browser or specialized tools that analyze SSL certificates.

4. Renew the Certificate: If the certificate has expired, the server administrator should renew the SSL/TLS certificate and deploy the new certificate on the server.

5. Contact Server Administrator: If you are not the server administrator, reach out to the responsible party and report the certificate validation issue. The server administrator may need to take action to renew or reconfigure the SSL/TLS certificate.