# "This site can't be reached" when trying to access Kibana **URL:** \ **Category:** Kibana\ **Created:** [February 15, 2019, 4:54am UTC](https://discuss.elastic.co/t/this-site-cant-be-reached-when-trying-to-access-kibana/168514 "2019-02-15T04:54:27Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![johnyom](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/johnyom/32/40699_2.png) [@johnyom](https://discuss.elastic.co/u/johnyom)\ **Post date:** [February 15, 2019, 4:54am UTC](https://discuss.elastic.co/t/this-site-cant-be-reached-when-trying-to-access-kibana/168514/1 "2019-02-15T04:54:27Z")
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](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](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? ---
**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\ **Post date:** [February 18, 2019, 7:57pm UTC](https://discuss.elastic.co/t/this-site-cant-be-reached-when-trying-to-access-kibana/168514/2 "2019-02-18T19:57:10Z")
@jbudz Thanks, Bhavya ---
**Author:** ![jbudz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jbudz/32/45922_2.png) [@jbudz](https://discuss.elastic.co/u/jbudz)\ **Post date:** [February 19, 2019, 4:38pm UTC](https://discuss.elastic.co/t/this-site-cant-be-reached-when-trying-to-access-kibana/168514/3 "2019-02-19T16:38:07Z")
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`? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 19, 2019, 4:38pm UTC](https://discuss.elastic.co/t/this-site-cant-be-reached-when-trying-to-access-kibana/168514/4 "2019-03-19T16:38:10Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.