# Please read: ECE 1.1.0 upgrade issue and mitigation

**URL:** <https://discuss.elastic.co/t/please-read-ece-1-1-0-upgrade-issue-and-mitigation/108783>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [November 22, 2017, 7:04pm UTC](https://discuss.elastic.co/t/please-read-ece-1-1-0-upgrade-issue-and-mitigation/108783 "2017-11-22T19:04:08Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![suyograo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/suyograo/32/44898_2.png) [@suyograo](https://discuss.elastic.co/u/suyograo)\
**Post date:** [November 22, 2017, 7:04pm UTC](https://discuss.elastic.co/t/please-read-ece-1-1-0-upgrade-issue-and-mitigation/108783/1 "2017-11-22T19:04:08Z")

</div>

Hi all, last week we [released ECE 1.1.0](https://www.elastic.co/blog/elastic-cloud-enterprise-1-1-0-released) with new features and bug fixes. Since then, we've discovered a critical bug that leads to Kibana being unavailable post-upgrade. This bug **only** affects users who upgraded from 1.0.x versions of ECE to 1.1.0. If you freshly installed 1.1.0, your deployments are not affected.

**Issue**

If you upgraded to ECE 1.1.0 and tried to:  
a) restart allocators  
b) increase capacity by adding hosts

You will see Kibana authentication issues and unavailability of monitoring.

**Immediate workaround**

Please see this [blog post](https://www.elastic.co/blog/elastic-cloud-enterprise-1-1-0-upgrade-issues) for a workaround and next steps.

---

<div class="post-metadata">

**Author:** ![suyograo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/suyograo/32/44898_2.png) [@suyograo](https://discuss.elastic.co/u/suyograo)\
**Post date:** [November 22, 2017, 7:04pm UTC](https://discuss.elastic.co/t/please-read-ece-1-1-0-upgrade-issue-and-mitigation/108783/2 "2017-11-22T19:04:41Z")

</div>



---

<div class="post-metadata">

**Author:** ![suyograo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/suyograo/32/44898_2.png) [@suyograo](https://discuss.elastic.co/u/suyograo)\
**Post date:** [November 28, 2017, 5:58am UTC](https://discuss.elastic.co/t/please-read-ece-1-1-0-upgrade-issue-and-mitigation/108783/3 "2017-11-28T05:58:54Z")

</div>

ECE 1.1.1 has been released to address this issue: [https://www.elastic.co/blog/elastic-cloud-enterprise-1-1-1-released](https://www.elastic.co/blog/elastic-cloud-enterprise-1-1-1-released)

---

<div class="post-metadata">

**Author:** ![suyograo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/suyograo/32/44898_2.png) [@suyograo](https://discuss.elastic.co/u/suyograo)\
**Post date:** [November 28, 2017, 5:59am UTC](https://discuss.elastic.co/t/please-read-ece-1-1-0-upgrade-issue-and-mitigation/108783/4 "2017-11-28T05:59:03Z")

</div>



---

<div class="post-metadata">

**Author:** ![suyograo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/suyograo/32/44898_2.png) [@suyograo](https://discuss.elastic.co/u/suyograo)\
**Post date:** [December 12, 2017, 5:59am UTC](https://discuss.elastic.co/t/please-read-ece-1-1-0-upgrade-issue-and-mitigation/108783/5 "2017-12-12T05:59:15Z")

</div>

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