Is this a real issue when we see Not Secure Warning when tried to run the https://XXXXXX/api/V1/runtime/IsAvaiable on the client machine. Is this any kind of blockage for the Robotics regarding the safety of the URL was blocking the access to the api via localhost.
When i checked for the availability of the Certificate, every thing looks good as per the Dates its still valid. Can you pl check and let me know how to suppress this and ensure the URL is secure and adaptable for Client environment.
It is not really an issue. You are using an incorrect URL to check if a client machine's runtime rest service is available. The certificate was issued for localruntime.pega.com address, so if you use any other URL address to check the service it considers the certificate as invalid.