# Kibana -H doesn't work in VM

**URL:** <https://discuss.elastic.co/t/kibana-h-doesnt-work-in-vm/120731>\
**Category:** Kibana\
**Created:** [February 20, 2018, 10:04pm UTC](https://discuss.elastic.co/t/kibana-h-doesnt-work-in-vm/120731 "2018-02-20T22:04:36Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![melissachang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/melissachang/32/36684_2.png) [@melissachang](https://discuss.elastic.co/u/melissachang)\
**Post date:** [February 20, 2018, 10:04pm UTC](https://discuss.elastic.co/t/kibana-h-doesnt-work-in-vm/120731/1 "2018-02-20T22:04:36Z")

</div>

I'm trying to start Kibana and access the web page from a different machine. On my Debian desktop, `kibana-5.0.2-linux-x86_64/bin/kibana -H <ip address>` works. From a different machine, I can access machine\_hostname:5601.

In a GCE VM, I get:

log [22:03:59.177] [fatal] Error: listen EADDRNOTAVAIL 35.230.120.179:5601  
at Object.exports.\_errnoException (util.js:1026:11)  
at exports.\_exceptionWithHostPort (util.js:1049:20)  
at Server.\_listen2 (net.js:1244:19)  
at listen (net.js:1293:10)  
at net.js:1403:9  
at \_combinedTickCallback (internal/process/next\_tick.js:77:11)  
at process.\_tickCallback (internal/process/next\_tick.js:98:9)

It seems I need different flags for a VM, but I can't figure out what they are.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [February 20, 2018, 10:07pm UTC](https://discuss.elastic.co/t/kibana-h-doesnt-work-in-vm/120731/2 "2018-02-20T22:07:52Z")

</div>

Can you show the complete command you are using on the VM?

---

<div class="post-metadata">

**Author:** ![melissachang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/melissachang/32/36684_2.png) [@melissachang](https://discuss.elastic.co/u/melissachang)\
**Post date:** [February 20, 2018, 10:10pm UTC](https://discuss.elastic.co/t/kibana-h-doesnt-work-in-vm/120731/3 "2018-02-20T22:10:40Z")

</div>

`kibana-5.0.2-linux-x86_64/bin/kibana -H <external ip address>`

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [February 20, 2018, 10:13pm UTC](https://discuss.elastic.co/t/kibana-h-doesnt-work-in-vm/120731/4 "2018-02-20T22:13:20Z")

</div>

Try binding to `0.0.0.0`.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 20, 2018, 10:13pm UTC](https://discuss.elastic.co/t/kibana-h-doesnt-work-in-vm/120731/5 "2018-03-20T22:13:49Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.