# 🎉 Node-RED 2.1.4 released

**URL:** <https://discourse.nodered.org/t/node-red-2-1-4-released/54622>\
**Category:** News\
**Created:** [2 December 2021 09:46 UTC](https://discourse.nodered.org/t/node-red-2-1-4-released/54622 "2021-12-02T09:46:35Z")\
**Posts on this page:** 6\
**Page:** 3

<div class="post-metadata">

**Author:** ![Christian-Me](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/christian-me/32/10774_2.png) [@Christian-Me](https://discourse.nodered.org/u/Christian-Me)\
**Post date:** [6 January 2022 15:53 UTC](https://discourse.nodered.org/t/node-red-2-1-4-released/54622/41 "2022-01-06T15:53:52Z")

</div>

Hi ... found a nasty bug ...

difficult to reproduce, but I give it a try.

- edited the subflow enviroment Variables like this

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/1/11fd49ce3ec6c6f7dc988f9e4511869212877de6.png)

- pressed done
- testing the "action" disappears and the dialog crashed

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/e/f/ef04f04e4a60f4354fbdbd5fc9a8626a5b213e76.png)

- not able to edit anything later ...
- exported the subflow
- analysed the problem:

```auto
                    "opts": {
                        "opts": [
                            {
                                "l": {
                                    "en-US": "Auto"
                                },
                                "v": "auto"
                            },
                            {
                                "l": {
                                    "en-US": "Add"
                                },
                                "v": "add"
                            },
                            {
                                "l": {
                                    "en-US": "Toggle"
                                },
                                "v": "toggle"
                            },
                            {
                                "v": "loop"
                            }
                        ]

```

... something missing

No a real problem because I could fix it during import and replace the old version  
Little note ... I was in the German version of the editor at this time. (promise that I will never do that again 😉

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [6 January 2022 16:07 UTC](https://discourse.nodered.org/t/node-red-2-1-4-released/54622/42 "2022-01-06T16:07:17Z")

</div>

If you've found a reproducable bug in the current release, please raise an issue on github with details. That will ensure it doesn't get overlooked/forgotten about.

---

<div class="post-metadata">

**Author:** ![Christian-Me](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/christian-me/32/10774_2.png) [@Christian-Me](https://discourse.nodered.org/u/Christian-Me)\
**Post date:** [6 January 2022 18:59 UTC](https://discourse.nodered.org/t/node-red-2-1-4-released/54622/43 "2022-01-06T18:59:51Z")

</div>

If I manage to really reproduce this I will.

---

<div class="post-metadata">

**Author:** ![gabric098](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gabric098/32/53854_2.png) [@gabric098](https://discourse.nodered.org/u/gabric098)\
**Post date:** [9 January 2022 14:58 UTC](https://discourse.nodered.org/t/node-red-2-1-4-released/54622/44 "2022-01-09T14:58:59Z")

</div>

Hi,  
I've been running node-red in my home automation dockerized stack for quite a while now and I always upgraded without any issue. This time, upgrading from:

```auto
image: nodered/node-red:2.1.3

```

to

```auto
image: nodered/node-red:2.1.4

```

the container doesn't start anymore throwing this error:

```auto
#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbea2a16c

```

My stack is defined in a `docker-compose.yaml` running on a raspberry pi 4. The image I pull should be this one:  
[https://hub.docker.com/layers/nodered/node-red/2.1.4/images/sha256-379a162f0d4614357e9204c7dfe5d0c214516c5850867dab5c4c7139d4cf00c0?context=explore](https://hub.docker.com/layers/nodered/node-red/2.1.4/images/sha256-379a162f0d4614357e9204c7dfe5d0c214516c5850867dab5c4c7139d4cf00c0?context=explore)

does anyone have the same issue?

Thank you,  
Gab

---

<div class="post-metadata">

**Author:** ![gabric098](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gabric098/32/53854_2.png) [@gabric098](https://discourse.nodered.org/u/gabric098)\
**Post date:** [10 January 2022 14:41 UTC](https://discourse.nodered.org/t/node-red-2-1-4-released/54622/45 "2022-01-10T14:41:25Z")

</div>

regarding my previous answer. I just noticed that a fixed tag `2.1.4-1` has been created and should be used.  
So for anyone upgrading on docker, please use

```auto
image: nodered/node-red:2.1.4-1

```

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [11 March 2022 14:42 UTC](https://discourse.nodered.org/t/node-red-2-1-4-released/54622/46 "2022-03-11T14:42:02Z")

</div>

Closed on 11 March 2022 14:42 UTC

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

[Previous page](https://discourse.nodered.org/t/node-red-2-1-4-released/54622.md?page=2)
