# I cant reach Kibana **URL:** \ **Category:** Kibana\ **Created:** [May 29, 2017, 11:08am UTC](https://discuss.elastic.co/t/i-cant-reach-kibana/87437 "2017-05-29T11:08:09Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![mlh1100](https://avatars.discourse-cdn.com/v4/letter/m/51bf81/32.png) [@mlh1100](https://discuss.elastic.co/u/mlh1100)\ **Post date:** [May 29, 2017, 11:08am UTC](https://discuss.elastic.co/t/i-cant-reach-kibana/87437/1 "2017-05-29T11:08:09Z")
Hey. So I'm new with elastic so please be kind if it's an obvious mistake of mine. I installed Kibana via apt and started it with "service kibana start" and looked up its status and i got this: ● kibana.service - Kibana Loaded: loaded (/etc/systemd/system/kibana.service; disabled) Active: active (running) since Mon 2017-05-29 12:43:07 CEST; 7min ago Main PID: 29572 (node) CGroup: /system.slice/kibana.service └─29572 /usr/share/kibana/bin/../node/bin/node --no-warnings /usr/share/kibana/bin/../src/cli -c /etc/kibana/kibana.yml ``` May 29 12:43:07 Debian-85-jessie-64-minimal systemd[1]: Started Kibana. May 29 12:43:09 Debian-85-jessie-64-minimal kibana[29572]: {"type":"log","@timestamp":"2017-05-29T10:43:09Z","tags":["status","plugin:kibana@5.4.0","info"],"pid":29572,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} May 29 12:43:09 Debian-85-jessie-64-minimal kibana[29572]: {"type":"log","@timestamp":"2017-05-29T10:43:09Z","tags":["status","plugin:elasticsearch@5.4.0","info"],"pid":29572,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"} May 29 12:43:09 Debian-85-jessie-64-minimal kibana[29572]: {"type":"log","@timestamp":"2017-05-29T10:43:09Z","tags":["status","plugin:console@5.4.0","info"],"pid":29572,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} May 29 12:43:09 Debian-85-jessie-64-minimal kibana[29572]: {"type":"log","@timestamp":"2017-05-29T10:43:09Z","tags":["status","plugin:elasticsearch@5.4.0","info"],"pid":29572,"state":"green","message":"Status changed from yellow to green - Kibana index ready","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} May 29 12:43:09 Debian-85-jessie-64-minimal kibana[29572]: {"type":"log","@timestamp":"2017-05-29T10:43:09Z","tags":["status","plugin:metrics@5.4.0","info"],"pid":29572,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} May 29 12:43:10 Debian-85-jessie-64-minimal kibana[29572]: {"type":"log","@timestamp":"2017-05-29T10:43:10Z","tags":["status","plugin:timelion@5.4.0","info"],"pid":29572,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} May 29 12:43:10 Debian-85-jessie-64-minimal kibana[29572]: {"type":"log","@timestamp":"2017-05-29T10:43:10Z","tags":["listening","info"],"pid":29572,"message":"Server running at http://127.0.0.1:5611"} May 29 12:43:10 Debian-85-jessie-64-minimal kibana[29572]: {"type":"log","@timestamp":"2017-05-29T10:43:10Z","tags":["status","ui settings","info"],"pid":29572,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} ``` I already Thought that there could be a problem because the status never really switched to green but I continued. I opend Firefox and wanted to enter Kibana but Firefox coudnt open a connection. I reloaded serveral times but nothing happend. I changed the port from 5601 to 5611 nothing happend eather. Then I changed the host from "localhost" to 127.0.0.1 which changed nothing too. Next I used "iptables" to maybe open the port but changed nothing at all... 😕 So my question is what am I doing wrong? Was it installed wrong or is there a bug with my Elasticsearch which btw. I started with no futher configuration. Thank up front for your help. regards Mats ---
**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\ **Post date:** [May 30, 2017, 3:59am UTC](https://discuss.elastic.co/t/i-cant-reach-kibana/87437/2 "2017-05-30T03:59:33Z")
According to the logs, everything should be good: `Status changed from uninitialized to green - Ready`. Are you accessing this from the same machine as it's running on? It's definitely going to be running on port 5601. Also to help when working through this issue. What version of Kibana is this and which Linux distro? ---
**Author:** ![mlh1100](https://avatars.discourse-cdn.com/v4/letter/m/51bf81/32.png) [@mlh1100](https://discuss.elastic.co/u/mlh1100)\ **Post date:** [May 30, 2017, 5:36am UTC](https://discuss.elastic.co/t/i-cant-reach-kibana/87437/3 "2017-05-30T05:36:31Z")
No im entering from another maschine. Kibana's version is 5.4.0 and runs on a linux debian 8 jessie server. And cant I change the port in the kibana.yml? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [May 30, 2017, 5:47am UTC](https://discuss.elastic.co/t/i-cant-reach-kibana/87437/4 "2017-05-30T05:47:52Z")
Kibana listens to localhost by default, which means you cannot connect to it remotely. You need to change `server.host` as per [https://www.elastic.co/guide/en/kibana/5.4/settings.html](https://www.elastic.co/guide/en/kibana/5.4/settings.html) ---
**Author:** ![mlh1100](https://avatars.discourse-cdn.com/v4/letter/m/51bf81/32.png) [@mlh1100](https://discuss.elastic.co/u/mlh1100)\ **Post date:** [May 30, 2017, 6:04am UTC](https://discuss.elastic.co/t/i-cant-reach-kibana/87437/5 "2017-05-30T06:04:02Z")
Yeah I already changed the host to 127.0.0.1 or do i have to change it to another host? In the guide unfortunately doesnt contain the right host for accessing it remotely. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [May 30, 2017, 6:11am UTC](https://discuss.elastic.co/t/i-cant-reach-kibana/87437/6 "2017-05-30T06:11:58Z")
The right host depends on what you want. `0.0.0.0` will listen to all IPs, `127.0.0.1` is localhost. Otherwise specify an IP that is connected to that host. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [May 30, 2017, 6:14am UTC](https://discuss.elastic.co/t/i-cant-reach-kibana/87437/7 "2017-05-30T06:14:23Z")
I've also raised [https://github.com/elastic/kibana/issues/12064](https://github.com/elastic/kibana/issues/12064) to see what we can do to clarify this 🙂 ---
**Author:** ![mlh1100](https://avatars.discourse-cdn.com/v4/letter/m/51bf81/32.png) [@mlh1100](https://discuss.elastic.co/u/mlh1100)\ **Post date:** [May 30, 2017, 6:21am UTC](https://discuss.elastic.co/t/i-cant-reach-kibana/87437/8 "2017-05-30T06:21:12Z")
Thank you/! I cant test it right now but I will test it later! 👍 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 27, 2017, 6:21am UTC](https://discuss.elastic.co/t/i-cant-reach-kibana/87437/9 "2017-06-27T06:21:27Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.