# Rolling Upgrade to 6.8.0

**URL:** <https://discuss.elastic.co/t/rolling-upgrade-to-6-8-0/182168>\
**Category:** Elasticsearch\
**Created:** [May 22, 2019, 8:09am UTC](https://discuss.elastic.co/t/rolling-upgrade-to-6-8-0/182168 "2019-05-22T08:09:31Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dawiro](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dawiro](https://discuss.elastic.co/u/dawiro)\
**Post date:** [May 22, 2019, 8:09am UTC](https://discuss.elastic.co/t/rolling-upgrade-to-6-8-0/182168/1 "2019-05-22T08:09:31Z")

</div>

Hi,  
I have a cluster running at 6.6.2 (basic lic) and want to roll it up to 6.8.0. I'm seeing discovery timeouts after deploying the first 6.8.0 master node.

Does the upgrade to 6.8.0 require me to set settings specifically to allow the node to connect to the existing cluster? Atm, I have `xpack.security.enabled: false` set in my config...

Regards,  
D

---

<div class="post-metadata">

**Author:** ![dawiro](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dawiro](https://discuss.elastic.co/u/dawiro)\
**Post date:** [May 22, 2019, 2:18pm UTC](https://discuss.elastic.co/t/rolling-upgrade-to-6-8-0/182168/2 "2019-05-22T14:18:50Z")

</div>

Think I've found the issue. Rogue firewalling change in one part of our network. Being investigated...

---

<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:** [June 19, 2019, 2:18pm UTC](https://discuss.elastic.co/t/rolling-upgrade-to-6-8-0/182168/3 "2019-06-19T14:18:54Z")

</div>

Closed on June 19, 2019, 2:18pm UTC

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