# Why connnect dashboard, webpage ✘ Connection lost?
**URL:** https://discourse.nodered.org/t/why-connnect-dashboard-webpage-connection-lost/69869
**Category:** Dashboard
**Created:** [1 November 2022 02:20 UTC](https://discourse.nodered.org/t/why-connnect-dashboard-webpage-connection-lost/69869 "2022-11-01T02:20:25Z")
**Posts on this page:** 19
**Page:** 1
### Author:  [@jackxuhass](https://discourse.nodered.org/u/jackxuhass)
#### Post date: [1 November 2022 02:20 UTC](https://discourse.nodered.org/t/why-connnect-dashboard-webpage-connection-lost/69869/1 "2022-11-01T02:20:25Z")
```
at Socket.Readable.push (internal/streams/readable.js:206:10)
at TCP.onStreamRead (internal/stream_base_commons.js:188:23)
```
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-red-docker@2.1.4 start: `node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-red-docker@2.1.4 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /data/.npm/\_logs/2022-11-01T02\_11\_05\_924Z-debug.log
> node-red-docker@2.1.4 start /usr/src/node-red
> node $NODE\_OPTIONS node\_modules/node-red/red.js $FLOWS "--userDir" "/data"
1 Nov 02:18:23 - [info] [mpd-server:3dd07d3a4643159d] Error: Connection problem? Is the mpd-server 192.168.3.149:6600 running?
Error code: Error: connect EHOSTUNREACH 192.168.3.149:6600
1 Nov 02:18:23 - [info] [mpd-server:3dd07d3a4643159d] Disconnected to MPD server 192.168.3.149:6600
1 Nov 02:18:24 - [warn] [ui\_chart:0758a669fe29e4f7] Bad data inject
1 Nov 02:18:24 - [warn] [ui\_chart:0758a669fe29e4f7] Bad data inject
who help me! thanks!
---
### Author:  [@jackxuhass](https://discourse.nodered.org/u/jackxuhass)
#### Post date: [1 November 2022 02:52 UTC](https://discourse.nodered.org/t/why-connnect-dashboard-webpage-connection-lost/69869/2 "2022-11-01T02:52:33Z")
```
at addChunk (internal/streams/readable.js:293:12)
at readableAddChunk (internal/streams/readable.js:267:9)
at Socket.Readable.push (internal/streams/readable.js:206:10)
at TCP.onStreamRead (internal/stream_base_commons.js:188:23)
```
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-red-docker@2.1.4 start: `node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-red-docker@2.1.4 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /data/.npm/\_logs/2022-11-01T02\_50\_01\_874Z-debug.log
> node-red-docker@2.1.4 start /usr/src/node-red
> node $NODE\_OPTIONS node\_modules/node-red/red.js $FLOWS "--userDir" "/data"
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [1 November 2022 09:42 UTC](https://discourse.nodered.org/t/why-connnect-dashboard-webpage-connection-lost/69869/3 "2022-11-01T09:42:07Z")
Please post the full startup log from the beginning.
I presume mpd is Music Player Daemon. What node are you using for that? Possibly node-red-contrib-something.
---
### Author:  [@jackxuhass](https://discourse.nodered.org/u/jackxuhass)
#### Post date: [1 November 2022 14:56 UTC](https://discourse.nodered.org/t/why-connnect-dashboard-webpage-connection-lost/69869/4 "2022-11-01T14:56:35Z")
chrome ---\> check:
app.min.js:530 Rendered [http://192.168.3.224:1880/ui/css/app.min.less](http://192.168.3.224:1880/ui/css/app.min.less) successfully.
app.min.js:530 CSS for [http://192.168.3.224:1880/ui/css/app.min.less](http://192.168.3.224:1880/ui/css/app.min.less) generated in 54ms
app.min.js:530 Less has finished. CSS generated in 54ms
:1880/ui/socket.io/?EIO=4&transport=polling&t=OGphRn-:1 Failed to load resource: net::ERR\_CONNECTION\_TIMED\_OUT
:1880/ui/socket.io/?EIO=4&transport=polling&t=OGphUVE:1 Failed to load resource: net::ERR\_CONNECTION\_REFUSED
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [1 November 2022 15:18 UTC](https://discourse.nodered.org/t/why-connnect-dashboard-webpage-connection-lost/69869/5 "2022-11-01T15:18:17Z")
What has that got to do with your first post?
---
### Author:  [@jackxuhass](https://discourse.nodered.org/u/jackxuhass)
#### Post date: [1 November 2022 19:34 UTC](https://discourse.nodered.org/t/why-connnect-dashboard-webpage-connection-lost/69869/6 "2022-11-01T19:34:26Z")
> [@Colin](#):
>
> node-red-contrib-something
node-red-contrib-mpd
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [1 November 2022 21:36 UTC](https://discourse.nodered.org/t/why-connnect-dashboard-webpage-connection-lost/69869/7 "2022-11-01T21:36:14Z")
Did you see my earlier request?
> [@Colin](#):
>
> Please post the full node red startup log from the beginning
Also please explain exactly what the problem is.
---
### Author:  [@jackxuhass](https://discourse.nodered.org/u/jackxuhass)
#### Post date: [2 November 2022 08:51 UTC](https://discourse.nodered.org/t/why-connnect-dashboard-webpage-connection-lost/69869/11 "2022-11-02T08:51:22Z")
Thank you very much, Mr. Colin. My nodered dashboard crashed every time it refreshed the ui page, and I updated the container version, which had the same problem. Many hidden node streams were removed in the background, and the night market did not help. (The current prop arm64 v8 2G), I'm going to upgrade my hardware configuration, I don't know if there is any superior configuration for my reference, thanks again! (Here are some logs for your reference.)
---
### Author:  [@jackxuhass](https://discourse.nodered.org/u/jackxuhass)
#### Post date: [2 November 2022 08:52 UTC](https://discourse.nodered.org/t/why-connnect-dashboard-webpage-connection-lost/69869/12 "2022-11-02T08:52:24Z")
After refreshing the ui webpage:
2 Nov 08:19:03 - [red] Uncaught Exception:
2 Nov 08:19:03 - [error] TypeError: bufferUtil.unmask is not a function
at unmask (/data/node\_modules/node-red-dashboard/node\_modules/ws/lib/buffer-util.js:115:23)
at Receiver.getData (/data/node\_modules/node-red-dashboard/node\_modules/ws/lib/receiver.js:420:25)
at Receiver.startLoop (/data/node\_modules/node-red-dashboard/node\_modules/ws/lib/receiver.js:148:22)
at Receiver.\_write (/data/node\_modules/node-red-dashboard/node\_modules/ws/lib/receiver.js:83:10)
at writeOrBuffer (internal/streams/writable.js:358:12)
at Receiver.Writable.write (internal/streams/writable.js:303:10)
at Socket.socketOnData (/data/node\_modules/node-red-dashboard/node\_modules/ws/lib/websocket.js:1116:35)
at Socket.emit (events.js:400:28)
at Socket.emit (domain.js:475:12)
at addChunk (internal/streams/readable.js:293:12)
at readableAddChunk (internal/streams/readable.js:267:9)
at Socket.Readable.push (internal/streams/readable.js:206:10)
at TCP.onStreamRead (internal/stream\_base\_commons.js:188:23)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-red-docker@2.2.3 start: `node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-red-docker@2.2.3 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /data/.npm/\_logs/2022-11-02T08\_19\_03\_473Z-debug.log
> node-red-docker@2.2.3 start /usr/src/node-red
> node $NODE\_OPTIONS node\_modules/node-red/red.js $FLOWS "--userDir" "/data"
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [2 November 2022 09:07 UTC](https://discourse.nodered.org/t/why-connnect-dashboard-webpage-connection-lost/69869/13 "2022-11-02T09:07:48Z")
What I would say is don't use docker unless you have a good reason. It just adds complexity.
---
### Author:  [@jackxuhass](https://discourse.nodered.org/u/jackxuhass)
#### Post date: [2 November 2022 10:15 UTC](https://discourse.nodered.org/t/why-connnect-dashboard-webpage-connection-lost/69869/14 "2022-11-02T10:15:49Z")
Mr. Colin, I would like to refer to your hardware configuration and installation scheme. Could you please give me a list? You are the most enthusiastic playmate I have ever met. I am so lucky to meet you. (Maybe bare installation should be more stable, thanks lot!)
---
### Author:  [@jackxuhass](https://discourse.nodered.org/u/jackxuhass)
#### Post date: [2 November 2022 13:30 UTC](https://discourse.nodered.org/t/why-connnect-dashboard-webpage-connection-lost/69869/15 "2022-11-02T13:30:48Z")
Node-RED v3.x no longer supports Nodejs 10
You can force an install of node 14, 16 or 18 by using the --node14, --node16 or --node18 parameter.
However doing so may break some nodes that may need re-installing manually.
Generally it is recommended to update all nodes to their latest versions before upgrading.
If you wish to stay on nodejs 10 you can update to the latest Node-RED 1.x or 2.x version by adding
--nodered-version="1.3.7" or --nodered-version="2.2.2" to that install command. If in doubt this is the safer option.
Please backup your installation and flows before upgrading.
Note: not all embedded hardware can be updated via this method - please check before proceeding.
Exiting now.
Node-RED v3.x不再支持Nodejs 10
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [2 November 2022 14:14 UTC](https://discourse.nodered.org/t/why-connnect-dashboard-webpage-connection-lost/69869/16 "2022-11-02T14:14:58Z")
Are you asking a question? It is telling you that you need to upgrade nodejs, which you can do by adding, for example, --node16 on the end of the command (after a space). I recommend using 16 at the moment, 18 is still quite new.
`bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered) --node16`
---
### Author:  [@jackxuhass](https://discourse.nodered.org/u/jackxuhass)
#### Post date: [2 November 2022 15:07 UTC](https://discourse.nodered.org/t/why-connnect-dashboard-webpage-connection-lost/69869/18 "2022-11-02T15:07:02Z")
yeah!
nodejs ---\> [GitHub - nvm-sh/nvm: Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions](https://github.com/nvm-sh/nvm)
curl -o- [https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.2/install.sh](https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.2/install.sh) | bash
root@jackxu224:~# node --version
v18.12.0
root@jackxu224:~# npm --version
8.19.2
thanks @Colin
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [2 November 2022 15:14 UTC](https://discourse.nodered.org/t/why-connnect-dashboard-webpage-connection-lost/69869/19 "2022-11-02T15:14:31Z")
> [@jackxuhass](#):
>
> curl -o- [https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.2/install.sh](https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.2/install.sh) | bash
NO, don't use nvm, that will just confuse things. I told you how to do it. Now you may have to work out how to fully remove nvm and start again
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [2 November 2022 15:26 UTC](https://discourse.nodered.org/t/why-connnect-dashboard-webpage-connection-lost/69869/20 "2022-11-02T15:26:40Z")
In case you need it - See this link for removing nvm. [https://github.com/nvm-sh/nvm/issues/298](https://github.com/nvm-sh/nvm/issues/298)
---
### Author:  [@jackxuhass](https://discourse.nodered.org/u/jackxuhass)
#### Post date: [4 November 2022 13:19 UTC](https://discourse.nodered.org/t/why-connnect-dashboard-webpage-connection-lost/69869/21 "2022-11-04T13:19:16Z")
thanks ! I've done it!
---
### Author:  [@jackxuhass](https://discourse.nodered.org/u/jackxuhass)
#### Post date: [7 November 2022 04:48 UTC](https://discourse.nodered.org/t/why-connnect-dashboard-webpage-connection-lost/69869/22 "2022-11-07T04:48:44Z")
☀
Problem solved!
Solution: After creating the nodered container in the docker environment, you must run the command ：
**chown -R 1000:1000 /nodered-home/ nodered-red**
to the physical data volume directory and reboot the host. Have a great day!
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [21 November 2022 04:49 UTC](https://discourse.nodered.org/t/why-connnect-dashboard-webpage-connection-lost/69869/23 "2022-11-21T04:49:07Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.