Kibana not showing indices screen after new install


Hi guys, I'm new to ELK and to this community.
I installed ELK on Ubuntu. All seems to be up and running (ES, nginx, Kibana, Logstash)
But, when I browse to Kibana, after authenticating on nginx, the browser displays only the upper header: Kibana logo + Discover / Visualize / Dashboard / Settings , without the indices info (see screenshot)

Any idea what went wrong?

(Mohammed Abdul Khaliq) #2


Did you go to settings and Indices and try it


Thank-you Mohammed.

The issue is that the Kibana screen that the browser presents (I attached a screenshot of it) is not active, and clicking on Settings at this screen does not cause anything to change on the screen, and specifically not to show anything related to indices.

(Mark Hanford) #4

Oddly I'm seeing something very similar. I have an existing setup, with a fair few searches and visualisations saved, but when I deleted one index in the Kibana settings, everything went blank.

(Mark Walkom) #5

Check your KB and ES logs.

(Vikas Gopal) #6

From last 1 week I am facing the same issue , I have just created a simple index just for testing purpose but when I open Kibana 4.3 nothing appears accept the screen you attached .

Sometimes after waiting for 5 min kibana page throws and error as below

Fatal Error
Courier Fetch Error: unhandled error Error: unknown error
at respond (http://localhost:5601/bundles/kibana.bundle.js:76162:16)
at checkRespForFailure (http://localhost:5601/bundles/kibana.bundle.js:76123:8)
at http://localhost:5601/bundles/kibana.bundle.js:74741:8
at processQueue (http://localhost:5601/bundles/commons.bundle.js:42339:29)
at http://localhost:5601/bundles/commons.bundle.js:42355:28
at Scope.$eval (http://localhost:5601/bundles/commons.bundle.js:43583:29)
at Scope.$digest (http://localhost:5601/bundles/commons.bundle.js:43394:32)
at Scope.$apply (http://localhost:5601/bundles/commons.bundle.js:43691:25)
at done (http://localhost:5601/bundles/commons.bundle.js:38140:48)
at completeRequest (http://localhost:5601/bundles/commons.bundle.js:38338:8)

Kibana 4.3 showing blank pages after creating or deleting Indices
(Vikas Gopal) #7

@ Mark

Since I am facing the exact issue so here is my ES logs.I am on windows 8 using ES2.1.0,Kibana 4.3.0

[2015-12-04 08:24:52,402][INFO ][cluster.metadata         ] [Bast] [my_index] creating index, cause [api], templates [], shards [5]/[1], mappings [my_type]
[2015-12-04 08:25:26,750][INFO ][rest.suppressed          ] /logstash-*/_mapping/field/* Params: {ignore_unavailable=false, allow_no_indices=false, index=logstash-*, include_defaults=true, fields=*, _=1449197726699}
[logstash-*] IndexNotFoundException[no such index]
	at org.elasticsearch.cluster.metadata.IndexNameExpressionResolver$WildcardExpressionResolver.resolve(
	at org.elasticsearch.cluster.metadata.IndexNameExpressionResolver.concreteIndices(
	at org.elasticsearch.cluster.metadata.IndexNameExpressionResolver.concreteIndices(
	at org.elasticsearch.action.admin.indices.mapping.get.TransportGetFieldMappingsAction.doExecute(
	at org.elasticsearch.action.admin.indices.mapping.get.TransportGetFieldMappingsAction.doExecute(
	at org.elasticsearch.client.node.NodeClient.doExecute(
	at org.elasticsearch.client.FilterClient.doExecute(
	at org.elasticsearch.http.HttpServer.internalDispatchRequest(
	at org.elasticsearch.http.HttpServer$Dispatcher.dispatchRequest(
	at org.elasticsearch.http.netty.NettyHttpServerTransport.dispatchRequest(
	at org.elasticsearch.http.netty.HttpRequestHandler.messageReceived(
	at org.elasticsearch.http.netty.pipelining.HttpPipeliningHandler.messageReceived(
	at org.jboss.netty.handler.codec.http.HttpChunkAggregator.messageReceived(
	at org.jboss.netty.handler.codec.http.HttpContentDecoder.messageReceived(

(Yodog) #8

my problem is almost the same as yours, except that i can connect to kibana on my nodes, but not on the balancer.

you can check my configs and logs here: [ 4.3.0 ] how to configure your nginx balancer and apache reverse proxy

(Vikas Gopal) #9

Actually Mine problem was with the environment i.e windows 8 so I switched to server 2012 and it works fine for me .Even it is working fine on Ubuntu .

(system) #10