Comment 3 for bug 1838780

This is all I've found, and at this point I don't know enough about how it's suppose to work to fix it beyond making some guess.

I verified that the certificate that is returned when the status is queried at 192.168.0.107:8443 is in fact issued for 192.168.0.266. This it turns out is the cluster.crt found on the LXD unit, not the server.crt. However, 192.168.0.266 isn't in the cluster anymore and it appears all units in the cluster have this same cluster certificate. Since the machine that I replaced was 192.168.0.244 I can only guess as a cluster member it had this same cert as well. I'm not clear why 192.168.0.244 was usable by the controller (or juju client client?) with this certificate but 192.168.0.107 returning it is an issue.