We are using nginx as our load balancer. It is working just fine for elastic. However, when logging into kibana, it shows "no data". However, we can go to index management and see indices have been created that match our pattern. I can also log onto each kibana instance directly (bypassing nginx) and I see data under under "discover". So the individual nodes look okay but when logging on through the nginx balancer, we see no data. Any thoughts? Has anyone run into this before? Thank you.
What does your configuration look like at the load-balancer for Kibana? I ask because I have seen people manually map individual paths within Kibana which will never work. The load-balancer should be redirecting all traffic so there should be no difference between hitting the LB or Kibana node directly.
Thank you Tyler. Here is my nginx configuration. We are mapping kibana to / and not using any subpaths. I am able to login to kibana just fine through the load balancer but see no data. Logging into the individual nodes, then I see data. Here is our nginx config. Thanks for any help!!
server {
listen 443 ssl;
server_name myserver.local;
ssl_certificate /etc/pki/tls/certs/myserver.crt;
ssl_certificate_key /etc/pki/tls/private/myserver.key;
location / {
proxy_pass https://kibana-proxies;
proxy_http_version 1.1;
proxy_set_header Connection "Keep-Alive";
proxy_set_header Proxy-Connection "Keep-Alive";
proxy_set_header X-Found-Cluster "0c924d29b44e48679b277cfc359eb263";
proxy_set_header Host $http_host;
client_max_body_size 200M;
}
}
I believe we have resolved this. We had an nginx server setup to listen at /elasticsearch. Did not realize that kibana also uses that path. Thank you for the help. Does anyone know if there is a documented list of paths that kibana uses?
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.