# Ui\_button missing after node-red-dashboard upgrade

**URL:** <https://discourse.nodered.org/t/ui-button-missing-after-node-red-dashboard-upgrade/21321>\
**Category:** Dashboard\
**Created:** [5 February 2020 18:39 UTC](https://discourse.nodered.org/t/ui-button-missing-after-node-red-dashboard-upgrade/21321 "2020-02-05T18:39:01Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![lenny1972](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/lenny1972/32/13210_2.png) [@lenny1972](https://discourse.nodered.org/u/lenny1972)\
**Post date:** [5 February 2020 18:39 UTC](https://discourse.nodered.org/t/ui-button-missing-after-node-red-dashboard-upgrade/21321/1 "2020-02-05T18:39:02Z")

</div>

After upgrading the node-red-dashboard palette from v 2.13.2 to v 2.19.3 ui\_button type disappered from the palette and my flows having button element didn't start anymore.  
The message error is the following:

Flows stopped due to missing node types.

- ui\_button

Close

Node-red v. 0.19.5 running on docker.  
I've already tried to restart the node-red docker - after upgrading the node-red-dashboard palette from within the Editor - but with no success.

Any thoughts?

---

<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 February 2020 18:48 UTC](https://discourse.nodered.org/t/ui-button-missing-after-node-red-dashboard-upgrade/21321/2 "2020-02-05T18:48:29Z")

</div>

Which version of node.js are you using ? Dashboard requires at least node v8, but even that is past end of life so 10 or 12 preferred. Core Node-RED is now at version 1.0.3 also...  
If you need to stay where you are then you may need to revert by using `npm i node-red-dashboard@2.13.2` or some lesser version that does work.

---

<div class="post-metadata">

**Author:** ![lenny1972](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/lenny1972/32/13210_2.png) [@lenny1972](https://discourse.nodered.org/u/lenny1972)\
**Post date:** [5 February 2020 22:20 UTC](https://discourse.nodered.org/t/ui-button-missing-after-node-red-dashboard-upgrade/21321/3 "2020-02-05T22:20:41Z")

</div>

Tomorrow I'll check it and let you know. Thanks for your prompt support.

---

<div class="post-metadata">

**Author:** ![lenny1972](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/lenny1972/32/13210_2.png) [@lenny1972](https://discourse.nodered.org/u/lenny1972)\
**Post date:** [6 February 2020 08:14 UTC](https://discourse.nodered.org/t/ui-button-missing-after-node-red-dashboard-upgrade/21321/4 "2020-02-06T08:14:16Z")

</div>

Here I am dceejay.  
After running the Node-Rer docker and entering the docker (by using `docker attach node-red` command) I get the following error

# Welcome to Node-RED

6 Feb 07:37:48 - [info] Node-RED version: v0.19.5  
6 Feb 07:37:48 - [info] Node.js version: v6.16.0  
6 Feb 07:37:48 - [info] Linux 4.15.0-39-generic x64 LE  
6 Feb 07:37:48 - [info] Loading palette nodes  
6 Feb 07:37:49 - [warn] rpi-gpio : Raspberry Pi specific node set inactive  
6 Feb 07:37:49 - [warn] rpi-gpio : Cannot find Pi RPi.GPIO python library  
6 Feb 07:37:51 - [warn] ------------------------------------------------------  
6 Feb 07:37:51 - [warn] [node-red-dashboard/ui\_button] SyntaxError: Unexpected token ...  
6 Feb 07:37:51 - [warn] ------------------------------------------------------  
6 Feb 07:37:51 - [info] Settings file : /data/settings.js  
6 Feb 07:37:51 - [info] Context store : 'default' [module=memory]  
6 Feb 07:37:51 - [info] User directory : /data  
6 Feb 07:37:51 - [warn] Projects disabled : editorTheme.projects.enabled=false  
6 Feb 07:37:51 - [info] Flows file : /data/flows.json  
6 Feb 07:37:51 - [info] Server now running at [http://127.0.0.1:1880/](http://127.0.0.1:1880/)  
6 Feb 07:37:51 - [warn]

* * *

Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials  
file will not be recoverable, you will have to delete it and re-enter  
your credentials.

## You should set your own key using the 'credentialSecret' option in your settings file. Node-RED will then re-encrypt your credentials file using your chosen key the next time you deploy a change.

6 Feb 07:37:51 - [info] Starting flows  
6 Feb 07:37:51 - [info] Started flows  
6 Feb 07:37:51 - [red] Uncaught Exception:  
6 Feb 07:37:51 - TypeError: Cannot read property 'emit' of undefined  
at /data/node\_modules/node-red-dashboard/ui.js:406:11  
at \_combinedTickCallback (internal/process/next\_tick.js:73:7)  
at process.\_tickCallback (internal/process/next\_tick.js:104:9)

npm ERR! Linux 4.15.0-39-generic  
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start" "--" "--userDir" "/data"  
npm ERR! node v6.16.0  
npm ERR! npm v3.10.10  
npm ERR! code ELIFECYCLE  
npm ERR! node-red-docker@1.0.0 start: `node $NODE_OPTIONS node_modules/node-red/red.js -v $FLOWS "--userDir" "/data"`  
npm ERR! Exit status 1  
npm ERR!  
npm ERR! Failed at the node-red-docker@1.0.0 start script 'node $NODE\_OPTIONS node\_modules/node-red/red.js -v $FLOWS "--userDir" "/data"'.  
npm ERR! Make sure you have the latest version of node.js and npm installed.  
npm ERR! If you do, this is most likely a problem with the node-red-docker package,  
npm ERR! not with npm itself.  
npm ERR! Tell the author that this fails on your system:  
npm ERR! node $NODE\_OPTIONS node\_modules/node-red/red.js -v $FLOWS "--userDir" "/data"  
npm ERR! You can get information on how to open an issue for this project with:  
npm ERR! npm bugs node-red-docker  
npm ERR! Or if that isn't available, you can get their info via:  
npm ERR! npm owner ls node-red-docker  
npm ERR! There is likely additional logging output above.  
npm ERR! Linux 4.15.0-39-generic  
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start" "--" "--userDir" "/data"  
npm ERR! node v6.16.0  
npm ERR! npm v3.10.10  
npm ERR! path npm-debug.log.896050243  
npm ERR! code EACCES  
npm ERR! errno -13  
npm ERR! syscall open

npm ERR! Error: EACCES: permission denied, open 'npm-debug.log.896050243'  
npm ERR! at Error (native)  
npm ERR! { Error: EACCES: permission denied, open 'npm-debug.log.896050243'  
npm ERR! at Error (native)  
npm ERR! errno: -13,  
npm ERR! code: 'EACCES',  
npm ERR! syscall: 'open',  
npm ERR! path: 'npm-debug.log.896050243' }  
npm ERR!  
npm ERR! Please try running this command again as root/Administrator.

npm ERR! Please include the following file with any support request:  
npm ERR! /usr/src/node-red/npm-debug.log

The node version provided with the docker image I use is node v6.16.0.

From the log it's clear that the dashboard module (after the upgrade to the last version from within the NOde-red IDE) didnt't load anymore. Is there a way to update the node-dashboard from within the node-red docker container? Do I have to launch the command you suggest me (`npm i node-red-dashboard@2.13.2`) when I'm attached to the node-red docker?

Otherwise I was thinking to to delete the node-red docker instance and create a new one (after backing-up flows, settings and credential files).. What do you think its the best option?

---

<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 February 2020 09:41 UTC](https://discourse.nodered.org/t/ui-button-missing-after-node-red-dashboard-upgrade/21321/5 "2020-02-06T09:41:08Z")

</div>

As long as you do the backup then yes I would start with another new docker container from [https://hub.docker.com/r/nodered/node-red](https://hub.docker.com/r/nodered/node-red) as that is up to date.

---

<div class="post-metadata">

**Author:** ![lenny1972](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/lenny1972/32/13210_2.png) [@lenny1972](https://discourse.nodered.org/u/lenny1972)\
**Post date:** [6 February 2020 20:26 UTC](https://discourse.nodered.org/t/ui-button-missing-after-node-red-dashboard-upgrade/21321/6 "2020-02-06T20:26:09Z")

</div>

Solved by pulling the last Node-Red docker image and run a new container from that. This solved the dashboard problems.

---

<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:** [20 February 2020 20:26 UTC](https://discourse.nodered.org/t/ui-button-missing-after-node-red-dashboard-upgrade/21321/7 "2020-02-20T20:26:14Z")

</div>

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