# Node-red doesn't run anymore

**URL:** <https://discourse.nodered.org/t/node-red-doesnt-run-anymore/13437>\
**Category:** Dashboard\
**Created:** [18 July 2019 11:17 UTC](https://discourse.nodered.org/t/node-red-doesnt-run-anymore/13437 "2019-07-18T11:17:39Z")\
**Posts on this page:** 12\
**Page:** 2

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [5 July 2021 08:40 UTC](https://discourse.nodered.org/t/node-red-doesnt-run-anymore/13437/21 "2021-07-05T08:40:50Z")

</div>

Yes - the error log above points to ui.js in dashboard... so yes should be caught there I think.  
Having said that I can't recreate the issue by just disabling either nodes or tabs... so if anyone has a simple example that shows the issue that would be useful.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [5 July 2021 09:35 UTC](https://discourse.nodered.org/t/node-red-doesnt-run-anymore/13437/22 "2021-07-05T09:35:15Z")

</div>

> [@dceejay](#):
>
> I can't recreate the issue by just disabling either nodes or tabs.

Did you try it with the ui-led node? That is the one I saw it on. I haven't seen it on core dashboard nodes.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [5 July 2021 11:08 UTC](https://discourse.nodered.org/t/node-red-doesnt-run-anymore/13437/23 "2021-07-05T11:08:47Z")

</div>

no - I was trying ui-table as per above.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [5 July 2021 13:02 UTC](https://discourse.nodered.org/t/node-red-doesnt-run-anymore/13437/24 "2021-07-05T13:02:47Z")

</div>

It fails for me with ui-table too. I installed ui-table, added a table node and assigned it to a new group on an existing tab and deployed (did not touch the table config or connect anything to it). Then I disabled the group and deployed and got, in the log

```auto
TypeError: Cannot read property 'config' of null
    at addWidget (/home/colinl/.node-red/node_modules/node-red-dashboard/index.js:73:39)
    at Object.addWidget (/home/colinl/.node-red/node_modules/node-red-dashboard/index.js:137:48)
    at new TableNode (/home/colinl/.node-red/node_modules/node-red-node-ui-table/node.js:89:27)
    at Object.createNode (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/util.js:86:27)
    at Flow.start (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:205:48)
    at start (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/index.js:371:33)
5 Jul 13:51:11 - [info] Started modified nodes

```

though I see this is not exactly the same message as reported above.

On further investigation, if instead of disabling the group I disable the tab (using the button down the bottom of the tab config node settings, not the disable field in the config itself) then I get exactly the error reported by @CreativeWarlock.

This is using node-red 2.0.0-Beta2 (I doubt if that is a factor), dashboard 2.29.3 and nodejs 16.4.0

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [5 July 2021 14:40 UTC](https://discourse.nodered.org/t/node-red-doesnt-run-anymore/13437/25 "2021-07-05T14:40:54Z")

</div>

ahhhhh that tab disable - I was using the workspace "tab" disable 🙂

OK - possible fix pushed to master (not on npm)

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [5 July 2021 15:01 UTC](https://discourse.nodered.org/t/node-red-doesnt-run-anymore/13437/26 "2021-07-05T15:01:50Z")

</div>

Is the fix in the dashboard? If so then presumably it should fix the ui-led problem too.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [5 July 2021 18:56 UTC](https://discourse.nodered.org/t/node-red-doesnt-run-anymore/13437/27 "2021-07-05T18:56:53Z")

</div>

Yes in dashboard. So hopefully fixed all over.

---

<div class="post-metadata">

**Author:** ![CreativeWarlock](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/creativewarlock/32/102051_2.png) [@CreativeWarlock](https://discourse.nodered.org/u/CreativeWarlock)\
**Post date:** [5 July 2021 19:33 UTC](https://discourse.nodered.org/t/node-red-doesnt-run-anymore/13437/28 "2021-07-05T19:33:46Z")

</div>

Alright, here we go: [[node-red-node-ui-table]: Cannot read property 'id' of null · Issue #71 · node-red/node-red-ui-nodes · GitHub](https://github.com/node-red/node-red-ui-nodes/issues/71)

I've stripped down my complete Node red flows to the only flow that causes the error on startup in hope that will make debugging as easy as possible.

If you need anything else let me know.

Cheers  
Marcel

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [6 July 2021 10:41 UTC](https://discourse.nodered.org/t/node-red-doesnt-run-anymore/13437/29 "2021-07-06T10:41:34Z")

</div>

Should I be able to install the fix from git using  
`npm install node-red/node-red-dashboard`?  
The install fails, on Ubuntu with nodejs 16.4.0, npm 7.18.1

I thought I would check before posting the large install log, it isn't obvious to me why it won't install, though it does start with

```auto
npm ERR! code 1
npm ERR! git dep preparation failed

```

which I don't remember seeing before.

I had removed the current version first.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [6 July 2021 12:47 UTC](https://discourse.nodered.org/t/node-red-doesnt-run-anymore/13437/30 "2021-07-06T12:47:29Z")

</div>

odd - I have seen it take ages from git before - (but still succeed) - in which case I used yarn add instead...

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [6 July 2021 13:13 UTC](https://discourse.nodered.org/t/node-red-doesnt-run-anymore/13437/31 "2021-07-06T13:13:29Z")

</div>

After a bit of googling to find out how to use it I tried  
`yarn add node-red/node-red-dashboard`  
and I got, after some warnings

```auto
Couldn't find any versions for "uws" that matches "0.13.0"
? Please choose a version of "uws" from this list: (Use arrow keys)

```

followed by a list of options, but uws doesn't seem to be installed, unless it is a new module required by the dashboard. Probably I just don't understand how to use yarn.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [6 July 2021 14:33 UTC](https://discourse.nodered.org/t/node-red-doesnt-run-anymore/13437/32 "2021-07-06T14:33:57Z")

</div>

very weird - only mention I can find of uws i some dep of ws websocket. Let me try on a test machine

[Previous page](https://discourse.nodered.org/t/node-red-doesnt-run-anymore/13437.md?page=1)