Hello,
I installed Elasticsearch and Kibana 7.4 on a VM running Ubuntu 18.04. Following the instructions in the guide for that version. After finishing I set this single option in kibana.yml
server.host:0.0.0.0
From what I have read this should cause Kibana to start listening on that address. However a netstat shows it is only still listening to localhost. I've restarted the service, the VM, and tried setting the value for server.host to the VMs IP address, with and without quotes. In my logs, the service explicitly states its running at http://localhost:5601
I have also left the default for the server.host and tried adjusting the port. And the server will not recognize this change either, remaining 5601.
Sounds like your Kibana instance is not loading your kibana.yml file.
To test that your Kibana instance is not loading your kibana.yml, put a configuration that does not exist, like not_a_valid_config: true in your kibana.yml. Your kibana instance should fail with invalid configurations. If it does not fail then your kibana instance is not loading your kibana.yml
So, I had a co-worker lend a second set of eyes. He noticed that every other configuration option had a whitespace after the colon. I added a whitespace, and it started the listener on the correct network/interface.
I did not realize the yaml tokenizer was that picky. Sorry for wasting your time. Thanks Nathan.
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.