# Can't connect to kibana on google cloud ubuntu vm

**URL:** <https://discuss.elastic.co/t/cant-connect-to-kibana-on-google-cloud-ubuntu-vm/123394>\
**Category:** Kibana\
**Created:** [March 10, 2018, 6:27pm UTC](https://discuss.elastic.co/t/cant-connect-to-kibana-on-google-cloud-ubuntu-vm/123394 "2018-03-10T18:27:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jtalmi](https://avatars.discourse-cdn.com/v4/letter/j/ecb155/32.png) [@jtalmi](https://discuss.elastic.co/u/jtalmi)\
**Post date:** [March 10, 2018, 6:27pm UTC](https://discuss.elastic.co/t/cant-connect-to-kibana-on-google-cloud-ubuntu-vm/123394/1 "2018-03-10T18:27:45Z")

</div>

tl;dr I can start the kibana service but port 5601 doesn't open.

I'm having trouble setting up kibana on a brand new ubuntu instance on google cloud platform. I have elasticsearch up and running on localhost:9200, but when I installed kibana using the instructions `[here](https://www.elastic.co/guide/en/kibana/current/deb.html)`, it doesn't work.

My elasticsearch.yml config:

`network.host: 0.0.0.0`  
`http.port: 9200-9300`

`curl localhost:9200` works fine.

My kibana config:

`server.port: 5601`  
`server.host: "0.0.0.0"`  
`elasticsearch.url: "http://localhost:9200"`  
`elasticsearch.preserveHost: true`  
`logging.dest: /var/log/kibana/kibana.log`

Note that I had to add the logging dest because otherwise i wasn't able to start the service using /bin/systemctl.

Now, `sudo /bin/systemctl status kibana.service` reveals that my kibana service is running, but kibana is absent from `sudo netstat -ntpl`, and `curl localhost:5601` yields `Failed to connect to localhost port 5601: Connection refused`

I've tried different configurations of kibana.yml. I've tried setting server.host to localhost, or my google cloud node's internal IP, and it doesn't work.

---

<div class="post-metadata">

**Author:** ![rebirther](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rebirther/32/19228_2.png) [@rebirther](https://discuss.elastic.co/u/rebirther)\
**Post date:** [March 11, 2018, 5:33am UTC](https://discuss.elastic.co/t/cant-connect-to-kibana-on-google-cloud-ubuntu-vm/123394/2 "2018-03-11T05:33:11Z")

</div>

Since you turned on logging, could not you put log here from `/var/log/kibana/kibana.log` file?

I also checked my kibana installation and all fields except `logging.dest` are commented out. Nevertheless, I quietly see kibana on `127.0.0.1:5601`

---

<div class="post-metadata">

**Author:** ![jtalmi](https://avatars.discourse-cdn.com/v4/letter/j/ecb155/32.png) [@jtalmi](https://discuss.elastic.co/u/jtalmi)\
**Post date:** [March 12, 2018, 2:50am UTC](https://discuss.elastic.co/t/cant-connect-to-kibana-on-google-cloud-ubuntu-vm/123394/3 "2018-03-12T02:50:35Z")

</div>

Hi Pavel, I should have followed up.

I turned on logging but nothing was being written to `/var/log/kibana/kibana.log`. I checked it several times.

I ended up installing a new kibana instance using curl straight into my user folder instead of using `apt-get` as I did initially. It worked. I'm not sure if the original problem was a permissions thing or my own incompetence. Thanks for the reply regardless, can you close this now?

---

<div class="post-metadata">

**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\
**Post date:** [March 12, 2018, 4:34am UTC](https://discuss.elastic.co/t/cant-connect-to-kibana-on-google-cloud-ubuntu-vm/123394/4 "2018-03-12T04:34:59Z")

</div>

Thanks for circling back with the solution which worked for you. Closing.

Cheers  
Rashmi

---

<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:** [April 9, 2018, 4:35am UTC](https://discuss.elastic.co/t/cant-connect-to-kibana-on-google-cloud-ubuntu-vm/123394/5 "2018-04-09T04:35:00Z")

</div>

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