Since I updated to ES 2.1.0, Shield 2.1.0 and Kibana 4.3.0, Kibana doesn't work properly. If I set an index with a wildcard in the Settings tab (for example, logstash-*), when I go to the Discover tab, I get an error that says: Fatal Error Courier Fetch: [index_not_found_exception] no such index…

Kibana doesn't work with wildcards since Shield 2.1.0

ttl January 21, 2016, 1:42am 13

I had the exact same problem. Installing Kibana 4.3.1 resolved this issue for me.

Topic		Replies	Views
Kibana doesn’t work authentication with Shield Kibana	18	1755	July 6, 2017
ES 2.2: index_not_found_exception [logstash-*] Logstash	5	6090	July 6, 2017
New install not working for search Kibana	1	730	July 6, 2017
Kibana does not create .kibana index Kibana	5	3455	July 6, 2017
Kibana is failing to find logstash-* indices after shield install Kibana	5	1520	July 6, 2017

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.

Kibana doesn't work with wildcards since Shield 2.1.0

Related topics