# Question - How do you upgrade the Docker install of Eramba?

**URL:** https://discussions.eramba.org/t/question-how-do-you-upgrade-the-docker-install-of-eramba/2644
**Category:** Forum - Installation
**Created:** [January 17, 2023, 2:24pm UTC](https://discussions.eramba.org/t/question-how-do-you-upgrade-the-docker-install-of-eramba/2644 "2023-01-17T14:24:56Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![nick.yonko](https://discussions.eramba.org/letter_avatar_proxy/v4/letter/n/9fc29f/32.png) [@nick.yonko](https://discussions.eramba.org/u/nick.yonko)
#### Post date: [January 17, 2023, 2:24pm UTC](https://discussions.eramba.org/t/question-how-do-you-upgrade-the-docker-install-of-eramba/2644/1 "2023-01-17T14:24:56Z")

</div>

I am running Eramba 3.17.0

---

<div class="post-metadata">

### Author: ![sam](https://discussions.eramba.org/letter_avatar_proxy/v4/letter/s/5f9b8f/32.png) [@sam](https://discussions.eramba.org/u/sam)
#### Post date: [January 17, 2023, 2:29pm UTC](https://discussions.eramba.org/t/question-how-do-you-upgrade-the-docker-install-of-eramba/2644/2 "2023-01-17T14:29:45Z")

</div>

Hello,

You have to navigate into settings/updates and if there is an update available, simply click on it.

documentation: [Docker Install | Eramba learning portal](https://www.eramba.org/learning/courses/12/episodes/276)

---

<div class="post-metadata">

### Author: ![rmn0](https://discussions.eramba.org/letter_avatar_proxy/v4/letter/r/977dab/32.png) [@rmn0](https://discussions.eramba.org/u/rmn0)
#### Post date: [February 28, 2023, 12:39pm UTC](https://discussions.eramba.org/t/question-how-do-you-upgrade-the-docker-install-of-eramba/2644/3 "2023-02-28T12:39:17Z")

</div>

Is this available for Enterprise only? I have the community edition an I get the error: “We are not able to authenticate your enterprise ID (Client ID). Please contact our support team.”

---

<div class="post-metadata">

### Author: ![sam](https://discussions.eramba.org/letter_avatar_proxy/v4/letter/s/5f9b8f/32.png) [@sam](https://discussions.eramba.org/u/sam)
#### Post date: [February 28, 2023, 12:40pm UTC](https://discussions.eramba.org/t/question-how-do-you-upgrade-the-docker-install-of-eramba/2644/4 "2023-02-28T12:40:49Z")

</div>

Hello,

You were doing an update from old community version?

---

<div class="post-metadata">

### Author: ![rmn0](https://discussions.eramba.org/letter_avatar_proxy/v4/letter/r/977dab/32.png) [@rmn0](https://discussions.eramba.org/u/rmn0)
#### Post date: [March 2, 2023, 9:37am UTC](https://discussions.eramba.org/t/question-how-do-you-upgrade-the-docker-install-of-eramba/2644/5 "2023-03-02T09:37:47Z")

</div>

No, 3.17

And as context, the crons are not working in this version and can’t get them to work.

 ![Screenshot 2023-03-02 at 11.39.59](https://discussions.eramba.org/uploads/default/original/2X/d/d33f3a24d353a79f073742a52d2bea82dbf3caec.png)

---

<div class="post-metadata">

### Author: ![sam](https://discussions.eramba.org/letter_avatar_proxy/v4/letter/s/5f9b8f/32.png) [@sam](https://discussions.eramba.org/u/sam)
#### Post date: [March 2, 2023, 7:34pm UTC](https://discussions.eramba.org/t/question-how-do-you-upgrade-the-docker-install-of-eramba/2644/6 "2023-03-02T19:34:28Z")

</div>

Strange. Please write to our support email and we will do a quick call so I can see what is the problem.

---

<div class="post-metadata">

### Author: ![sam](https://discussions.eramba.org/letter_avatar_proxy/v4/letter/s/5f9b8f/32.png) [@sam](https://discussions.eramba.org/u/sam)
#### Post date: [March 7, 2023, 9:41am UTC](https://discussions.eramba.org/t/question-how-do-you-upgrade-the-docker-install-of-eramba/2644/7 "2023-03-07T09:41:25Z")

</div>

Three problems were found here:

- after migration from community version 2 you have to reset the app ID to obtain a new one, we added this step into the migration procedure as well
- missing public address setting - we will also fix this one with release 3.19.0, the public address will be an environmental variable and you will also see error in cron history
- we also needed to update the docker folder repository, it was not the latest
