# Cant connect to ES via http **URL:** \ **Category:** Elasticsearch\ **Created:** [January 4, 2016, 3:58pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-via-http/38327 "2016-01-04T15:58:12Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![andreynikk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andreynikk/32/6873_2.png) [@andreynikk](https://discuss.elastic.co/u/andreynikk)\ **Post date:** [January 4, 2016, 3:58pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-via-http/38327/1 "2016-01-04T15:58:12Z")
Hi, im currently testing migration to ES 2.1, i installed it on a dedicated node. ES started succesfully: [root@XXXbin]# curl -XGET '[http://XXX.XXX.com:9202/\_cat/health](http://XXX.XXX.com:9202/_cat/health)' 1451922644 07:50:44 es\_search\_cluster\_v2 yellow 1 1 3 3 0 0 3 0 - 50.0% the yellow state is because the cluster has 1 node. kibana is succesfully connected: {"type":"log","@timestamp":"2016-01-04T15:39:12+00:00","tags":["warning","elasticsearch"],"pid":2899,"message":"No living connections"} {"type":"log","@timestamp":"2016-01-04T15:39:14+00:00","tags":["status","plugin:elasticsearch","info"],"pid":2899,"name":"plugin:elasticsearch","state":"green","message":"Status changed from red to green - Kibana index ready","prevState":"red","prevMsg":"Unable to connect to Elasticsearch at [http://XXX.XXX.com:9202](http://XXX.XXX.com:9202). Retrying in 2.5 seconds."} and a modified the yml configuration file according to: [https://www.elastic.co/guide/en/elasticsearch/reference/2.1/breaking\_20\_network\_changes.html](https://www.elastic.co/guide/en/elasticsearch/reference/2.1/breaking_20_network_changes.html) i know its not a kibana related issue as i cant connect to any of the plugins i installed via http (HQ, kopf and etc). what am i missing here? ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [January 4, 2016, 4:14pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-via-http/38327/2 "2016-01-04T16:14:25Z")
9202 as a port? You are running more than one instance? Also check network.host setting. You can also copy your logs here. ---
**Author:** ![andreynikk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andreynikk/32/6873_2.png) [@andreynikk](https://discuss.elastic.co/u/andreynikk)\ **Post date:** [January 4, 2016, 4:18pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-via-http/38327/3 "2016-01-04T16:18:35Z")
yes, there are 2 client nodes streaming data. the problem was that that specific node i was testing on couldn't be reached remotely for some reason, connected via a browser in the DC itself and it worked so i have to check why the node is not reachable remotely. thanks for they reply! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:27pm UTC](https://discuss.elastic.co/t/cant-connect-to-es-via-http/38327/4 "2017-07-05T23:27:17Z")