When trying to install Zato step-by-step as the quickstart does it, the UI throws an error of ‘Could not fetch the load balancer’s configuration’.
After comparing the configuration in detail to the quickstart one and the one created while running via the zato cli, the only issue that seems to be is the difference of the certificates.
It seems like zato has a different private key for each individual service (web-admin/load-balancer/serverN)
We have a wildcard certificate and key (*.domain.com):
- private key (wildcard) -> public key can be generated from this.
- certificate (wildcard)
- CA certificate
How can we use that within the context of deploying zato?
The load-balancer is created as such:
zato create load_balancer /opt/zato/dev/load_balancer /opt/zato/dev/certs/PUBLICKEY.pem /opt/zato/dev/certs/PRIVATEKEY.pem /opt/zato/dev/certs/WILDCARDCERTIFICATE.pem /opt/zato/dev/certs/CACERTIFICATE.pem
What would be the best approach for us to go with? Would the above wildcard key/cert pair be sufficient or an individual set needs to be created for each service?