# Fresh install of 7.4 Kibana - Kibana does not start listening on expected interface **URL:** \ **Category:** Kibana\ **Created:** [October 31, 2019, 2:18pm UTC](https://discuss.elastic.co/t/fresh-install-of-7-4-kibana-kibana-does-not-start-listening-on-expected-interface/206055 "2019-10-31T14:18:00Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![David.CIS](https://avatars.discourse-cdn.com/v4/letter/d/a183cd/32.png) [@David.CIS](https://discuss.elastic.co/u/David.CIS)\ **Post date:** [October 31, 2019, 2:18pm UTC](https://discuss.elastic.co/t/fresh-install-of-7-4-kibana-kibana-does-not-start-listening-on-expected-interface/206055/1 "2019-10-31T14:18:01Z")
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](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. Am I missing something? ---
**Author:** ![Nathan\_Reese](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nathan_reese/32/84829_2.png) [@Nathan\_Reese](https://discuss.elastic.co/u/Nathan_Reese)\ **Post date:** [November 1, 2019, 5:51pm UTC](https://discuss.elastic.co/t/fresh-install-of-7-4-kibana-kibana-does-not-start-listening-on-expected-interface/206055/2 "2019-11-01T17:51:08Z")
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 ---
**Author:** ![David.CIS](https://avatars.discourse-cdn.com/v4/letter/d/a183cd/32.png) [@David.CIS](https://discuss.elastic.co/u/David.CIS)\ **Post date:** [November 1, 2019, 6:16pm UTC](https://discuss.elastic.co/t/fresh-install-of-7-4-kibana-kibana-does-not-start-listening-on-expected-interface/206055/3 "2019-11-01T18:16:41Z")
Thanks for your help Nathan. I placed that bad option in the /etc/kibana.yml file and it did indeed throw an exception, but not for the line I placed it in the file. Prior to your response I also tried installing as 7.3 in a clean VM and the issue occurred again. I used the instructions here to install it on this Ubuntu VM: [https://www.elastic.co/guide/en/kibana/7.4/deb.html#deb-repo](https://www.elastic.co/guide/en/kibana/7.4/deb.html#deb-repo) ---
**Author:** ![David.CIS](https://avatars.discourse-cdn.com/v4/letter/d/a183cd/32.png) [@David.CIS](https://discuss.elastic.co/u/David.CIS)\ **Post date:** [November 1, 2019, 6:40pm UTC](https://discuss.elastic.co/t/fresh-install-of-7-4-kibana-kibana-does-not-start-listening-on-expected-interface/206055/4 "2019-11-01T18:40:57Z")
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. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 29, 2019, 6:41pm UTC](https://discuss.elastic.co/t/fresh-install-of-7-4-kibana-kibana-does-not-start-listening-on-expected-interface/206055/5 "2019-11-29T18:41:01Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.