# Elasticsearch/Kibana behind Azure load balancer **URL:** \ **Category:** Elasticsearch\ **Created:** [July 2, 2017, 3:36pm UTC](https://discuss.elastic.co/t/elasticsearch-kibana-behind-azure-load-balancer/91563 "2017-07-02T15:36:50Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![stefan2017](https://avatars.discourse-cdn.com/v4/letter/s/e79b87/32.png) [@stefan2017](https://discuss.elastic.co/u/stefan2017)\ **Post date:** [July 2, 2017, 3:36pm UTC](https://discuss.elastic.co/t/elasticsearch-kibana-behind-azure-load-balancer/91563/1 "2017-07-02T15:36:50Z")
Greetings All, I'm running a 3 node Elastic Stack cluster in Azure. Each server has Elasticsearch and Kibana installed. When I try to hit Kibana using the load balancer IP, logging in fails. It attempts to log in then logs out. In the Kibana log I see messages with "status code 304" and "session expired" . I believe this has to do with load balancing and redirects. Hitting the servers individually works perfectly. Can someone please shed some light on this issue? Any help is greatly appreciated. Thank you, Stefan ---
**Author:** ![stefan2017](https://avatars.discourse-cdn.com/v4/letter/s/e79b87/32.png) [@stefan2017](https://discuss.elastic.co/u/stefan2017)\ **Post date:** [July 3, 2017, 12:42pm UTC](https://discuss.elastic.co/t/elasticsearch-kibana-behind-azure-load-balancer/91563/2 "2017-07-03T12:42:22Z")
I solved the issue. Added session persistence (client IP) to the Azure load balancing rules. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 31, 2017, 12:42pm UTC](https://discuss.elastic.co/t/elasticsearch-kibana-behind-azure-load-balancer/91563/3 "2017-07-31T12:42:22Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.