# Kibana unable to read indexes
**URL:** https://discuss.elastic.co/t/kibana-unable-to-read-indexes/83135
**Category:** Kibana
**Created:** [April 21, 2017, 1:27am UTC](https://discuss.elastic.co/t/kibana-unable-to-read-indexes/83135 "2017-04-21T01:27:02Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@oobl](https://discuss.elastic.co/u/oobl)
#### Post date: [April 21, 2017, 1:27am UTC](https://discuss.elastic.co/t/kibana-unable-to-read-indexes/83135/1 "2017-04-21T01:27:02Z")
Hello, just trying out Kibana 5.3 before upgrading from our 4.6 setup.
We can query at the newly formed indices in devtools and commandline, but Kibana still can't read the indices even though we're using the default format of logstash-\*
Filebeat, elasticsearch, logstash, kibana, all at 5.3.0-1. This cluster is on Centos7.
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [April 21, 2017, 2:22am UTC](https://discuss.elastic.co/t/kibana-unable-to-read-indexes/83135/2 "2017-04-21T02:22:38Z")
> [@oobl](#):
>
> Kibana still can't read the indices even though we're using the default format of logstash
What do you mean by this?
---
### Author:  [@oobl](https://discuss.elastic.co/u/oobl)
#### Post date: [April 21, 2017, 4:57pm UTC](https://discuss.elastic.co/t/kibana-unable-to-read-indexes/83135/3 "2017-04-21T16:57:39Z")
Our indexes are using the format of logstash-%{+YYYY.MM.dd}, same as our previous setup. So figured a the default index of logstash-\* would catch it.
---
### Author:  [@oobl](https://discuss.elastic.co/u/oobl)
#### Post date: [April 21, 2017, 5:50pm UTC](https://discuss.elastic.co/t/kibana-unable-to-read-indexes/83135/4 "2017-04-21T17:50:12Z")
Able to query all our indices through devtools or just command line curl commands, but Kibana returns with an unable to fetch mapping error.
Update: we had some old nginx proxy directives in place. Looks like they were interfering with Kibana's ability to grab the data. Below is what we had in place, just commented out the lot of them.
location ~ ^/\_plugin/.\*$ {
proxy\_pass [http://127.0.0.1:9200](http://127.0.0.1:9200);
proxy\_read\_timeout 90; }
location ~ ^/\_status$ {
proxy\_pass [http://127.0.0.1:9200](http://127.0.0.1:9200);
proxy\_read\_timeout 90; }
location ~ ^/\_cluster/.\*$ {
proxy\_pass [http://127.0.0.1:9200](http://127.0.0.1:9200);
proxy\_read\_timeout 90; }
location ~ ^/\_nodes/.\*$ {
proxy\_pass [http://127.0.0.1:9200](http://127.0.0.1:9200);
proxy\_read\_timeout 90; }
location /elasticsearch/ {
proxy\_pass [http://127.0.0.1:9200/;](http://127.0.0.1:9200/;)
proxy\_redirect [http://127.0.0.1:9200/](http://127.0.0.1:9200/) /elasticsearch/;
proxy\_read\_timeout 90; }
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 19, 2017, 6:03pm UTC](https://discuss.elastic.co/t/kibana-unable-to-read-indexes/83135/5 "2017-05-19T18:03:39Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.