# Problem connecting Kibana to remote ES cluster
**URL:** https://discuss.elastic.co/t/problem-connecting-kibana-to-remote-es-cluster/198004
**Category:** Kibana
**Created:** [September 4, 2019, 8:28am UTC](https://discuss.elastic.co/t/problem-connecting-kibana-to-remote-es-cluster/198004 "2019-09-04T08:28:21Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@theaxe](https://discuss.elastic.co/u/theaxe)
#### Post date: [September 4, 2019, 8:28am UTC](https://discuss.elastic.co/t/problem-connecting-kibana-to-remote-es-cluster/198004/1 "2019-09-04T08:28:21Z")
Hi y'all
I'm kinda new to ELK and trying to setup an environment to monitor my ES "version 2.4" cluster.
My environment consists of a cluster of 3 nodes, production, then a server running Kibana, and Logstash n Beats.
On the machine running Kibana i have installed ES "version 6.8.2" to test out the environment and kibana has no issues accessing it from `elk.XXX.XXX.XXX.XXX.xip.io`, however once i change the `elasticsearch.hosts: ["http://YYY.YYY.YYY.YYY:9200"]`, this is my production server local IP address which is in the same network as kibana server, under `kibana.yml`, i get the message saying `Kibana server is not ready yet`.
I'm using NGINX to proxy the server.
Would appreciate if anyone could shed some light on my path.
Thanks
---
### Author:  [@Aaron\_Caldwell](https://discuss.elastic.co/u/Aaron_Caldwell)
#### Post date: [September 4, 2019, 8:33pm UTC](https://discuss.elastic.co/t/problem-connecting-kibana-to-remote-es-cluster/198004/2 "2019-09-04T20:33:03Z")
Hello Alex,
Have you exposed port 9200 on your production server hosting Elasticsearch? What happens when you run the following command from your Kibana host using your server's ip address?
```auto
curl -X GET ":9200/_cat/health?v&pretty"
```
Regards,
Aaron
---
### Author:  [@theaxe](https://discuss.elastic.co/u/theaxe)
#### Post date: [September 5, 2019, 4:04am UTC](https://discuss.elastic.co/t/problem-connecting-kibana-to-remote-es-cluster/198004/3 "2019-09-05T04:04:31Z")
Hello Aaron
Thanks for you response.
I believe i got this part right, nonetheless here is the result of curl:
---
### Author:  [@theaxe](https://discuss.elastic.co/u/theaxe)
#### Post date: [September 10, 2019, 3:17am UTC](https://discuss.elastic.co/t/problem-connecting-kibana-to-remote-es-cluster/198004/4 "2019-09-10T03:17:24Z")
Could the version of it be the cause?
My ES is ver 2.4 as for the rest of the stack I installed the latest
---
### Author:  [@anon42972578](https://discuss.elastic.co/u/anon42972578)
#### Post date: [September 10, 2019, 11:07am UTC](https://discuss.elastic.co/t/problem-connecting-kibana-to-remote-es-cluster/198004/5 "2019-09-10T11:07:14Z")
as far as i know:
best practice is to upgrade ES always first. When ES is 2.4 , Kibana should be 2.4 or lower.
the different between 2.4 and 6.8.2 is huge 😮
---
### Author:  [@theaxe](https://discuss.elastic.co/u/theaxe)
#### Post date: [September 10, 2019, 12:02pm UTC](https://discuss.elastic.co/t/problem-connecting-kibana-to-remote-es-cluster/198004/6 "2019-09-10T12:02:28Z")
I know, but I'm using the type feature whis is deprecated in 5.2 and above, if I upgrade I'll be royally doomed, I'm trying to upgrade to 5.2 and retry the whole process again
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 8, 2019, 12:02pm UTC](https://discuss.elastic.co/t/problem-connecting-kibana-to-remote-es-cluster/198004/7 "2019-10-08T12:02:31Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.