# Curl comand is failing

**URL:** <https://discuss.elastic.co/t/curl-comand-is-failing/77881>\
**Category:** Elasticsearch\
**Created:** [March 8, 2017, 7:50pm UTC](https://discuss.elastic.co/t/curl-comand-is-failing/77881 "2017-03-08T19:50:52Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jamir\_Phillips](https://avatars.discourse-cdn.com/v4/letter/j/f475e1/32.png) [@Jamir\_Phillips](https://discuss.elastic.co/u/Jamir_Phillips)\
**Post date:** [March 8, 2017, 7:50pm UTC](https://discuss.elastic.co/t/curl-comand-is-failing/77881/1 "2017-03-08T19:50:52Z")

</div>

I have a two node setup using 5.2.1

Successful:  
Node 1:

curl http://host1\_IPNode1:9200; work w/o issue

Node 2:

curl http://host2\_IPNode2:9200; work w/o issue

Failure:

Node 1:

curl http://host2\_IPNode2:9200; work w/o issue  
curl: (7) Failed connect to XXXXX; No route to host  
Node 2:

curl http://host1\_IPNode1:9200; work w/o issue  
curl: (7) Failed connect to XXXXX; No route to host

For a two node configuration, curl command can be run on either node. Why does it fail and how can I fix?

Tks,

JP

---

<div class="post-metadata">

**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:** [March 8, 2017, 10:25pm UTC](https://discuss.elastic.co/t/curl-comand-is-failing/77881/2 "2017-03-08T22:25:17Z")

</div>

No route to host means that it cannot find a way to connect, can you ping the hosts from each other?

---

<div class="post-metadata">

**Author:** ![Jamir\_Phillips](https://avatars.discourse-cdn.com/v4/letter/j/f475e1/32.png) [@Jamir\_Phillips](https://discuss.elastic.co/u/Jamir_Phillips)\
**Post date:** [March 17, 2017, 3:14pm UTC](https://discuss.elastic.co/t/curl-comand-is-failing/77881/3 "2017-03-17T15:14:33Z")

</div>

Mark,

1st is was a pleasure seeing you in training. Very informative and helpful. I didn't anticipate you would reply to my ES support questions.

The problem is no longer an issue. Both servers were in the same subnet, which led me to believe that this was not a firewall issue. However, I was wrong. Linux has a local firewall service. Once the firewall service was disabled communication worked w/o issue. We will turn the firewall back on both nodes and enabled on the specific ports required.

These are the ports I assume we need.  
Ports: 9200-9300, 5601

Tks,

JP

---

<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 14, 2017, 3:14pm UTC](https://discuss.elastic.co/t/curl-comand-is-failing/77881/4 "2017-04-14T15:14:34Z")

</div>

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