Elasticsearch/Kibana behind Azure load balancer

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

1 Like

I solved the issue. Added session persistence (client IP) to the Azure load balancing rules.

2 Likes

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.