# Connectivity issues with a new/upgraded 2.X cluster? Read here first :)

**URL:** <https://discuss.elastic.co/t/connectivity-issues-with-a-new-upgraded-2-x-cluster-read-here-first/35699>\
**Category:** Elasticsearch\
**Created:** [November 27, 2015, 1:44am UTC](https://discuss.elastic.co/t/connectivity-issues-with-a-new-upgraded-2-x-cluster-read-here-first/35699 "2015-11-27T01:44:23Z")\
**Posts on this page:** 1\
**Showing post:** 7

<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:** [January 24, 2016, 3:31am UTC](https://discuss.elastic.co/t/connectivity-issues-with-a-new-upgraded-2-x-cluster-read-here-first/35699/7 "2016-01-24T03:31:50Z")

</div>

Well it's connecting to a valid interface.

I'd suggest you create a separate thread and ask, I don't think this is a settings issue related to the original post.

---

_[View the full topic](https://discuss.elastic.co/t/connectivity-issues-with-a-new-upgraded-2-x-cluster-read-here-first/35699)._
