# Kibana no longer working **URL:** \ **Category:** Elastic Cloud on Kubernetes (ECK)\ **Created:** [November 18, 2019, 11:10pm UTC](https://discuss.elastic.co/t/kibana-no-longer-working/208399 "2019-11-18T23:10:29Z")\ **Posts on this page:** 1\ **Showing post:** 9
**Author:** ![sebgl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sebgl/32/48702_2.png) [@sebgl](https://discuss.elastic.co/u/sebgl)\ **Post date:** [November 26, 2019, 9:23am UTC](https://discuss.elastic.co/t/kibana-no-longer-working/208399/9 "2019-11-26T09:23:36Z")
> Updated the value of reindex.remote.whitelist to `es.example.com:443` . ES health stay green, stuck at 2 ES nodes Looks like the rolling upgrade did not go fine. If 1/3 Pods is not available (probably the one being upgraded) you can look at its logs (the Elasticsearch logs) to see if anything's wrong with its configuration. And maybe learn more about the failing reindex from cluster. Do things work correctly if you unset the `LoadBalancer` type service? We've seen other folks having issues with LoadBalancer services not being reachable using the internal DNS. A workaround is to create your own additional LoadBalancer service, see [this example](https://discuss.elastic.co/t/kibana-cant-connect-to-es-having-openstack-loadbalancer-setting/206691/4). Let me know what happens in your case! --- _[View the full topic](https://discuss.elastic.co/t/kibana-no-longer-working/208399)._