Kibana listening but webui can't be displayed

Elastic Stack Kibana
1

Hi all,

we have installed elasticsearch 2.4 and kibana 4.6 with no errors, but when we try to open webui from browser we riceived that the page can’t be displayed.

This is my log file and kibana.yml:

{"type":"log","@timestamp":"2016-10-04T15:39:28Z","tags":["status","plugin:kibana@1.0.0","info"],"pid":19344,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2016-10-04T15:39:28Z","tags":["status","plugin:elasticsearch@1.0.0","info"],"pid":19344,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2016-10-04T15:39:28Z","tags":["status","plugin:kbn_vislib_vis_types@1.0.0","info"],"pid":19344,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2016-10-04T15:39:28Z","tags":["status","plugin:markdown_vis@1.0.0","info"],"pid":19344,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2016-10-04T15:39:28Z","tags":["status","plugin:metric_vis@1.0.0","info"],"pid":19344,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2016-10-04T15:39:28Z","tags":["status","plugin:spyModes@1.0.0","info"],"pid":19344,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2016-10-04T15:39:28Z","tags":["status","plugin:statusPage@1.0.0","info"],"pid":19344,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2016-10-04T15:39:28Z","tags":["status","plugin:elasticsearch@1.0.0","info"],"pid":19344,"state":"green","message":"Status changed from yellow to green - Kibana index ready","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
{"type":"log","@timestamp":"2016-10-04T15:39:28Z","tags":["status","plugin:table_vis@1.0.0","info"],"pid":19344,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2016-10-04T15:39:28Z","tags":["listening","info"],"pid":19344,"message":"Server running at http://bda1node04.sede.corp.sanpaoloimi.com:5601"}

==========================================================================

# Kibana is served by a back end server. This controls which port to use.
 server.port: 5601

# The host to bind the server to.
 server.host: "bda1node04.sede.corp.sanpaoloimi.com"

# The Elasticsearch instance to use for all your queries.
 elasticsearch.url: "http://bda1node04.sede.corp.sanpaoloimi.com:9200"

# preserve_elasticsearch_host true will send the hostname specified in `elasticsearch`. If you set it to false,
# then the host you use to connect to *this* Kibana instance will be sent.
 elasticsearch.preserveHost: true


# The default application to load.
 kibana.defaultAppId: "discover"

# Set the path to where you would like the process id file to be created.
# pid.file: /var/run/kibana.pid
 pid.file: /tmp/kibana/kibana-4.6.1-linux-x86_64/kibana.pid

# If you would like to send the log output to a file you can set the path below.
# logging.dest: stdout
 logging.dest: /tmp/kibana/kibana-4.6.1-linux-x86_64/log_dest.log

Do you have any suggestions?

Thanks

2
  • Can you verify that bda1node04.sede.corp.sanpaoloimi.com resolves to the correct ip?
  • Are there any firewalls which are preventing you from accessing http://bda1node04.sede.corp.sanpaoloimi.com:5601 remotely?
  • From the remote machine, can you try accessing Kibana. curl --head http://localhost:5601 might help.
1 Like
3

Is a network problem.

Now work fine.

thanks