# ECE Upgrade v2.3.2 to v2.4.1

**URL:** <https://discuss.elastic.co/t/ece-upgrade-v2-3-2-to-v2-4-1/207262>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [November 11, 2019, 1:49am UTC](https://discuss.elastic.co/t/ece-upgrade-v2-3-2-to-v2-4-1/207262 "2019-11-11T01:49:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jugsofbeer](https://avatars.discourse-cdn.com/v4/letter/j/9de0a6/32.png) [@Jugsofbeer](https://discuss.elastic.co/u/Jugsofbeer)\
**Post date:** [November 11, 2019, 1:49am UTC](https://discuss.elastic.co/t/ece-upgrade-v2-3-2-to-v2-4-1/207262/1 "2019-11-11T01:49:46Z")

</div>

Hi,

Has anyone tried to do an upgrade on-premise, from ECE 2.3.2 to v2.4.1 on RHEL 7.5 with Docker 1.13?

Does anyone have any feedback on how the new proxy has improved things in your environment ?

We are just wanting to hear about other people's migrations and if there were any lessons learned that you can share.

We have done a lot of reading of the documentation, but keen to hear from others.

---

<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:** [November 25, 2019, 1:49am UTC](https://discuss.elastic.co/t/ece-upgrade-v2-3-2-to-v2-4-1/207262/2 "2019-11-25T01:49:52Z")

</div>

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