spujadas / elk-docker

Elasticsearch, Logstash, Kibana (ELK) Docker image
Other
2.16k stars 908 forks source link

Kibana Dashboard not accessible #319

Closed grohan2002 closed 4 years ago

grohan2002 commented 4 years ago

I am using the latest image -

 * Starting periodic command scheduler cron        
[ OK ]
 * Starting Elasticsearch Server        future versions of Elasticsearch will require Java 11; your Java version from [/usr/lib/jvm/java-8-openjdk-amd64/jre] does not meet this requirement

[ OK ]
waiting for Elasticsearch to be up (1/30)
waiting for Elasticsearch to be up (2/30)
waiting for Elasticsearch to be up (3/30)
waiting for Elasticsearch to be up (4/30)
waiting for Elasticsearch to be up (5/30)
waiting for Elasticsearch to be up (6/30)
waiting for Elasticsearch to be up (7/30)
waiting for Elasticsearch to be up (8/30)
waiting for Elasticsearch to be up (9/30)
waiting for Elasticsearch to be up (10/30)
waiting for Elasticsearch to be up (11/30)
waiting for Elasticsearch to be up (12/30)
waiting for Elasticsearch to be up (13/30)
waiting for Elasticsearch to be up (14/30)
Waiting for Elasticsearch cluster to respond (1/30)
logstash started.
 * Starting Kibana5        
[ OK ]
==> /var/log/elasticsearch/elasticsearch.log <==
[2020-04-14T18:17:15,746][INFO ][o.e.c.m.MetaDataIndexTemplateService] [elk] adding template [.monitoring-logstash] for index patterns [.monitoring-logstash-7-*]
[2020-04-14T18:17:15,805][INFO ][o.e.c.m.MetaDataIndexTemplateService] [elk] adding template [.monitoring-es] for index patterns [.monitoring-es-7-*]
[2020-04-14T18:17:15,857][INFO ][o.e.c.m.MetaDataIndexTemplateService] [elk] adding template [.monitoring-beats] for index patterns [.monitoring-beats-7-*]
[2020-04-14T18:17:15,902][INFO ][o.e.c.m.MetaDataIndexTemplateService] [elk] adding template [.monitoring-alerts-7] for index patterns [.monitoring-alerts-7]
[2020-04-14T18:17:15,944][INFO ][o.e.c.m.MetaDataIndexTemplateService] [elk] adding template [.monitoring-kibana] for index patterns [.monitoring-kibana-7-*]
[2020-04-14T18:17:15,977][INFO ][o.e.x.i.a.TransportPutLifecycleAction] [elk] adding index lifecycle policy [watch-history-ilm-policy]
[2020-04-14T18:17:16,023][INFO ][o.e.x.i.a.TransportPutLifecycleAction] [elk] adding index lifecycle policy [slm-history-ilm-policy]
[2020-04-14T18:17:16,066][INFO ][o.e.x.i.a.TransportPutLifecycleAction] [elk] adding index lifecycle policy [ilm-history-ilm-policy]
[2020-04-14T18:17:16,231][INFO ][o.e.l.LicenseService     ] [elk] license [9b47e51e-55fa-4239-81c6-19d092ff42b0] mode [basic] - valid
[2020-04-14T18:17:16,236][INFO ][o.e.x.s.s.SecurityStatusChangeListener] [elk] Active license is now [BASIC]; Security is disabled

==> /var/log/logstash/logstash-plain.log <==

==> /var/log/kibana/kibana5.log <==
{"type":"log","@timestamp":"2020-04-14T18:17:58Z","tags":["info","plugins-service"],"pid":316,"message":"Plugin \"case\" is disabled."}

curl http://localhost:32770 curl: (52) Empty reply from server

image

spujadas commented 4 years ago

Something like a firewall or a proxy is preventing connections between where you're running curl and the host running the container. Would suggest running the curl command in the container (through docker exec) with localhost:9200 to confirm that Kibana is running as expected, then on the host at localhost:32770 to confirm that the port is mapped properly… and then you'll need to investigate connectivity between your remote client and the host. (Tried replicating the port mapping on my machine, is working absolutely fine after creating the proper tunnels to go through the firewall.)

spujadas commented 4 years ago

Closing this issue as it has been inactive for a while.