# Node-Red Connection Lost
**URL:** https://discourse.nodered.org/t/node-red-connection-lost/1724
**Category:** Dashboard
**Created:** [21 July 2018 06:18 UTC](https://discourse.nodered.org/t/node-red-connection-lost/1724 "2018-07-21T06:18:30Z")
**Posts on this page:** 20
**Page:** 2
### Author:  [@dedynobre](https://discourse.nodered.org/u/dedynobre)
#### Post date: [23 July 2018 18:43 UTC](https://discourse.nodered.org/t/node-red-connection-lost/1724/21 "2018-07-23T18:43:54Z")
I tried to use the xiaomi-mqtt.
Is installed but not used in NR
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [23 July 2018 19:42 UTC](https://discourse.nodered.org/t/node-red-connection-lost/1724/22 "2018-07-23T19:42:51Z")
Uninstall it. It may be doing something.
---
### Author:  [@dedynobre](https://discourse.nodered.org/u/dedynobre)
#### Post date: [23 July 2018 19:50 UTC](https://discourse.nodered.org/t/node-red-connection-lost/1724/23 "2018-07-23T19:50:16Z")
Right.
I'll do this as soon as I get home.
---
### Author:  [@dedynobre](https://discourse.nodered.org/u/dedynobre)
#### Post date: [24 July 2018 09:32 UTC](https://discourse.nodered.org/t/node-red-connection-lost/1724/24 "2018-07-24T09:32:28Z")
Even removing xiaomi and removing several nodes that were not in use, the error still continues.
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [25 July 2018 09:42 UTC](https://discourse.nodered.org/t/node-red-connection-lost/1724/25 "2018-07-25T09:42:55Z")
What other nodes have you got installed and deployed in your flow that do things on the network? One of them has not got proper error handling in place.
---
### Author:  [@dedynobre](https://discourse.nodered.org/u/dedynobre)
#### Post date: [25 July 2018 14:38 UTC](https://discourse.nodered.org/t/node-red-connection-lost/1724/28 "2018-07-25T14:38:59Z")
I apologize for the inconvenience caused by the posts made in different places and that the goal was the same.
I apologize for this.
Currently the components that I have configured outside the default nodes are:
Home Assistant
Broadlink
Redchat
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [25 July 2018 14:46 UTC](https://discourse.nodered.org/t/node-red-connection-lost/1724/29 "2018-07-25T14:46:31Z")
> [@dedynobre](#):
>
> Home Assistant
> Broadlink
> Redchat
Have you tried singling out which of those modules is at fault? Have you checked each of their github pages to see if there are any known issues reported against them?
---
### Author:  [@dedynobre](https://discourse.nodered.org/u/dedynobre)
#### Post date: [25 July 2018 14:57 UTC](https://discourse.nodered.org/t/node-red-connection-lost/1724/30 "2018-07-25T14:57:03Z")
In gitbub I have not found anything that clearly shows the error I am facing.
It has specific functionality errors and is not stopping the NR.
And the log is also confusing to me because it does not make clear something that is clear of the problem and which component.
What part of the log can you assume that something network might be causing the problem?
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [25 July 2018 15:06 UTC](https://discourse.nodered.org/t/node-red-connection-lost/1724/31 "2018-07-25T15:06:16Z")
> [@dedynobre](#):
>
> What part of the log can you assume that something network might be causing the problem?
```auto
Error [ERR_SOCKET_CANNOT_SEND]: Unable to send data
at Socket.onListenError (dgram.js:362:22)
```
The error is related to something failing to send data over a socket.
Nothing in the error tells us which node created that socket or tried to write to it. All it tells us is that an asynchronous error has occurred and whoever created that socket has not added an error handler to cope with these sorts of errors.
---
### Author:  [@zenofmud](https://discourse.nodered.org/u/zenofmud)
#### Post date: [25 July 2018 15:53 UTC](https://discourse.nodered.org/t/node-red-connection-lost/1724/32 "2018-07-25T15:53:06Z")
So pull out one of the nodes and see if the error still occurs, if it does, pull another and repeat. If the error goes away, put the node back in and see if the error re-occurs. That way you should be able to isolate the culprit
---
### Author:  [@dedynobre](https://discourse.nodered.org/u/dedynobre)
#### Post date: [25 July 2018 16:02 UTC](https://discourse.nodered.org/t/node-red-connection-lost/1724/33 "2018-07-25T16:02:04Z")
Right @zenofmud
I just could not identify which component is generating the error because the log does not clarify this issue.
The way it is I will have to remove each component and go testing as the error occurs randomly.
---
### Author:  [@dedynobre](https://discourse.nodered.org/u/dedynobre)
#### Post date: [25 July 2018 16:06 UTC](https://discourse.nodered.org/t/node-red-connection-lost/1724/34 "2018-07-25T16:06:25Z")
Ah okay!
Now it's clear @knolleary
Then you can think of something.
The Telegram component I believe is not the problem because it is more recent and before it presented the problem.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [26 July 2018 06:46 UTC](https://discourse.nodered.org/t/node-red-connection-lost/1724/35 "2018-07-26T06:46:01Z")
When you deploy are you getting a message about unused configuration nodes? If so then follow the link and delete them. Otherwise you have not fully removed nodes from your flow.
---
### Author:  [@cflurin](https://discourse.nodered.org/u/cflurin)
#### Post date: [26 July 2018 09:04 UTC](https://discourse.nodered.org/t/node-red-connection-lost/1724/36 "2018-07-26T09:04:49Z")
> [@dedynobre](#):
>
> 23 Jul 06:34:24 - [red] Uncaught Exception:
> 23 Jul 06:34:24 - Error [ERR\_SOCKET\_CANNOT\_SEND]: Unable to send data
> at Socket.onListenError (dgram.js:362:22)
> at Object.onceWrapper (events.js:315:30)
> at emitOne (events.js:116:13)
> at Socket.emit (events.js:211:7)
> at \_handle.lookup (dgram.js:267:14)
> at \_combinedTickCallback (internal/process/next\_tick.js:141:11)
> at process.\_tickCallback (internal/process/next\_tick.js:180:9)
> nodered.service: Main process exited, code=exited, status=1/FAILURE
> nodered.service: Unit entered failed state.
> nodered.service: Failed with result 'exit-code'.
> nodered.service: Service hold-off time over, scheduling restart.
> Stopped Node-RED graphical event wiring tool.
> Started Node-RED graphical event wiring tool.
Open your `.node-red/flow_???.json` file in an editor and search for `9898`
If there are several matches, then it could be you are trying to open the port in several nodes.
Port `9898` is used in connection with xiaomi (udp node or contrib-nodes)
---
### Author:  [@cflurin](https://discourse.nodered.org/u/cflurin)
#### Post date: [26 July 2018 11:44 UTC](https://discourse.nodered.org/t/node-red-connection-lost/1724/37 "2018-07-26T11:44:53Z")
> [@Colin](#):
>
> Are you using xiaomi-mqtt? If so is it this problem?
> ...
> Uninstall it. It may be doing something.
If you don't start xiaomi-mqtt, the port 9898 isn't used!
Just check it:
```auto
sudo lsof -i UDP:9898
```
---
### Author:  [@dedynobre](https://discourse.nodered.org/u/dedynobre)
#### Post date: [27 July 2018 00:14 UTC](https://discourse.nodered.org/t/node-red-connection-lost/1724/38 "2018-07-27T00:14:32Z")
I removed the Broadlink node and the error stopped happening.
I'm still following but since 11PM yesterday the failure has not occurred.
---
### Author:  [@davidcgu](https://discourse.nodered.org/u/davidcgu)
#### Post date: [21 August 2018 07:52 UTC](https://discourse.nodered.org/t/node-red-connection-lost/1724/39 "2018-08-21T07:52:27Z")
Time ago I wrote a similar post related to this,most probably...
Rm broadlink node works great, however if you try to capture the temperature from a RM broadlink pro sometimes does not answer and causes crashes on node red.
I simply removed tho flow related to this and actually I'm using a RM pro & a mini with this node and works fine.
Maybe you have same problem....
Regards
---
### Author:  [@tarbear123](https://discourse.nodered.org/u/tarbear123)
#### Post date: [17 June 2019 17:00 UTC](https://discourse.nodered.org/t/node-red-connection-lost/1724/40 "2019-06-17T17:00:23Z")
i can't deploy a module,when i type node-red in the command prompt i get getting
```auto
Welcome to Node-RED
===================
17 Jun 10:55:09 - [info] Node-RED version: v0.20.5
17 Jun 10:55:09 - [info] Node.js version: v10.16.0
17 Jun 10:55:09 - [info] Windows_NT 10.0.18362 x64 LE
17 Jun 10:55:10 - [info] Loading palette nodes
17 Jun 10:55:11 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
17 Jun 10:55:11 - [info] Settings file : \Users\taran\.node-red\settings.js
17 Jun 10:55:11 - [info] Context store : 'default' [module=memory]
17 Jun 10:55:11 - [info] User directory : \Users\taran\.node-red
17 Jun 10:55:11 - [warn] Projects disabled : editorTheme.projects.enabled=false
17 Jun 10:55:11 - [info] Flows file : \Users\taran\.node-red\flows_DESKTOP-RQP2C5K.json
17 Jun 10:55:11 - [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.
---------------------------------------------------------------------
17 Jun 10:55:11 - [info] Starting flows
17 Jun 10:55:11 - [error] [e-mail in:c300172.26f78e8] No e-mail userid set
17 Jun 10:55:11 - [error] [e-mail in:c300172.26f78e8] No e-mail password set
17 Jun 10:55:11 - [info] Started flows
17 Jun 10:55:11 - [info] Server now running at http://127.0.0.1:1880/
17 Jun 10:55:12 - [info] [e-mail in:c300172.26f78e8] Error: No supported authentication method(s) available. Unable to login.
```
---
### Author:  [@nygma2004](https://discourse.nodered.org/u/nygma2004)
#### Post date: [8 November 2019 07:11 UTC](https://discourse.nodered.org/t/node-red-connection-lost/1724/41 "2019-11-08T07:11:35Z")
I am facing the same issue for the last few weeks even though I did not install new nodes, and made very little change to my flows.
I have just upgraded to 1.0 hoping that it will resolve the issue, but did not.
My flows are running, UI works, I can make changes and even deploy changes, but this message is showing constantly in the editor.
8 Nov 07:59:39 - [info] Node-RED version: v1.0.2
8 Nov 07:59:39 - [info] Node.js version: v10.15.3
8 Nov 07:59:39 - [info] Linux 4.9.35-v7+ arm LE
I see the following in the log:
(node:11584) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 open listeners added. Use emitter.setMaxListeners() to increase limit
How can I tell which is node 11584?
Regards,
Csongor
---
### Author:  [@bakman2](https://discourse.nodered.org/u/bakman2)
#### Post date: [8 November 2019 07:17 UTC](https://discourse.nodered.org/t/node-red-connection-lost/1724/42 "2019-11-08T07:17:52Z")
Could you open a new topic with your issue ?
[Previous page](https://discourse.nodered.org/t/node-red-connection-lost/1724.md?page=1)