I was getting this same problem, with a juju 2.2.3 setup and cs:landscape-client.
Found that setting url and ping-url by hand fixed it, but I had already added a relation between landscape-server and landscape-client, and I would fully expect the relation to populate that info without needing to configure after deployment.
I was getting this same problem, with a juju 2.2.3 setup and cs:landscape- client.
Found that setting url and ping-url by hand fixed it, but I had already added a relation between landscape-server and landscape-client, and I would fully expect the relation to populate that info without needing to configure after deployment.