Problem Installing Analytics Server Thingworx

Hi @AntonioFar 

You mentioned having enabled TLS for Analytics microservices and Zookeeper. I would like to point something out here.

Obviously security is important and should be taken seriously, however in the case of Analytics microservices and zookeeper, those are services installed by ThingWorx Analytics Server and they all run on the same machine, communicating to each other on that same machine, there is no network access. Therefore by enabling TLS for those components, you are securing a connection that never goes to the network. There might be scenario where this is needed, but you'll have to consider if the added complexity is necessary here.

Regarding securing the communication between ThingWorx Analytics Server and ThingWorx is different as both software can be deployed on different machine and anyway ThingWorx is likely needed in TLS as it is accessed by other clients over the Internet.

Now to the error you face, You are setting ThingWorx hostname as 127.0.0.1 and add a certificate.

Assuming that your certificate would be valid for 127.0.0.1, it would work only for the local machine, any other clients will not access ThingWorx via 127.0.0.1, they will use either its external ip address or its hostname. This means the every client will get a warning of unsecure connection because they would not be accessing the server with the ip defined in the certificate (127.0.0.1).

It does not seem to me that this is a useful certificate.
Could you give some explanation on your scenario ?

Can you maybe upload the thingworx.csr file ?

Thanks

Christophe