if you run kibana and es on the same machine, es should probably just listen to 127.0.0.1.
What i would suggest is to first try to access kibana from the same machine its running on. That way you at least know its running ok, and that the only issue is with accessing it from outside.
what does netstat -natp | grep 5601 give you ?
can you connect to kibana from machine its running on ?
if not .... check logs, there should be some information on why its failing to start.
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.