# Getting Kibana on Host **URL:** \ **Category:** Kibana\ **Created:** [June 29, 2018, 10:40am UTC](https://discuss.elastic.co/t/getting-kibana-on-host/137938 "2018-06-29T10:40:04Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Marcos\_Felix](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marcos_felix/32/32486_2.png) [@Marcos\_Felix](https://discuss.elastic.co/u/Marcos_Felix)\ **Post date:** [June 29, 2018, 10:40am UTC](https://discuss.elastic.co/t/getting-kibana-on-host/137938/1 "2018-06-29T10:40:04Z")
Hello, I'm trying to get Kibana to run on my host I have it running on my VMware server and I connect it via console. I am using NGINX and got all the settings configured according to multiple tutorials. For some reason I cannot use my host machine to connect to the Kibana web interface. When I try to curl it it gives refused connection. I have all the ports needed open and have no idea of what else to try. Any tips? ---
**Author:** ![Marcos\_Felix](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marcos_felix/32/32486_2.png) [@Marcos\_Felix](https://discuss.elastic.co/u/Marcos_Felix)\ **Post date:** [June 29, 2018, 10:46am UTC](https://discuss.elastic.co/t/getting-kibana-on-host/137938/2 "2018-06-29T10:46:17Z")
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:2049 0.0.0.0:\* LISTEN - tcp 0 0 127.0.0.1:5601 0.0.0.0:\* LISTEN 547/node tcp 0 0 0.0.0.0:56783 0.0.0.0:\* LISTEN 22062/rpc.mountd tcp 0 0 0.0.0.0:111 0.0.0.0:\* LISTEN 21425/rpcbind tcp 0 0 0.0.0.0:80 0.0.0.0:\* LISTEN 31604/nginx: master tcp 0 0 127.0.0.53:53 0.0.0.0:\* LISTEN 309/systemd-resolve tcp 0 0 0.0.0.0:22 0.0.0.0:\* LISTEN 645/sshd tcp 0 0 0.0.0.0:35959 0.0.0.0:\* LISTEN - tcp 0 0 0.0.0.0:34775 0.0.0.0:\* LISTEN 22062/rpc.mountd tcp 0 0 127.0.0.1:631 0.0.0.0:\* LISTEN 527/cupsd tcp 0 0 0.0.0.0:42361 0.0.0.0:\* LISTEN 22062/rpc.mountd tcp 0 0 0.0.0.0:443 0.0.0.0:\* LISTEN 31604/nginx: master tcp6 0 0 :::2049 :::\* LISTEN - tcp6 0 0 :::38817 :::\* LISTEN 22062/rpc.mountd tcp6 0 0 :::54211 :::\* LISTEN 22062/rpc.mountd tcp6 0 0 :::35951 :::\* LISTEN - tcp6 0 0 :::111 :::\* LISTEN 21425/rpcbind tcp6 0 0 :::9200 :::\* LISTEN 30742/java tcp6 0 0 :::5044 :::\* LISTEN 31779/java tcp6 0 0 :::9300 :::\* LISTEN 30742/java tcp6 0 0 :::53461 :::\* LISTEN 22062/rpc.mountd tcp6 0 0 :::22 :::\* LISTEN 645/sshd tcp6 0 0 ::1:631 :::\* LISTEN 527/cupsd tcp6 0 0 :::5400 :::\* LISTEN 31779/java tcp6 0 0 127.0.0.1:9600 :::\* LISTEN 31779/java you see 127.0.0.1:5601 is connected on local address but not foreign which I assume would be the host. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [June 29, 2018, 10:53am UTC](https://discuss.elastic.co/t/getting-kibana-on-host/137938/3 "2018-06-29T10:53:37Z")
That is the loopback interface, so can only be reached from within the host. You will need to change the `kibana.yml` file to make it bind to an external IP or `0.0.0.0` (all interfaces). ---
**Author:** ![Marcos\_Felix](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marcos_felix/32/32486_2.png) [@Marcos\_Felix](https://discuss.elastic.co/u/Marcos_Felix)\ **Post date:** [June 29, 2018, 10:54am UTC](https://discuss.elastic.co/t/getting-kibana-on-host/137938/4 "2018-06-29T10:54:32Z")
> [@Marcos\_Felix](#): > > tcp 0 0 0.0.0.0:34775 0.0.0.0:\* LISTEN 22062/rpc.mountd that's already been done. I have tried using 0.0.0.0 and my actual IP from ipconfig. I honestly have tried everything that I could find online. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [June 29, 2018, 11:03am UTC](https://discuss.elastic.co/t/getting-kibana-on-host/137938/5 "2018-06-29T11:03:06Z")
But that is not Kibana listening on `0.0.0.0:5601`. ---
**Author:** ![Marcos\_Felix](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marcos_felix/32/32486_2.png) [@Marcos\_Felix](https://discuss.elastic.co/u/Marcos_Felix)\ **Post date:** [June 29, 2018, 11:36am UTC](https://discuss.elastic.co/t/getting-kibana-on-host/137938/6 "2018-06-29T11:36:11Z")
> [@Christian\_Dahlqvist](#): > > 0.0.0.0:5601 I changed the network.host to 0.0.0.0 from my IP. This is the new list on netstat tcp 0 0 0.0.0.0:5601 0.0.0.0:\* LISTEN 32003/node tcp 0 0 0.0.0.0:2049 0.0.0.0:\* LISTEN - tcp 0 0 0.0.0.0:56783 0.0.0.0:\* LISTEN 22062/rpc.mountd tcp 0 0 0.0.0.0:111 0.0.0.0:\* LISTEN 21425/rpcbind tcp 0 0 0.0.0.0:80 0.0.0.0:\* LISTEN 31604/nginx: master tcp 0 0 127.0.0.53:53 0.0.0.0:\* LISTEN 309/systemd-resolve tcp 0 0 0.0.0.0:22 0.0.0.0:\* LISTEN 645/sshd tcp 0 0 0.0.0.0:35959 0.0.0.0:\* LISTEN - tcp 0 0 0.0.0.0:34775 0.0.0.0:\* LISTEN 22062/rpc.mountd tcp 0 0 127.0.0.1:631 0.0.0.0:\* LISTEN 527/cupsd tcp 0 0 0.0.0.0:42361 0.0.0.0:\* LISTEN 22062/rpc.mountd tcp 0 0 0.0.0.0:443 0.0.0.0:\* LISTEN 31604/nginx: master tcp6 0 0 :::2049 :::\* LISTEN - tcp6 0 0 :::38817 :::\* LISTEN 22062/rpc.mountd tcp6 0 0 :::54211 :::\* LISTEN 22062/rpc.mountd tcp6 0 0 :::35951 :::\* LISTEN - tcp6 0 0 :::111 :::\* LISTEN 21425/rpcbind tcp6 0 0 :::9200 :::\* LISTEN 32080/java tcp6 0 0 :::9300 :::\* LISTEN 32080/java tcp6 0 0 :::5044 :::\* LISTEN 31779/java tcp6 0 0 :::53461 :::\* LISTEN 22062/rpc.mountd tcp6 0 0 :::22 :::\* LISTEN 645/sshd tcp6 0 0 ::1:631 :::\* LISTEN 527/cupsd tcp6 0 0 :::5400 :::\* LISTEN 31779/java tcp6 0 0 127.0.0.1:9600 :::\* LISTEN 31779/java ---
**Author:** ![Marcos\_Felix](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marcos_felix/32/32486_2.png) [@Marcos\_Felix](https://discuss.elastic.co/u/Marcos_Felix)\ **Post date:** [June 29, 2018, 12:00pm UTC](https://discuss.elastic.co/t/getting-kibana-on-host/137938/7 "2018-06-29T12:00:30Z")
> [@Christian\_Dahlqvist](#): > > is not Kibana listening on `0.0.0.0:5601` . I just tried to connect to the VM IP and a security warning popped up. I proceeded and it asked me for credentials. I entered them and it gave 403 fobidden nginx/1.14.0(ubuntu) ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [June 29, 2018, 12:01pm UTC](https://discuss.elastic.co/t/getting-kibana-on-host/137938/8 "2018-06-29T12:01:28Z")
Seems to be a problem with nginx then? ---
**Author:** ![Marcos\_Felix](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marcos_felix/32/32486_2.png) [@Marcos\_Felix](https://discuss.elastic.co/u/Marcos_Felix)\ **Post date:** [June 29, 2018, 12:14pm UTC](https://discuss.elastic.co/t/getting-kibana-on-host/137938/9 "2018-06-29T12:14:02Z")
but why is it only connecting through the VM's IP? surely it should be the one I specified which is the hosts IP ---
**Author:** ![Marcos\_Felix](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marcos_felix/32/32486_2.png) [@Marcos\_Felix](https://discuss.elastic.co/u/Marcos_Felix)\ **Post date:** [June 29, 2018, 12:37pm UTC](https://discuss.elastic.co/t/getting-kibana-on-host/137938/10 "2018-06-29T12:37:54Z")
Well nvm, I just went back to the tab and Kibana loaded, I didn't change anything or do anything. Just took a snapshot of the VM. Well....welll....well ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 27, 2018, 12:38pm UTC](https://discuss.elastic.co/t/getting-kibana-on-host/137938/11 "2018-07-27T12:38:05Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.