# Problem with kibana index pattern

**URL:** https://discuss.elastic.co/t/problem-with-kibana-index-pattern/253202
**Category:** Kibana
**Created:** [October 24, 2020, 12:20pm UTC](https://discuss.elastic.co/t/problem-with-kibana-index-pattern/253202 "2020-10-24T12:20:39Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![milguad](https://avatars.discourse-cdn.com/v4/letter/m/4bbf92/32.png) [@milguad](https://discuss.elastic.co/u/milguad)
#### Post date: [October 24, 2020, 12:20pm UTC](https://discuss.elastic.co/t/problem-with-kibana-index-pattern/253202/1 "2020-10-24T12:20:39Z")

</div>

Hi,

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 `http://192.168.40.12/_cat/indices?v ` 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]
Wrapper@https:// ****** /33984/bundles/core/core.entry.js:28:7985
construct@[native code]
_createSuperInternal@https:// ******* /33984/bundles/core/core.entry.js:28:7121
HttpFetchError@https:// ******* /33984/bundles/core/core.entry.js:28:9746
_callee3$@https:// *********/33984/bundles/core/core.entry.js:34:109390l@https://********* /33984/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:368:155659
.....
```

````

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. 😁

---

<div class="post-metadata">

### Author: ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)
#### Post date: [October 29, 2020, 7:59pm UTC](https://discuss.elastic.co/t/problem-with-kibana-index-pattern/253202/2 "2020-10-29T19:59:48Z")

</div>

> [@milguad](#):
>
> ```auto
> location ~ (/app|/translations|/node_modules|/built_assets/|/bundles|/es_admin|/plugins|/api|/ui|/elasticsearch|/spaces/enter)
> 
> ```

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.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [November 26, 2020, 8:00pm UTC](https://discuss.elastic.co/t/problem-with-kibana-index-pattern/253202/3 "2020-11-26T20:00:06Z")

</div>

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