Getting Kibana on Host


(Marcos Felix) #1

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?


(Marcos Felix) #2

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.


(Christian Dahlqvist) #3

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).


(Marcos Felix) #4

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.


(Christian Dahlqvist) #5

But that is not Kibana listening on 0.0.0.0:5601.


(Marcos Felix) #6

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


(Marcos Felix) #7

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)


(Christian Dahlqvist) #8

Seems to be a problem with nginx then?


(Marcos Felix) #9

but why is it only connecting through the VM's IP? surely it should be the one I specified which is the hosts IP


(Marcos Felix) #10

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


(system) #11

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