# Cannot access Kibana remotely or on local machine **URL:** \ **Category:** Kibana\ **Created:** [August 27, 2019, 6:09pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-remotely-or-on-local-machine/196986 "2019-08-27T18:09:19Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![Terran](https://avatars.discourse-cdn.com/v4/letter/t/94ad74/32.png) [@Terran](https://discuss.elastic.co/u/Terran)\ **Post date:** [August 27, 2019, 6:09pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-remotely-or-on-local-machine/196986/1 "2019-08-27T18:09:19Z")
I have installed ES in a 3 node cluster. I have Kibana on #3 as well. ES is running fine as far as I can tell. Kibana installed and started fine. I have edited the .yml file with the following Contents of kibana.yml server.port: 5601 server.host: "0.0.0.0" server.name: "name" elasticsearch.hosts: ["[http://localhost:9200](http://localhost:9200)"] I have checked for a listener [clintd@pdxelastictest03 kibana]$ netstat -nat | grep 5601 tcp 0 0 0.0.0.0:5601 0.0.0.0:\* LISTEN [clintd@pdxelastictest03 kibana]$ netstat -nat | grep 9200 tcp6 0 0 127.0.0.1:9200 :::\* LISTEN tcp6 0 0 ::1:9200 :::\* LISTEN Attempted to connect from the local machine [clintd@pdxelastictest03 kibana]$ curl '10.6.48.235:5061' curl: (7) Failed connect to 10.6.48.235:5061; Connection refused Found this in the logs: [clintd@pdxelastictest03 kibana]$ vi kibana.stderr FATAL Error: Port 5601 is already in use. Another instance of Kibana may be running! I don't see anything that would suggest Kibana is running anywhere else. I am at a loss. Anyone have ideas that would help me? ---
**Author:** ![mattkime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattkime/32/43522_2.png) [@mattkime](https://discuss.elastic.co/u/mattkime)\ **Post date:** [August 27, 2019, 6:21pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-remotely-or-on-local-machine/196986/2 "2019-08-27T18:21:52Z")
Which OS are you running? You might try `lsof -i :5601` without kibana running to try to determine whether another process is using 5601. ---
**Author:** ![Terran](https://avatars.discourse-cdn.com/v4/letter/t/94ad74/32.png) [@Terran](https://discuss.elastic.co/u/Terran)\ **Post date:** [August 28, 2019, 12:42pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-remotely-or-on-local-machine/196986/3 "2019-08-28T12:42:15Z")
That didn't return any values. ---
**Author:** ![mattkime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattkime/32/43522_2.png) [@mattkime](https://discuss.elastic.co/u/mattkime)\ **Post date:** [August 28, 2019, 2:51pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-remotely-or-on-local-machine/196986/4 "2019-08-28T14:51:20Z")
What kind of cluster are you running? How are you starting the instances? ---
**Author:** ![Terran](https://avatars.discourse-cdn.com/v4/letter/t/94ad74/32.png) [@Terran](https://discuss.elastic.co/u/Terran)\ **Post date:** [August 28, 2019, 3:36pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-remotely-or-on-local-machine/196986/5 "2019-08-28T15:36:33Z")
I'm afraid I don't understand the question. I have 3 nodes running ES, I edited the .yml files for each indicating their partners and manually started each one. ---
**Author:** ![mattkime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattkime/32/43522_2.png) [@mattkime](https://discuss.elastic.co/u/mattkime)\ **Post date:** [August 28, 2019, 3:40pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-remotely-or-on-local-machine/196986/6 "2019-08-28T15:40:02Z")
It sounds like something is trying to start kibana more than once in one of your environments. Are you using a cloud provider? Kubernetes or something similar, etc? ---
**Author:** ![Terran](https://avatars.discourse-cdn.com/v4/letter/t/94ad74/32.png) [@Terran](https://discuss.elastic.co/u/Terran)\ **Post date:** [August 28, 2019, 4:22pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-remotely-or-on-local-machine/196986/7 "2019-08-28T16:22:36Z")
It is an on-prem set up. I only have Kibana set up on server #3. I have tried to find anything like it trying to start Kibana twice, or anything else that would claim 5601 but no dice. ---
**Author:** ![mattkime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattkime/32/43522_2.png) [@mattkime](https://discuss.elastic.co/u/mattkime)\ **Post date:** [August 28, 2019, 4:23pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-remotely-or-on-local-machine/196986/8 "2019-08-28T16:23:45Z")
Are you starting kibana manually from the command line? If so, what command are you running? ---
**Author:** ![Terran](https://avatars.discourse-cdn.com/v4/letter/t/94ad74/32.png) [@Terran](https://discuss.elastic.co/u/Terran)\ **Post date:** [August 28, 2019, 4:24pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-remotely-or-on-local-machine/196986/9 "2019-08-28T16:24:00Z")
sudo systemctl start kibana ---
**Author:** ![mattkime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattkime/32/43522_2.png) [@mattkime](https://discuss.elastic.co/u/mattkime)\ **Post date:** [September 1, 2019, 4:05am UTC](https://discuss.elastic.co/t/cannot-access-kibana-remotely-or-on-local-machine/196986/10 "2019-09-01T04:05:28Z")
Curious if you've made any progress. What does your `kibana.service` file look like? ---
**Author:** ![Terran](https://avatars.discourse-cdn.com/v4/letter/t/94ad74/32.png) [@Terran](https://discuss.elastic.co/u/Terran)\ **Post date:** [September 3, 2019, 11:42am UTC](https://discuss.elastic.co/t/cannot-access-kibana-remotely-or-on-local-machine/196986/11 "2019-09-03T11:42:36Z")
No, I have not made any progress unfortunately / fortunately. I am out on vacation for the next 6 days. I will post my file when I return. TY for following up with me. ---
**Author:** ![NewmazN24](https://avatars.discourse-cdn.com/v4/letter/n/b77776/32.png) [@NewmazN24](https://discuss.elastic.co/u/NewmazN24)\ **Post date:** [September 3, 2019, 7:27pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-remotely-or-on-local-machine/196986/12 "2019-09-03T19:27:03Z")
Hey, server.port: 5601 server.host: "0.0.0.0" server.name: "name" **elasticsearch.hosts: ["[http://localhost:9200](http://localhost:9200)"]** You are telling Kibana to look for himself as an elastic hosts. server.port: 5601 server.host: "0.0.0.0" server.name: "name" elasticsearch.hosts: ["http:// **YourElasticHost1** :9200", "http:// **YourElasticHost2** :9200"] Also, since you are running machines, if you are on CentOS7, make sure you have authorized access through your firewall. Test firewall-cmd --permanent --add-port=5601/tcp, then --reload. ---
**Author:** ![Terran](https://avatars.discourse-cdn.com/v4/letter/t/94ad74/32.png) [@Terran](https://discuss.elastic.co/u/Terran)\ **Post date:** [September 9, 2019, 4:00pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-remotely-or-on-local-machine/196986/13 "2019-09-09T16:00:42Z")
I attempted that and still no luck. Output below: .yml file details- server.port: 5601 server.host: "0.0.0.0" server.name: "name" elasticsearch.hosts: ["[http://hostname01:9200](http://hostname01:9200), "[http://hostname02:9200](http://hostname02:9200)"] # firewall-cmd --permanent --add-port=5601/tcp success # systemctl stop kibana # systemctl start kibana # systemctl status kibana ● kibana.service - Kibana Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: disabled) Active: active (running) since Mon 2019-09-09 08:52:54 PDT; 36ms ago Main PID: 6594 (node) CGroup: /system.slice/kibana.service └─6594 /usr/share/kibana/bin/../node/bin/node --no-warnings --max-http-header-... # curl [http://10.6.48.235:5601/api/status](http://10.6.48.235:5601/api/status) curl: (7) Failed connect to 10.6.48.235:5601; Connection refused ---
**Author:** ![mattkime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattkime/32/43522_2.png) [@mattkime](https://discuss.elastic.co/u/mattkime)\ **Post date:** [October 4, 2019, 9:14pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-remotely-or-on-local-machine/196986/14 "2019-10-04T21:14:07Z")
Apologies for letting this drop, did you ever solve it? If not, lets take another swing at it. Thanks ---
**Author:** ![Terran](https://avatars.discourse-cdn.com/v4/letter/t/94ad74/32.png) [@Terran](https://discuss.elastic.co/u/Terran)\ **Post date:** [October 7, 2019, 12:09pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-remotely-or-on-local-machine/196986/15 "2019-10-07T12:09:39Z")
No, I was unable to resolve this. After attempting to get the communication to work with the cluster I decided to try and simplify. I uninstalled ES and Kibana one the node in question, then reinstalled as a single node deployment with the intent, that if I could get it working as a single node I could add the other cluster members later. This seemed to help somewhat, but now I receive a notice when attempting to browse to my kibana IP address that, "The Kibana server is not ready." I am not working through this, but seem stalled again. ---
**Author:** ![Terran](https://avatars.discourse-cdn.com/v4/letter/t/94ad74/32.png) [@Terran](https://discuss.elastic.co/u/Terran)\ **Post date:** [October 31, 2019, 5:33pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-remotely-or-on-local-machine/196986/16 "2019-10-31T17:33:56Z")
I have resolved this. How do I close it? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 28, 2019, 5:33pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-remotely-or-on-local-machine/196986/17 "2019-11-28T17:33:56Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.