Problem with kibana index pattern


I have a problem with kibana index pattern. I set up a ES Cluster with Nginx as a reverse proxy. Everything is working well, but the Kibana index pattern. I have logs coming from fluentd into elasticsearch. I can see the logs when I do the following and when when I query the ES cluster in kibana, I can have a response for each indices, which means that the setup seems fine.

However, when I tried to get to Kibana Index Patterns, I cannot see any indices and I have the following messages when I tried to create an index pattern:

Couldn't find any Elasticsearch data 
You'll need to index some data into Elasticsearch before you can create an index pattern. Learn    how or get started with some sample data sets.```

When I test with kibana_sample_data_logs, I can see the index in the app/management/kibana/indexPatterns page but I cannot create an index pattern.

When I go to app/discover#/view/3ba638e0-b894-11e8-a6d9-e546fe2bba5f?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-15m,to:now))&_a=(columns:!(category,sku,taxful_total_price,total_quantity),filters:!(),index:ff959d40-b880-11e8-a6d9-e546fe2bba5f,interval:auto,query:(language:kuery,query:''),sort:!(!(order_date,desc)))
I've got the following error:

Error loading data
construct@[native code]
construct@[native code]

Does anyone have an idea of what I might have done wrong?

Please see below and my NGINX conf file for kibana:

location ~ (/app|/translations|/node_modules|/built_assets/|/bundles|/es_admin|/plugins|/api|/ui|/elasticsearch|/spaces/enter)
  proxy_pass $proxy_pass_url;
  proxy_set_header Host $host;
  proxy_set_header X-Real-IP $remote_addr;
  proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
  proxy_set_header X-Forwarded-Proto $scheme;
  proxy_set_header X-Forwarded-Host $http_host;
  proxy_set_header Authorization "";
  proxy_hide_header Authorization;


Thank you in advance for any help. :grin:

Why not serve Kibana under a basePath, and use that path as the location? The way you are matching each Kibana path for the proxy rules is going to be a never-ending maintenance struggle.

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