"This site can't be reached" when trying to access Kibana

Elastic Stack Kibana
1

I am getting the following message in Chrome when I try to connect to Kibana by entering my public IP address followed by :5601
e.g. 12.34.56.78:5601 (where 12.34.56.78 is replaced with my VM's public IP address)

This site can’t be reached
[MY VM'S PUBLIC IP ADDRESS HERE] refused to connect.
Search Google for 5601
ERR_CONNECTION_REFUSED

Just an FYI: I am able to successfully get a proper response (for elastic search) when entering in Chrome:
http://12.34.56.78:9200 (where 12.34.56.78 is replaced with my VM's public IP address)

My kibana.yml file (in /etc/kibana/) has the following entries:

server.port: 5601
server.host: "12.34.56.78" #where 12.34.56.78 is replaced with my VM's public IP address)
elasticsearch.url: "http://12.34.56.78:9200" #where 12.34.56.78 is replaced with my VM's public IP address)
elasticsearch.preserveHost: true
kibana.index: ".kibana"
xpack.security.enabled: false
elasticsearch.username: "kibana"
elasticsearch.password: "kibanapassword"

When I run "systemctl status kibana.service" I see that kibana is running successfully:

● kibana.service - Kibana
Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2019-02-15 04:34:25 UTC; 576ms ago
Main PID: 16188 (node)
Tasks: 6 (limit: 4915)
CGroup: /system.slice/kibana.service
└─16188 /usr/share/kibana/bin/../node/bin/node --no-warnings /usr/share/kibana/bin/../src/cli -c /etc/kibana/kibana.yml

Feb 15 04:34:25 sb-elastic-upgrade systemd[1]: Started Kibana.

So..... What could I be missing?

2

@jbudz

Thanks,
Bhavya

3

Kibana can have an especially slow startup (on the order of minutes) if a configuration change requires it to rebundle.

Do you see anything interesting in journalctl -u kibana.service?

4

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